This would be my advice, which repeats and expands on some of the stuff already said.
1) Get a degree in something that gives you a lot of experience writing both fiction and technical things. You need the fiction to be able to write good dialog and you need the technical writing to describe systems and events to programmers in ways that they can understand quickly.
2) Learn a 3D program well enought to construct a simple level - pretty much one made out of blocks. This shows you can get around a 3D world and that you know what most of the 3D terms really mean - texture maps, texels, bump mapping, verticies, etc... Putting a level together in something like the NWN or Battlefield 1942 can really help you here.
3) Learn to program either in C++ or a scripting language. This will help you understand how the computer thinks and how you have to design systems and game elements to make them work in the real world.
4) Get a job in QA, however don't stay there long if there does not look like a way to get out.
a) Don't be super pushy about getting out - that annoys people.
B) Let it be known that you are available to do extra things like review strat guides.
c) Offer to help out at trade shows - try to work whatever trade shows you can (like E3), especially during setup and tear down, even if you have to pay your way to some extent.
d) Come up with ideas for the games that you are working on and present them - but don't shove them down the producer's throat. Most producers are overworked and on death march like schedules - they may really like your ideas, but just don't have the time to include them or even consider them.
There you go.