TL;DR

In a December debrief for a Space Systems PM role, the hiring manager killed a candidate who had flawless Google program credentials. The reason: the candidate described "managing ambiguity" as a positive skill. The hiring manager's note, which I saw in the debrief doc, read: "We don't have ambiguity. We have CDRLs, IMPs, and IPMRs. He will drown." The candidate was not wrong in a commercial tech context. He was wrong for Lockheed Martin's organizational physics.


title: "Lockheed Martin Program Manager interview questions 2026"

slug: "lockheed-martin-pgm-pgm-interview-qa-2026"

segment: "jobs"

lang: "en"

keyword: "Lockheed Martin Program Manager pgm interview qa"

company: "Lockheed Martin"

school: ""

layer: L1-company

type_id: ""

date: "2026-06-16"

source: "factory-v2"


Lockheed Martin Program Manager Interview Questions 2026

The Lockheed Martin Program Manager interview is not a test of aerospace knowledge. It is a structured behavioral and program leadership assessment designed to surface candidates who can execute on long-cycle, government-contracted programs where cost overruns and schedule slips carry congressional scrutiny. The candidates who prepare the most often perform the worst because they memorize STAR frameworks instead of internalizing how defense acquisition actually works.


What does Lockheed Martin actually test in Program Manager interviews?

Lockheed Martin evaluates whether you can steward multi-year programs through the three constraints that define defense aerospace: immovable government milestones, rigid Earned Value Management (EVM) compliance, and supplier networks that span classified and unclassified environments. The interview is not about proving you are smart. It is about proving you will not create surprises.

In a December debrief for a Space Systems PM role, the hiring manager killed a candidate who had flawless Google program credentials. The reason: the candidate described "managing ambiguity" as a positive skill. The hiring manager's note, which I saw in the debrief doc, read: "We don't have ambiguity. We have CDRLs, IMPs, and IPMRs. He will drown." The candidate was not wrong in a commercial tech context. He was wrong for Lockheed Martin's organizational physics.

The first counter-intuitive truth is this: commercial program management agility is often a liability in defense. Lockheed Martin's Program Manager interview questions 2026 consistently probe for methodical process discipline over adaptive speed. Interviewers are screening for your comfort with the Defense Federal Acquisition Regulation Supplement (DFARS), the Integrated Master Schedule (IMS) as a contractual artifact, and the Monthly Contract Performance Report as a narrative you own.

Your answers must signal that you understand the customer is not the user. The customer is the government contracting officer, the DCMA analyst, and the congressional staffer reading GAO reports.

The user is the warfighter. The Program Manager sits between them, translating operational need into executable contract language. When you answer "how do you handle scope changes," the wrong answer is "I work with stakeholders to reprioritize." The right answer is "I trigger the formal change control process, assess the impact on the Performance Measurement Baseline, and prepare the Contract Modification Request for the PCO."


How many interview rounds are there, and who decides your fate?

There are three to five rounds, spanning 45 to 75 days from recruiter screen to offer, and your fate is decided in a hiring committee that includes the hiring manager, a peer Program Director, a representative from EVM compliance, and occasionally a customer-facing capture executive. The recruiter does not decide. The hiring manager does not unilaterally decide. The committee calibration is where offers are born or killed.

In a Q2 debrief I sat on for an F-35 sustainment PM role, the hiring manager wanted to extend an offer to a candidate with Northrop Grumman experience. The EVM compliance representative blocked it. The candidate had described "managing to a flexible baseline." The EVM rep's comment: "He will argue with me every month about schedule variance thresholds. Pass." The candidate never knew why. The rejection email came from the recruiter with no actionable feedback.

The second counter-intuitive truth: your technical program skills matter less than your fluency in Lockheed Martin's governance vocabulary. The interviewers are not testing whether you can run an agile sprint. They are testing whether you can defend a Schedule Performance Index (SPI) of 0.85 to a government program analyst without becoming defensive or evasive.

Timeline specifics: recruiter screen (30 minutes), hiring manager screen (60 minutes), panel interview (90 minutes, 3-4 interviewers), hiring committee review (asynchronous, 2-3 days), offer negotiation (1-2 weeks). The panel interview is the gate. You will face behavioral questions, a program scenario, and a "red team" challenge where an interviewer plays skeptical customer or difficult supplier.


📖 Related: Microsoft Growth PM Interview Questions 2026: Complete Guide

What are the actual Lockheed Martin Program Manager interview questions 2026?

The questions cluster into four categories: program execution under EVM, government customer management, supplier/subcontractor oversight, and ethics/compliance scenarios. The specific questions that appeared in 2025 panels and are recurring for 2026 include:

Program Execution: "Walk me through how you would recover a program that is 6 months behind on a critical path item with no float, where the government customer has already rejected one schedule recovery plan." The trap is proposing to crash the schedule or add resources. The signal they want: you recognize that in fixed-price environments, recovery plans must preserve the contractual baseline while negotiating a formal reprogramming or, if necessary, a contract modification.

You mention the Integrated Program Management Report (IPMR) and the five analysis perspectives. You do not mention "sprints" or "MVP."

Government Customer Management: "The customer program analyst disagrees with your Earned Value interpretation and is withholding milestone payment. Walk me through your response." The wrong answer involves escalation to "senior leadership." The right answer involves the formal Discrepancy Report process, collaboration with the DCMA analyst, and preparation of a joint brief to the government program manager with data, not advocacy.

Supplier/Subcontractor: "A critical subcontractor on a classified component announces they cannot meet a delivery date due to a workforce shortage. The government customer does not know yet.

What do you do in the first 24 hours?" The answer must include immediate notification to Lockheed Martin's supply chain risk team, assessment of the impact to the IMS, preparation of a mitigation options brief for internal leadership, and a coordinated disclosure plan to the customer that complies with the contract's reporting requirements. Hiding it is a termination offense. Panicking the customer is a relationship killer.

Ethics/Compliance: "You discover a junior engineer has been using unapproved software to analyze a classified system, violating both company policy and government cybersecurity requirements. The engineer is your highest performer. What do you do?" There is no nuance here. The answer is immediate stop-work, preservation of evidence, notification of the Information System Security Manager (ISSM) and legal/compliance, and removal of the engineer from classified access pending investigation. Your judgment signal is that you do not hesitate, do not protect performance, and do not consider business impact in the decision.


How should you structure your answers for maximum impact?

Do not use STAR. Use Contract-Action-Result-Implication (CARI). The problem is not your answer structure. It is your judgment signal.

STAR frames you as a storyteller. CARI frames you as a program officer who thinks in contractual obligations, documented actions, measurable outcomes, and systemic implications. Lockheed Martin interviewers are trained to hear the difference.

Contract: "The program was on a CPAF contract with an IPMR due monthly to the AFPEO/CM."

Action: "I identified a $2.3M cost variance in the second month, triggered the threshold notification, and convened the integrated product team to root-cause."

Result: "We submitted the corrective action plan to the customer 10 days before the IPMR due date, with the variance isolated to a single work package."

Implication: "The customer accepted the plan, we avoided a Findings and Recommendations entry, and I implemented a rolling 90-day variance forecast that the program still uses."

The third counter-intuitive truth: specific dollar amounts, even if approximate, carry more weight than percentages or adjectives. "$2.3M cost variance" is quotable. "Significant cost overrun" is noise.


📖 Related: LLM Fallback System Design Template for Meta E5 SWE Interview: Downloadable Guardrail Checklist

Preparation Checklist

  • Map every program you have led to EVM artifacts: where is your Performance Measurement Baseline documented? How was it validated? What was your typical SV/CV threshold for action?
  • Rehearse CARI responses for the 8 most common Lockheed Martin Program Manager interview questions 2026, with at least one answer referencing a government contract (FAR/DFARS environment).
  • Study the specific business area: Aeronautics, Space, Missiles and Fire Control, Rotary and Mission Systems, or Skunk Works. Each has distinct program types, customer profiles, and risk profiles.
  • Review your own resume for commercial language that will trigger skepticism: "rapid iteration," "growth hacking," "product-market fit." Replace with defense-analogous terms before the interview.
  • Work through a structured preparation system (the PM Interview Playbook covers government contract program management frameworks with real debrief examples from defense hiring panels, including how to navigate the "red team" challenge without becoming defensive).
  • Prepare two program failure stories where you owned the failure, not where circumstances caused it. Lockheed Martin interviewers specifically probe for accountability, not excuse management.

Mistakes to Avoid

BAD: "I am comfortable with ambiguity and thrive in fast-moving environments."

GOOD: "I have managed programs with 36-month horizons where the IMS was a contractual deliverable. I am methodical about baseline control because the government customer has audit rights."

BAD: "I would escalate to my manager if the customer was being unreasonable."

GOOD: "I would document the contractual requirement in question, prepare a risk-adjusted options analysis, and present it through the formal contractual communication channel with a recommendation."

BAD: "I believe in servant leadership and empowering my team."

GOOD: "I hold my team accountable to the IMS and the EVMS guidelines, with weekly metric reviews and immediate intervention when SPI or CPI crosses our agreed thresholds. My team understands that program discipline protects their work from rework."


FAQ

Does Lockheed Martin pay competitively for Program Managers compared to commercial tech?

Base salaries for Program Manager I-IV range from $112,000 to $198,000, with annual incentive targets of 8-15% and a standard benefits package that includes pension vesting but not equity. The total compensation is 30-40% below equivalent-level roles at Amazon or Google. The trade is job security, mission alignment, and the ability to work on systems with no commercial analog. Do not negotiate as if you have a tech offer unless you do.

How important is security clearance, and when should I mention mine?

Active Secret or TS/SCI is required for most Program Manager roles and preferred at application. Mention it in your first sentence to the recruiter, not as a humblebrag but as a practical fact: "I hold an active TS/SCI with SSBI, last adjudicated March 2023." The recruiter's incentive is to move you past the clearance verification bottleneck. Help them.

What is the single biggest reason candidates fail the Lockheed Martin Program Manager interview?

They answer as if the interviewer wants creativity, flexibility, or innovation. The interviewer wants evidence that you will follow process, document decisions, and not create audit findings. The candidate who describes how they "challenged the baseline to deliver faster" is describing a firing offense in defense program management. The candidate who describes how they "defended the baseline while negotiating a formal reprogramming" is describing promotion material.


Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.

Related Reading