Interview Prep Planner — Weighted Checklist + STAR Story Frame

The most common interview-prep mistake is over-indexing on technical practice at the expense of behavioral. I've watched dozens of strong engineers miss offers because their three STAR stories blurred into one vague "team project" answer under pressure. Meanwhile they'd done 60 LeetCode problems in the preceding week. The marginal hour on LeetCode at 60 hours prepared barely moves the needle; the marginal hour rehearsing STAR stories at 0 stories prepared moves it enormously.

This planner weights prep categories by how much each actually predicts interview outcomes. STAR stories and mock interviews carry the highest weights because they have the biggest delta between "prepared" and "not prepared" performance. Company research carries a smaller weight per item but has more items, because a candidate who knows zero about the company is immediately downgraded. Logistics carry the smallest weight per item but show up because an interview where you arrive 15 minutes late with a dead laptop battery can't recover.

STAR (Situation, Task, Action, Result) is the dominant frame for behavioral interviews at B2B SaaS, finance, consulting, and most enterprise jobs. Every hiring manager who's trained in the last 10 years has been told to listen for all four pieces and downgrade answers that are missing one.

Situation sets the context. 40 seconds spoken max. Where, when, what scale, what was at stake. Most candidates over-invest here — they take 2 minutes setting up the story and run out of time in the result. Trim.

Task is the part most candidates forget. What did YOU specifically own? "We" is the enemy word here. If your task description uses "we" more than "I", the interviewer doesn't know what you actually did versus what the team did around you. Rewrite in first person.

Action is the biggest section — 40-50% of the answer. Three specific actions, in order. Verbs, not adjectives. "I ran a 45-minute meeting with the CSM and the AE to build a trade sheet" is an action. "I collaborated with the team" is not.

Result needs a number. A percentage, a dollar value, a time-to-impact, a count of people. No result, no story. Candidates routinely leave the Result fuzzy ("and the project was a success") — the interviewer writes "no result cited" in their notes.

Bonus: a 5th part, what you'd do differently. Most candidates skip it. Including it is the fastest way to look senior. It signals reflection, learning from experience, and willingness to critique your own work.

Over 90% of behavioral questions in a typical interview loop are variations on six themes. If you have six strong STAR stories covering these themes, you can handle almost any behavioral prompt by mapping it to the closest story.

1. A conflict story. "Tell me about a conflict with a teammate" or "a time you disagreed with your manager." Must include what you did to resolve it and what you learned.
2. A failure story. "Tell me about a time you failed." Must include a specific failure, not a fake-modest humblebrag, and must include what you took from it.
3. A persuasion story. "Tell me about a time you persuaded a skeptical stakeholder" or "drove a decision without authority." Shows you can move a room without being the most senior person in it.
4. A judgment-under-ambiguity story. "Tell me about a decision you made with incomplete data." Shows you can move when a clear plan isn't available.
5. A managing-up story. "Tell me about a time you had to push back on your manager" or "re-prioritized at your manager's request." Shows you can work with, not around, leadership.
6. A delivery story. "Tell me about a time you shipped a hard project." The signature result story. This one does most of the interview work.

Prepare all six. Rehearse them aloud. Record yourself on a phone and play it back — the gap between what you think you said and what you actually said is surprisingly large on first listen.

Reading your STAR notes in your head is like reading music notes in your head. You can do it, but it has almost nothing to do with playing the music under pressure. One mock interview with a real human listening, interrupting, asking follow-up questions, beats three hours of solo prep.

The mock doesn't need to be with an expert. A peer in the same job family is fine. A spouse asking you the questions from a printed list is fine. The single most valuable input is a live human who interrupts you at the wrong time — which is exactly what a real interviewer does. Interruption rehearsal is specifically what solo prep can't simulate.

If you don't have a peer available, record yourself giving each answer into your phone. Play it back. You will be appalled by the filler words, the "um"s, the moments you lose the thread. That's the value — the appalled listening is the learning.

Company research is a diminishing-returns activity. The first two hours get you to 90% of what a recruiter will test for. The next two hours get you to 95%. The hours after that mostly reassure you without changing outcomes.

What to do in those two hours:

1. Read the last 3 blog posts. What's the company talking about publicly right now? A funding announcement, a product launch, a hiring post — all are cues to what the interviewer will care about.
2. Read the interviewer's LinkedIn. Where did they work before? What have they posted recently? Any hobby or side project? This is the single most efficient hour of prep — it's specific, fast, and you can use it for natural rapport in the first 30 seconds.
3. Read 2-3 recent Glassdoor reviews. Not for quality judgment — for question prediction. Glassdoor reviews mention specific interview questions that recur. If the same question comes up three times, it's coming up again.
4. Read the JD one more time. Highlight the 5 keywords that recur. Your answers to "why this role" and "why this company" should hit at least 3 of those keywords.
5. Write two questions only someone who did the research would ask. Generic questions ("what's the culture like") are fine but forgettable. Specific questions ("I saw the CEO's post on enterprise expansion last week — how does the PM team think about that tension with SMB velocity?") land.

Onsite interviews where something logistically goes wrong cost candidates more offers than any other single factor. Dead laptop battery during the virtual loop. Wrong address for the in-person. Route timing that eats the buffer and makes you arrive sweating. Running out of water mid-panel. Forgetting the portfolio.

Most of this is solvable the night before. Plan the route. Charge the devices. Lay out the outfit. Pack the bag. Go to bed at a reasonable hour. This is not the night to "catch up on" LeetCode or redo your STAR stories one more time — pre-onsite panic prep actively degrades performance. The best use of the night before is a 45-minute slow walk, a normal dinner, and 7-8 hours of sleep.

"What questions do you have for us?" is the highest-leverage 10 minutes of the interview. It is simultaneously an information-gathering chance for you and a performance for the interviewer. A candidate who asks three specific, thoughtful questions moves up in the recruiter's notes more than one who delivers three strong answers in the panel.

Three kinds of question to have ready:

• A specific question about the work. "What's the hardest technical decision the team has made in the last 6 months, and how did you make it?" Shows you care about the work, not the role title.
• A specific question about the team. "How did the two most recent senior hires on the team ramp? What made the one who ramped faster different?" Shows you're thinking about working there, not just getting hired there.
• A specific question that only the interviewer can answer. For an individual contributor: "What's been the hardest thing for you this quarter?" For a manager: "What's the team's biggest unsolved problem right now?" These get real answers and create a small moment of connection.

Never ask questions you could have Googled. "What does your company do?" is a rejection trigger.

Thirty minutes before the interview: reread your six STAR stories one time. Not to memorize — to re-prime the language. Take a walk, 10-15 minutes, phone on airplane mode. Drink water. Arrive (or log in) 10 minutes early. In the last 2 minutes, warm up your voice by reading a paragraph aloud — stretch-runners do this before a race for the same reason.

When the interview starts, your job in the first 30 seconds is to be warmer than you feel. Smile, name them, ask how their day is going. It sounds corny; it works because the interviewer is also a human who's been in a window-less room for three hours and will respond to warmth. That 30 seconds sets the tone for the full hour.