Hacker News Reader

Comment by makerofspoons | Hacker News Reader

Defense contractors have a huge spectrum of work- some projects will be horrible projects maintaining legacy products with outdated technology and numerous security flaws, some will be using cutting-edge technology and will involve innovative things. There is a lot of bureaucracy, they often move slow, and the pay is often below industry standards. The current backlog of security clearance applications (in the US) means it could take years before you're fully onboard your program, and means that hiring help takes forever as well. If you end up on a great program they can be rewarding places to work, it's just a matter of being careful about choosing your opportunities.

View on HN

My experience at a big defense contractor was like that. Huge spectrum of work. Fortunately I got to work on some very cool cutting edge (at the time) technology. We were developing wafer scale integration, doing things like inter-reticle stitching to make chips the size of an entire 4 inch wafer (4 inch wafers were common at the time). Through on-chip redundancy/self-testing/configuration we were getting 50% yield. It was pretty amazing. But so many other engineers were using stone-aged technology to field satellite systems, working under hugely bloated management structures where easily 20% of your time was spent reporting and accounting for hours and costs. For quite a few years I was clever enough or lucky enough to avoid ever having to work one of those dinosaur projects.

My god, the latency on a wafer sized die must have been incredible. Certainly such a beast wouldn't be used for logic... A 4 inch image sensor would be quite interesting though.

It was indeed logic. A pair of MACs, a pair of ALUs, big chunk of on-chip memory and a big ol' mess of wires to interconnect them all. Heavily pipelined. For use in signal processing applications where latency wasn't really a concern.

We dabbled with big image sensor arrays but the sparing for yield was messy and we never came to grips with how to deal with the situation where the working sensors were in random locations in the array. It seemed to really mess up all the important systems level calculations. We also never completely worked out testing. The big logic chip had BILBO blocks so we could just put it in self test mode, run a lot of clock cycles, check the signatures, and switch in the working blocks. The sensor array needed more than that. Perhaps solvable issues, but we never got around to it.

Its really quite amazing how much more dense modern ASICs are.

I don’t think the pay thing is true in general.

> the pay is often below industry standards

Is there any defense contractor that pays anywhere near industry standards?

It depends on who is judging. I recall that you were unemployed for quite a long time because nothing was up to your standard. This suggests that your impression of "industry standards" is inaccurate, at least for someone of your capability.

You recall wrong. I haven't been unemployed since I graduated college 17 years ago.

/s Palantir.

Honestly, though, defense contractor pay is less location-dependent because a lot of the jobs are billed through to the DOD. Defense jobs can even best the industry--- just not in major areas with high costs of livi g.

I spent my time in the industry in Dallas, which is pretty close to the optimal balance of salary and metro area. My salary was not at industry averages. I remember, vaguely, Raytheon's salary bands. They weren't anything to write home about, and you were not getting anywhere near the top ends in a low COL location like Dallas.

During my career, defense contractors have generally paid a lot more with much more generous benefits (I've seen fully employer paid 401K plans to the IRS maximum), and have been a much more stable employer. Since contract work hours are billable, you generally get paid for each hour you work, unless you are working for the wrong company and only get a salary. This naturally limits extra hours to those that are truly needed, and leads to a good work/life balance.

Other than stability, none of those applied to Raytheon while I was there.

The 401k match was 6% which, while good, didn't even come to what my wife gets from her non-profit. I was paying 25% of my health coverage, which is the highest proportion if any of my five employers. (I will day, though, that Raytheon had the best family coverage rates of any of them.)

I was salaried, and other than a few times was required to record no more than 40 hours in my timesheet regardless of how much time I needed to put in. The work/life balance was highly dependent on the program you were on, and I got trapped on a bad one.

Some parts make you pay 0% of health coverage. It varies.

If you were told to record no more than 40 hours in my timesheet, then that means you DO NOT put in more than 40 hours. You're supposed to go home. If you were told to stay and this was for a government contract, it's a violation that you're supposed to report. Unless this was decades ago, you got training that told you so.

Interesting that you leaped to the experience of working at such an enterprise, rather than the ethics.

This may come as a surprise, but a lot of military contracting is stuff that many people find ethically un-troublesome. Most people within a military contractor are not working on new ways to kill poor brown people a world away or how to spy on a dissident. Plenty are working on how to preserve food better, or how to keep birds away from runways more cheaply or effectively, or how to detect malware. Or monitoring groundwater for contamination.

It could also be worth considering that anyone who makes the choice to work for such an employer has already reached ethical conclusions they are comfortable with.

Reply on news.ycombinator.com