Stage 07 of 12 — Interviews
Interview Prep
Pilots know how to execute. The problem is most haven’t thought about what interviewers are actually evaluating — and confuse performance with authenticity.
The research on employment interviews is clear: structured behavioral interviews predict performance better than anything except actual work samples. You can bring structure to your side of the conversation regardless of what they bring to theirs.
~4 min read
TL;DR
- —What interviewers actually evaluate — and how to give them what they want
- —The STAR-L framework and how to build a story bank before every interview
- —Skim if: you're consistently getting to final rounds and getting offers
What they’re actually evaluating
Not polish. Not rank. Not how many hours you flew.
Can this person think clearly?
Reason through ambiguous problems, explain complex ideas simply, show their work.
Can the team work with this person?
Listening, adaptability, awareness of how they affect others, ability to disagree without damaging the relationship.
Do they have the technical foundation?
Relevant experience, demonstrated capability in required domains, honest about gaps.
Do they fit this org?
Values, working style, motivations aligned with the team culture and mission.
Source: Huffcutt et al. (2001) meta-analysis on employment interview validity, Journal of Applied Psychology.
The STAR-L framework
STAR answers work because they’re specific and concrete. The L is what separates good answers from great ones — and what most pilots skip.
One or two sentences. Just enough context for them to understand the stakes. Not the full mission brief.
⚠ Common trap: Pilots spend 80% of their answer here. Don't.
Your specific responsibility. Not the team's. Yours. What were you accountable for?
What you actually did. The specific decisions you made and why. Your reasoning. Your adjustments. Use "I," not "we." This is the longest part by far.
⚠ Common trap: Many candidates default to "we" because that's how collaborative work happens. In an interview they're evaluating YOU. Say "I."
What happened? Quantify where possible. Don't fabricate numbers, but don't be vague if you have them.
One sentence: what did you take from this experience? This signals growth mindset and self-awareness — two things interviewers specifically weight.
⚠ Common trap: This is the differentiator. Most candidates skip it entirely.
Key insight
The difference between a good answer and a great one is the L — what you Learned. It’s the signal that you reflect, adapt, and won’t repeat mistakes. Interviewers remember it because almost no one does it.
Build your story bank before every interview
Prepare these five categories minimum. Rehearse them until they’re natural, not memorized.
Technical challenge
A time you solved a complex technical problem. Not "I flew the mission." A specific problem you diagnosed and solved.
Team success / leadership
A time your team achieved something significant because of how you led. Specific. Named. Dated.
Failure and what you learned
A real failure. Not "I work too hard." A genuine mistake, what happened as a result, and what you changed afterward.
Time you led without authority
A time you influenced an outcome without a direct authority over the people involved. Lateral leadership.
Something you built from nothing
A program, process, team, or initiative you started that didn't exist before you. Especially valuable for management roles.
Treat your interviewer as an asset
Before every interview, spend 15 minutes on each interviewer. Not to impress them. To understand them.
Find their LinkedIn. See how they got to where they are. What did they do before this org? What do they seem to care about? Have they published, spoken, or written anything? Is there common ground — geography, school, background, interest?
You’re not fishing for flattery material. You’re trying to understand their frame of reference so you can communicate effectively with them.
What to do with what you find
Questions to ask them
The questions you ask reveal more about you than the answers you gave. Strong questions signal you’ve actually thought about the role.
Strong questions
- ✓What does success look like in this role in the first six months?
- ✓What's the biggest challenge the team is facing right now?
- ✓What made the last person in this role effective — or what would you change?
- ✓How does this role interact with [specific other team]?
- ✓What do people who thrive here have in common?
Weak questions
- ✗"What's the work-life balance like?" (Save for after the offer.)
- ✗"How quickly could I be promoted?" (Signals you're already looking past the role.)
- ✗Anything you could have found on their website.
- ✗"What does [company] do?" (Shows you didn't research.)
- ✗No questions at all. (Signals low interest.)
Managing anxiety
Performance anxiety in interviews is physiological, not a character flaw. Evidence-based management exists.
Reframe, don't suppress
Tell yourself "I am excited" rather than trying to calm down. Anxiety and excitement have the same physiological signature. Reframing to excitement improves performance. Trying to suppress arousal makes it worse. (Jamieson et al., 2010)
Pre-interview routine
Develop a 5-minute routine before every interview: slow breathing, review your key stories, one brief physical movement. Athletes use pre-performance routines to regulate arousal. Works the same in interviews.
Preparation is the strongest anxiety reducer
Anxiety is highest when uncertainty is highest. Know your stories. Know the org. Know your questions. Preparation doesn't guarantee a good interview, but lack of preparation guarantees a bad one.
The post-interview PEDL
Run this within 2 hours of every interview. Win or lose — the debrief is the product.
What was your strategy going in? What stories were you planning to use? What questions were you going to ask?
What actually happened? Which questions came up? How did your answers land? Where did you feel strong, where shaky?
Two things you did well. Two things you'd do differently. Your assessment first — don't wait for external feedback.
What is the one thing you're taking forward to every interview after this one?
The interview that doesn’t get debriefed is an experience that doesn’t become learning. (Kolb, 1984)
Interview Workbook
The full prep workbook — worked example
A complete interview prep workbook built for a USAFA pilot applying to Anduril as a Product Manager. Five phases: map the company, understand the role, practice answers out loud, analyze tradeoffs, run scenarios. Includes Weapons School → PM translations, company intel, story bank prompts, and a post-interview debrief template.
The structure is reusable for any role. Replace the company-specific sections with your own research. The frameworks — STAR-L, PRD structure, prioritization logic, debrief cadence — transfer anywhere.
Open the workbookWhere people stall here
Over-preparing for predicted questions, under-preparing the story bank. You can’t control what they ask. You can control how well you know your own material.