How to prepare for an interview — the checklist that actually matters, not the one that feels productive
Rereading your resume and researching the company feels like preparation. Most of it doesn't move the needle. Here's what actually predicts how an interview goes.
Interview prep has a productivity-theater problem. Rereading your resume, skimming the company's About page, googling "questions to ask the interviewer" — all of it feels like preparing, and almost none of it predicts how the interview actually goes. The things that do predict it are less comfortable, which is exactly why they get skipped.
What actually correlates with how an interview goes
Two things, more than anything else: whether you have real, specific stories ready for the questions that are almost certainly coming, and whether you've said your answers out loud before the interview does it for the first time. Everything else — company research, outfit, arriving early — matters, but at the margins. Candidates who skip the two things above and nail everything else still stumble; candidates who nail the two things above and skip the rest usually do fine.
The four things worth spending real prep time on
Five or six specific stories, not fifty vague ones. Behavioral questions ("tell me about a time you...") are near-universal, and they draw from a small set of themes: a conflict, a mistake, a deadline, a time you influenced someone without authority, a project that failed. Pick one real, specific memory for each theme rather than trying to prepare a unique answer for every possible phrasing of the question — the same story usually answers several different versions of the question.
The technical or role-specific core, in depth rather than breadth. For technical roles, this means picking the handful of topics that actually come up constantly (the fundamentals of your stack, not the entire surface area of every technology you've touched) and being able to explain not just what they are, but why they matter and what breaks without them. Shallow familiarity with fifty topics loses to real depth on six, every time a follow-up question lands.
A walkthrough of your own most relevant project, rehearsed. Almost every interview includes some version of "walk me through a project you're proud of," and it's one of the few questions you can predict with near certainty and still prepare badly for. The failure mode is reciting the resume bullet point instead of the actual story — what the hard decision was, what you'd do differently, what broke and how you found it.
Two or three real questions to ask at the end. Not "what's the culture like" — a question that signals you actually thought about the specific role: what does success look like in the first three months, what's changed about the team in the last year, what's the hardest part of this job that doesn't show up in the posting.
What matters less than it feels like it should
Researching the company beyond a basic understanding of what they do and why you want to work there specifically. Memorizing the exact wording of an answer, rather than knowing the substance of it well enough to say it differently each time you practice. Arriving extremely early — on time is enough; excessive early arrival often just adds waiting-room anxiety.
The step almost everyone skips
Say the answers out loud, once, before the interview does it for you the first time. This is the single highest-leverage thing on this list and the most commonly skipped, because it's slightly uncomfortable and doesn't feel like "real" studying the way reading does. But producing an answer live, under a little pressure, is a different skill from recognizing a good answer on the page — and the gap between the two is exactly where prepared candidates still freeze.
If you want to run through your prep out loud, with role-specific questions and a real follow-up when an answer is thin, try mock interview practice — free to start.