Which of the Armed Forces is Better for IT-Types? 45
tang asks: "As a Computer Science major who will be graduating this year, I wanted to know the experiences of any slasdotters who have been/are in the military. I'm exploring my options after college, and wouldn't mind serving my country. The question is, which branch of the armed forces? Physical shape is no problem, I just wanted to know which branch would have the most use for a computer programmer. The army seems to have only slightly interesting computer positions, while the navy has some better ones. Will any particular branch give me better training for when I get out?" We've already argued the point of whether it's better to go to college or sign-up, so if one had their heart set on joining, which service is better if you are planning on a career in IT, afterwards?
Air Force or Navy (Score:3, Interesting)
I can't speak for how things are today, but I know several good IT/IS guys that came out of the Air Force with decent training (and in one case a Master's degree in Math that he earned while in the Air Force). Like someone else said, it's the "least demanding" of the services, if you care about that sort of thing.
If I had to pick between Navy and Air Force, I'd consider my lifestyle. In the Navy there is a decent chance you'll get assigned to a ship at some point. If you're single, that can be somewhat cool. Go see the world, one port at a time. If you've got a family, in the Air Force you're going to get to come home almost every night to your wife & kids. You might be living in base housing in a foreign country, but at least you'll see them.
If you do this, be very careful with the recruiter(s). They will verbally assure you that you'll go into the MOS you want, then you'll get assigned to some crap that isn't useful out in the civilian world. I know a power generation guy and a communications tech trying to get MCSE certifications so they can get a civilian job. Get everything in writing.
Re:Air Force or Navy (Score:3, Interesting)
I just got out of the military (AF) a little over a year ago. I still work as a DoD contractor at the base I was stationed at for the four years I was in.
Prior to coming in the hardest decision to make was between which branch. It narrowed down rather quickly to either Navy or AirForce. They both have decent tech jobs, but it was mostly an issue of lifestyle.
Both my mother (6 years) and father (22 years)were in the AirForce so I was leaning on going towards Navy for a change of pace. He had served as a recruiter for a couple of years so I had the added advantage of taking him with me when I met with the recruiters so I wouldn't get stuck in some non-useful AFSC (Air Force Specialty Code).
The best advice you will hear over and over again is "get everything in writing". Remember it, but also read everything before you sign it and remember everything is waiverable. Two other little pieces of advice that helped a lot.
Do not just take the word of the recruiter or any one else. Things can be changed with a waiver and you are not committed to anything until you sign, so read it. It is nearly impossible to get something changed once you sign it. After you sign up you become government property (don't get a sun burn
My experience was a good one. It could have been a lot better; however, it could have been a lot worse.
Re:Don't join for the IT (Score:3, Interesting)
First, I've had almost a year of electronics training that can be transfered to college credit fairly easy. I know the Navy has longer schools (we go to some of them for some of our equipment that we get from them) but theirs are very focused. Coast Guard ETs are given a broad little-bit-of everything because that's what our support task is like. We are much thinner on resources than the other services and so we must make them stretch.
Notice that I am an Electronics Technician. I've got plenty of background in computers and I wanted to stay away from that whole psyched up shebang...though I'll be reprogramming some RADAR Eeproms via a custom serial interface when I get back from leave next week...
In any service it helps a lot to know what you want to do before you get in. Don't rely on recruiters or their aptitude tests. If possible talk to folks who've been in and are doing the job you are interested in.
The Coast Guard's IT program is a sad joke, I don't even want to go there. I pity the fools who are going to be going to the new IT school they're brewing up...(NT 4.0 basics and some exchange hacks that nobody knows how to support and you're on your way have fun. You're an "IT".)
I'll stick to my hardware thank you, as somebody's sig pointed out, if it ain't on fire, it's a software problem. But even then, almost half my job is spent with the human support side. I spend more time training folks (and fixing their mistakes) than I do ripping open racks.
Seeing as you'll have your degree, you'll be pushed into being an Officer (three times the pay for a third the work ain't bad) which is mostly paperwork and babysitting. Unless you get on one of the engineering staffs I dunno what kinda technical stuff you would be doing.
And another thing: Those of us lucky enough to be on whitehulls (Real Ships) spend at least half the year at sea. Don't listen to some sandpeep or squid who tells you otherwise.
good luck!