Car Interview Prep

When to use

Reach for this when you have an interview scheduled and need to walk in with rehearsed stories, real knowledge of the company, and questions that show judgment. Use after car-resume so your stories map to the same evidence you claimed on paper.

Not for: the employer side. Designing the interview loop, competencies, and scorecards is hr-interview-prep (same name, opposite seat). This skill prepares you to be interviewed, not to interview others.

Method

1. Map likely competencies — from the posting, predict the 4-6 competencies they will probe (technical depth, leadership, conflict, ambiguity, impact). Decision point: if the loop stages are known, assign each competency to the interviewer likely to own it.
2. Build STAR stories — draft 5-7 stories in Situation / Task / Action / Result form, each with a quantified result. Cover a range so one story rarely answers two competencies.
3. Stress-test each story — for each, prep the follow-ups: root cause, your specific contribution vs. the team's, what you'd do differently.
4. Research the company — product, recent news, competitors, and the problem the role solves. Prepare to reference it naturally.
5. Prepare questions to ask — 5-8 per role, tailored per interviewer (manager: expectations/success; peers: workflow; skip-level: strategy). Decision point: never ask what a 2-minute site visit answers.
6. Rehearse aloud — time answers to 90-120 seconds; practice a clean "I don't know, here's how I'd find out."

Example

Competency "handling ambiguity." Story — S: product had no analytics and leadership wanted a roadmap. T: I owned prioritization with no data. A: I instrumented three key funnels in two weeks, ran user interviews, and built a weighted scoring model. R: shipped a roadmap that lifted activation 22%. Follow-up ready: "What would you change?" → "I'd have shipped a rough dashboard in week one instead of week three."

Pitfalls

• Memorizing scripts word-for-word — you freeze when the question is phrased differently; internalize the beats instead.
• Stories with no measurable result, or where "we" hides what you did.
• Generic questions ("What's the culture like?") that signal you didn't research.
• Rambling past two minutes; interviewers read length as poor prioritization.

Output format

Role + predicted competencies: [4-6]
STAR bank (5-7 stories):
  Title | Competency covered | S / T / A / R (result quantified) | stress-test follow-ups
Company brief: product | recent news | competitors | problem this role solves
Questions to ask (per interviewer): manager | peers | skip-level
Rehearsal checklist: timing (90-120s) | "don't know" line | opening 30s pitch