One candidate describes a relaxed, audio-only Microsoft Teams interview of about 45 minutes for a Lockheed Martin Supply Chain Analyst role, built on STAR-style behavioral questions and ending in an offer.
$82K
Avg. Base Comp
$100K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The Lockheed Martin Supply Chain Analyst interview is described by one candidate, who received an offer, as approachable for such a large aerospace company. The conversation ran about 45 minutes over Microsoft Teams, and the candidate says no webcam was required. It was audio only, which made the setting feel less formal than expected.
The questions were behavioral and built around the STAR format. The candidate was asked to tell the interviewer about themselves, explain what drew them to the role, and describe a challenge they had faced and how they handled it. The interviewer was patient and encouraged openness about what the candidate did and did not know. The candidate says the focus was on how they think and handle situations rather than on catching them out with technical questions.
The second half of the call left substantial time for the candidate's own questions, and they were answered thoughtfully. Expect to use that time. Good questions to bring include how supply chain processes run day to day, how the team works together, and what growth looks like in the role.
To prepare, write out two or three STAR stories about challenges you overcame and conflicts you resolved with teammates. Keep each story specific and short enough to deliver conversationally. Also prepare a clear answer for why you want a supply chain role in aerospace and defense. This guide rests on a single candidate report, so other interviewers or teams may run the process differently.
Synthesized from 2 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Lockheed Martin process.
The interview was pretty structured and moved faster than I expected. I was contacted through LEO and got scheduled about a week later for a Zoom interview, and the questions were clearly pre-determined. The first round felt like a phone screening with the hiring manager, where they mostly walked through my resume and asked for more detail on my experience and projects. One question that stood out was asking me to tell them something that was not on my resume, so it was less about reciting bullets and more about how I talked through my background on the spot.
After that, I was invited to a panel interview, and that part was a mix of behavioral and technical discussion. The behavioral side was very common-sense but still specific to the role, like whether I work better in teams or as an individual, describing a time I had to communicate an unpopular opinion, and talking about the biggest mistake I’ve made. They also asked about data collection and how I handle communicating ideas, so they were paying attention to how I think and how I work with other people. The technical questions came up during the panel, but it wasn’t a heavy coding or case interview; it was more about knowing your stuff and being able to explain your experience clearly. One thing I appreciated was that they gave time to think through questions and would repeat them if needed, which made the process feel fair and conversational. Overall, it was a pretty prompt process and they got back to me quickly with feedback. I ended up not moving forward, but the interview itself was straightforward and well organized.
Prep tip from this candidate
Be ready to walk through your resume in detail and answer behavioral questions about teamwork, mistakes, and communicating unpopular opinions. Also prepare to discuss data collection and how you explain ideas, since the panel mixed those themes with light technical follow-up.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Lockheed Martin
Describing a data project and its challenges
| Question | |
|---|---|
| Client Solution Pushback | |
| Nightly Job | |
| Deciding Between Solutions | |
| Testing Constraints | |
| Your Strengths and Weaknesses | |
| Presentations and Insights | |
| Top 3 Users | |
| Over-Budget Projects | |
| International e-Commerce Warehouse | |
| Addressing Data Quality Issues | |
| Safe Deployments | |
| The Pirate’s Hunt | |
| Why Do You Want to Work With Us | |
| Stakeholder Communication | |
| Robotics Upgrade Tradeoff | |
| Analyzing Multiple Data Sources | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Fair Coin | |
| Upsell Transactions | |
| Longest Streak Users | |
| Employee Salaries | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Slacking Employees Salaries | |
| Last Transaction |
Synthesized from candidate reports. Individual experiences may vary.
The candidate reports an interview of about 45 minutes over Microsoft Teams, audio only with no webcam required. It opened with foundational questions: tell us about yourself and what drew you to the role. Prepare a short, specific answer on your background and why supply chain at Lockheed Martin.
The candidate was asked to describe a challenge from the past and walk through how they handled it, in a structured STAR format. The interviewer was relaxed and willing to explain concepts in detail, and encouraged openness about what the candidate did or did not know. Prepare two or three STAR stories, including team conflicts you resolved.
The candidate says the interviewers left substantial time in the second half for their own questions and answered them thoughtfully. This typically gives you room to show interest, so bring questions about supply chain processes, team dynamics, and growth opportunities. The candidate reported receiving an offer.
