Pluspunten
-Lots of good people there, I enjoyed working with my colleagues. -Flexible work life balance. -Lockheed will pay for your post graduate schooling. -80 hours of Floating Holidays -Strong Ethics and Values -Good opportunities to mentor and learn -Some cool R&D projects
Minpunten
-Colorado Springs location used to have a cafeteria. They replaced it with a gas station like food. -There used to be more work at this area, but other contractors have beat Lockheed in some contracts Colorado Springs. With more space work coming to Colorado Springs, I'm sure they will have more opportunities. -Security - This is happening with all defense contractors, but over the last 3 years or so, Lockheed starting locking down on some processes and labs adding more work on teams to comply with stricter security measures. I found I was spending much more time with security people in meetings instead of working on building the product. -Paternity leave is not as good as some other defense contractors. -Lockheed recently combined PTO and sick time. They added 40 hours of "discretionary" time as well, but it was a little confusing when you can or can't use it. I think they should just let you use discretionary time for whatever you want. -Typical Bureaucracy Complaint: Working in different business areas feels like working for a different company. A while ago Lockheed used to be more unified as a company, but it becomes confusing who is responsible for what IT infrastructure, security, etc. when you have different business units in the same building. For example, if you work for RMS in a Space building, you might have two different security groups evaluating and randomly making requests for you to comply with security. Sometimes they even contradict each other, and don't communicate. You'll get an email from someone on the east coast demanding you make changes to your local system or a server they scanned. You then hop on a call with (I'm not even exaggerating) 20 different people who don't know each other trying to coordinate and figure out who is responsible for patching and fixing the system in question. It gets figured out eventually, the only point I'm making is it's a lot of man power to address sometimes lower priority items.