Slashdot Mirror
Become A Techie In The Military Or Tough Out College?
Vain asks: "I'm a student in Wisconsin who is wondering just where his career path is leading him and needs advice. I'll be graduating with a 2 year degree (in networking) this summer. A few people have suggested that the military is a great place to get not only good pay, but good money for school as well, even if it's just the guard. Should I consider joining the guard, getting a BS or MS through government funding, or stick with my 2 year for now and try to find a place in the area? I guess what I'm looking for is some techies in the military (or out) to give me a few suggestions."
- No guarantee of good use of your talents I have a degree in computer science with a specialization in network protection and information warfare. My AF job code is as a communications & information officer. Currently, though, my job is as an analyst for mostly unrelated subjects. (Some are related to computers, but less than 10%.) There is nothing I can do about this. Period. I've tried at least 5 times to be a better asset to the Air Force, and have been shot down each time by someone who manages my career (whom I've never talked to in person about my career, nonetheless) in Texas. I've basically been told that this inefficiency is par for the course and I just need to wait a few years to take a chance on another job with no guarantee of being interesting.
- Lack of self-determined direction As mentioned above, you get little to no input to where you will be going next, or what you will be doing when you get there. Have a family in Virginia? Here's your 1-year ticket to Korea/Greenland/etc. Granted that's a part of the way-of-life, and I understand that, but it's a major factor for many techies. (Ever try to stay current on the tech issue-of-the-day from a camp on the Korean DMZ? Me neither, but I doubt they have decent public internet access.) Even if they tell you you are on your way to a dream job, it can get pulled out from under you before you get there (or after). For instance, when coming to my current assignment, I was told I'd be managing the network administration shop. When I arrived, they told me that I'd be doing something completely different. Too bad - that's the end of the discussion.
- Slow bureauacracy (sp?) Don't expect to work with the latest technology, no matter what the Navy commericals tell you. For the most part, the acquisitions process takes so long that we don't get to play with the latest toys, except in some of the more restricted programs. Hell, I had some brilliant airmen working for me a few years ago that were forced to sit on 20-year old messaging equipment (teletypes, anyone?) and operate them for 8-12 hour shifts, 24/7. Needless to say, they are pursuing other interests, for far greater pay.
- Lack of generally-accepted 'perks' No 401K, no retirement plan outside of "stay for 20 years to get 50% of your pay, but leave before then and get nothing"
- Frequent moves Every 2 years, you will most likely have to move. This could be a good or a bad point depending on your perspective.
There are the good parts, though - guaranteed job security, the ability to put it on a resume as experience (even if it wasn't that techie-related, it does look good), camaraderie (I've gotten several job offers that I'll look at when getting out from people I used to work for/with), etc.So what's the optimal solution? Not sure. I'd say it seems to be either Guard/Reserve (I plan to go reserve when I seperate from active duty), or contractor. Just be sure you can still have a connection to the outside world to stay current.
Finally, for some people, this is just the right thing to do, and they would stay past 30 years if they were allowed. I'm just relaying my experience. If you have other questions, feel free to drop a line at the above email addy (after despamming it, of course).
Good Luck!