Pressure questions, calmly
Write the contract
Deadline + thin docs
Early + owned
Gates + rollback
Ambiguity and change
Decision with incomplete information
Aim: Make the bet small and reversible.
Ambiguity / requirements kept changing
Aim: Freeze a short contract; park the rest.
Pivot mid-project / announce an unpopular direction change
Aim: Bad news early, with a better plan and no ambush.
Scope creep / limited resources / quality vs cost
Aim: Cut with a rule, publish the cut list.
Case pack: foggy feature, tight deadline
Write a thin contract
Discover + spike
Cut list + kill criteria
Protect invariants
Interviewers love this shape: build a feature that is time- and cost-sensitive, documentation is thin, product intent is fuzzy, and the date will not move. They are scoring judgment under fog — not whether you hero-coded all weekend.
Situation prompt (umbrella)
Tell me about a time you had to build a feature under a tight deadline when the product wasn’t clear, documentation was limited, and both time and cost mattered.
Aim: Show you create clarity, constrain cost, and still ship a trustworthy slice.
Product is fuzzy — what do you do first?
The product manager can’t fully specify the feature, but leadership wants it this sprint. Walk me through your first 72 hours.
Limited documentation
You inherited a critical path with almost no docs and a feature due soon. How did you learn enough to ship safely?
Time and cost sensitive
Leadership says both the date and the budget are fixed. How do you negotiate scope without sounding difficult?
Tight deadline — quality under pressure
The date will not move. What do you refuse to cut, and what do you cut first?
When the fog wins (miss / near-miss)
Tell me about a time this kind of foggy, deadline-driven feature still went sideways. What did you do?
Follow-up Q&A: foggy feature & deadline
After the umbrella story, interviewers dig here. Full sample answers — swap your facts.
Signals rubric: foggy deadline cases
Misses and tight deadlines
You failed / missed a date / broke a commitment
Aim: Real miss, your part, system change.
Delivered under a brutal deadline / surprise obstacle
Aim: Cut scope, keep the safety net.
Error in judgment / your idea wasn’t best / you changed your mind
Aim: Help the better idea win out loud.
How do you verify correctness? / your code review bar
Aim: Layers: tests, canary, review questions.
AI judgment and hard conversations
Criteria to release a new AI model
Aim: A go/no-go list a skeptical HM would trust.
AI safety / security / agent tools / what you’d rebuild with AI
Aim: Controls on tools and data — not framework name-drops.
Explain to non-technical stakeholders / deliver bad news
Aim: Impact, options, ask — leave the jargon at home.
Emerging tech disrupted how you work — what did you do?
Aim: Govern the accelerator; don’t lower the bar.
Signals rubric: ambiguity & change
How interviewers hear answers in the ambiguity & change cluster at staff / L6 backend.
Follow-up Q&A: ambiguity & change
Interviewers almost always dig after your STAR. Each card is a likely follow-up with a full sample answer — swap in your facts; keep the shape.
30-minute rehearsal: ambiguity & change
Signals rubric: misses & tight deadlines
How interviewers hear answers in the misses & tight deadlines cluster at staff / L6 backend.
Follow-up Q&A: misses & tight deadlines
Interviewers almost always dig after your STAR. Each card is a likely follow-up with a full sample answer — swap in your facts; keep the shape.
30-minute rehearsal: misses & tight deadlines
Signals rubric: AI judgment & hard conversations
How interviewers hear answers in the AI judgment & hard conversations cluster at staff / L6 backend.
Follow-up Q&A: AI judgment & hard conversations
Interviewers almost always dig after your STAR. Each card is a likely follow-up with a full sample answer — swap in your facts; keep the shape.