Big company hand-holding.
Very good benefits.
A number of projects that only big-gun defense contractors can get.
Depending on where you are, you can be working with some really good people.
Much better for technical work than management.
Big company bureaucracy and irrational processes, well beyond what's required for defense contracting.
Lots of unaccounted-for time, particularly if you are in management, where you are graded on the curve. It is a "40 hour nominal" but really 50, 60 if you are trying to get anywhere, with lots of fuzzy expectations. That fact is not remarkable, but the refusal to keep track of it makes planning a lot harder and tends to lead to fake plans.
Lots of straight communication noise and rules that are irrelevant to day-to-day operations.
I feel like I am supporting a lot of heavy weight that is paid to get in my way.
Lots of unexciting projects that big-gun defense contractors generate for job security and revenue.
Different activities have different levels of risk. For example, heavy, month-long purchasing processes that are appropriate for commercial airplanes or shooting things are not appropriate for routine IT procurement. In the end, people determine where you get to, so you have to provide the right balance between empowerment and risk mitigation.
Not bad, but since the software test is in pen and paper, you should practice pseudocode and not cheat. Interviews are now in the post-AI era, where companies use it extensively or not at all.
Though it was pre-recorded, there was one behavioral question, one coding question, and one recording of you explaining your solution. The question was impossible, and I later looked it up to see it wasn’t actually solvable.
Three engineers interviewed me at my university during a career fair. Two were mechanical, and one was a DevOps engineer. They introduced themselves and asked me some questions. Overall, it was very relaxed.
Not bad, but since the software test is in pen and paper, you should practice pseudocode and not cheat. Interviews are now in the post-AI era, where companies use it extensively or not at all.
Though it was pre-recorded, there was one behavioral question, one coding question, and one recording of you explaining your solution. The question was impossible, and I later looked it up to see it wasn’t actually solvable.
Three engineers interviewed me at my university during a career fair. Two were mechanical, and one was a DevOps engineer. They introduced themselves and asked me some questions. Overall, it was very relaxed.