Dot-Commers vs. Government Contractors
StrangeBeer writes: "When the dot-Com movement went bust, it sent thousands of former employees running for cover (or the unemployment line, whichever was closer). One place they didn't go was the way of the Government Contractor who, incidentally, is doing just fine right now with or without a recession. Various reasons are given for this and one I'd like to point out is that the government managers would rather hire an underqualified person with a security clearance and later train them in their tradecraft. The vast majority of these kinds of employees are coming from other kinds of federal work (military, civil service, etc.) and not defunct dot-Com companies."
I'd like to second this. I got VERY lucky... just coming out of college and looking for my first job, I NEEDED something in the area, stable, and with decent pay. I found a job as a webmonkey (with training opportunities for database programming and multimedia) for the FDA's Center For Devices and Radiological Health.
The practical upshot is that I got lots of great training via the Killing-- err, the Learning Tree, expanded my skills tremendously, started out with a fairly eeeh salary but am now living quite comfortably... and most importantly, I did all of right at the start of the .Com Crash.
If I had jumped in on the corporate entry level (not that there were many jobs for someone who previously thought Cold Fusion was a physics thing) I'd probably have bounced around a couple jobs, maybe had to move once or twice, and definitely not had the ability to save money and get nice and financially stable. While others were auctioning off their Aeron chairs to afford cold cans of beans, I was sittin' pretty on my cheapo Ikea office stool (with homemade padding).
There are drawbacks. One, you don't start out with the Hat Made Of Money. If you can live 'comfortably' and likely single without needing a ferrari, this is not a huge hurdle. Two, if you're young, a lot of government employees are not. I'm the youngest guy in my office by about ten years. Three, no, the work is not very sexy. I view work as a means to an end (end meaning "$$$" which I spend on things I WANT to do). If a sexier job with the same amount of stability pops up, I'll go for it, but until then make mine federal.
And yet you were saying how us at SAIC are "scary" a couple of months ago 'cause we do all kinds of secret stuff :)
Truth is, working at a government contractor is great right now - especially a defense contractor, which SAIC is. Our stock is going up. We've got thousands of openings. We're hiring, not laying off. The benefits are great.
The problem is, it takes discipline. I'm only 20, so this is something I had to learn the hard way. I'm still learning. Government contractors are different. They do require documentation. They want to know exactly how you made the broken software work so that if you do get hit by a bus, someone else can make it work. It's serious business. Unfortunately, not many from the dot-com bust really seem to understand this. It's a shame too, 'cause we miss out on a lot of talent simply because people don't understand the scope of what we're doing and how it must be complete and perfect because lives depend on it.
Those who do get it though... this is the place to be. You couldn't ask for anything more.
(OT: Where do you work again wiredog?)
Every once in a while I like to masturbate a new word into my vocabulary, even if I don't know what it means.
government managers would rather hire an underqualified person with a security clearance and later train them in their tradecraft
What bullshit. Government managers want somebody with 10 years of Java experience to come and work for $35,000/year. Then, once you get in, they remove all incentive for you to advance by promising cushy benefits, annual COLAs, and best of all, job security. Here at NIH, it took almost two years for a grossly incompetent worker to be fired, simply becuase of the bureaucratic crap they had to wade through. There are techs here who let their NT 4 MCSE certifications lapse because our institute is primarily a Novell shop (although we use Exchange, we have no full-time Exchange admin); when I asked if they were planning to go for the upgrade to Win2K, they said "why bother? I don't need it" That's the kind of attitude they have here.
Then there's the condescending view all government employees have of contractors. That Dilbert cartoon a few months ago where the contractor is asked to bring his own air? It's not a joke.
I hate it here. As soon as I pass my Oracle certification tests, I'm out of here, and the federal government can kiss my fucking ass.
I use Macs for work, Linux for education, and Windows for cardplaying.
Working for the government is a double-edge sword where I work. I'm also a contractor working at a government facility.
At first, I did it our of desperation, since I got out of the Army last August, and there were serious hiring freezes in effect. "Infantry Platoon Leader" doesn't garner accolades with normal businesses.
Government work was a no-brainer for me, I had the clearance already, all I had to do is basically show up. Yes, I have to wear slacks and shirts with collars on them, but all in all, not to bad a situation, considering where the economy is.
My problem is lack of challenge. Everything is pretty backwards here. Users are expected to backup and install their own software, and print/sharing is basically all we have, but that doesn't matter, because God knows where the hell everything is anyway. Desktops and Laptops that come with Win2k are immediately downgraded to Windows 98 first edition, because it takes a LONG TIME to get anything approved. Every piece of software and hardware that we buy has to go through 3 comittees before approval. (Yep, even that printer cable).
We're running some sort of hybrid Novel 3.x network with some hastily thrown together login scripts, 10 Exchange servers that go down all the time (I believe it's 5.5 they are running), and some Computer Associates stuff that has yet to do anything. Some people even use Ghost to install client software, but only certain people are 'authorized', so all in all, the Dell Desktops (not allowed to buy anything else) are the default install, complete with AOL icons and everything. The typical 'security bulletin' is "Everyone go to Windows Update."
Of course, the mail system is clogged by the 'normal' US Army 300MB Powerpoint presentation that needs to be forwarded to multiple people, multiple times, at least three times a day. That's always great over our antiquated network.
What I don't know is if this is a typical situation in corporate America. I know other government agencies are more advanced, but its definately not us. I would like to know, because I'm pretty darn sure that Outlook shared calendars and Powerpoint "collaboration" using file sharing is considered enterprise level.
If that's the ONE great thing about working for the government, there's never a shortage of stuff to do.
Look at TRW Space and defence in Redondo beach CA, look at BAE Systems in San Diego. Those places are cutting edge. I don't understance the "2nd or 3rd rate" comment, definitly troll.
Remember that ARPANET was developed by government contractors.
Job for life mentality? What does that mean? Their company offers a pension instead of stock options that may well evaporate? They offer job security? Those things are more important as you grow older and get married and whatnot.
I interviewed with TRW. (Didn't take it because I decided I didn't like Cali). One of the people that I was interviewed by was actually a telemetry engineer for the Apollo 13 mission. That was cool.
The reason that a lot of places don't get much attention is that most of the really cool stuff to work on is rated DOD Top secret.