The Complete Interview Preparation Guide (Without Scripts That Sound Scripted)
Interviews are prepared, not survived
People confuse two different things: being good at your job and being good at interviews. They are related skills, and only one of them is decided mostly in the week before. You can't fake competence past the second question from someone who does the work daily — but you can absolutely lose a fair interview you deserved by walking in unprepared, because an interview is a specific performance format with its own rules. This guide covers how to prepare in layers — the long game, the week before, the day of, and the formats that ambush people. By the end you'll have a checklist, not a motivational poster.
The long game: become interview-ready by default
The single highest-leverage interview preparation happens months earlier, while you work. Keep a brag document: one line a week about what you shipped, fixed, handled, or learned, with the numbers and the mess while they are fresh. "Took over the escalation queue for two weeks while Aisha was on leave; cleared a 40-ticket backlog" costs ten seconds to write in June and is worth a full, specific answer to "tell me about a challenge" in November. Candidates without these notes fall back on adjectives; candidates with them tell stories. Interviewers can smell the difference in seconds and it's not a matter of charm — specifics read as truth.
The stories: your six, not someone's twenty
Almost every behavioral question ("tell me about a time…") maps to one of about six story slots: a conflict, a failure, a moment you led without authority, a deadline or pressure test, a time you learned something fast, and a time you disagreed and committed. Pick two real stories per slot from your notes — so about a dozen, of which you'll tell six. Structure each one in STAR: a two-sentence Situation, one-sentence Task, three or four sentences of Action (the part that's you, specifically — what you said, decided, built), and a Task-result ending with something concrete and one thing you learned. Rehearse out loud, twice, to a friend or a recorder — and rehearse the shape, never the words, because a memorized paragraph collapses the moment someone interrupts with a question, and interrupted recitals are exactly where nervous candidates crater.
The failure story deserves special care: pick a real failure, own it plainly in one sentence, spend most of the air on what you changed, and land the change in behavior, not humility. "I shipped a report with the wrong timezone and an executive made a decision on it. I rebuilt the close process with a two-person check, and I haven't touched a number since without one" is a complete, strong answer. Faux failures ("I once worked too late") insult the interviewer's intelligence.
The technical layer: prepare the way the round actually runs
For skill-based roles, the technical round tests a narrow, knowable band: the tools on your own resume and the core of the job description. Anything you listed is fair game, so audit your page ruthlessly before the interview — every skill there should survive a five-minute interrogation, and anything that shouldn't gets deleted today, not defended badly on the call. Then practice out the way interviews happen: talking while solving. Solve familiar problems at your desk explaining each step aloud — silence while thinking reads as blankness, and the fix is a habit of narrating ("I would first check whether the grain of this table is…"). Prepare your honest move for the unknown: state what you do know, what you would assume, and how you would find out. "I haven't used window functions in production; I know they partition a set for a per-group calculation, and I would check the docs on framing and rebuild this query with them" is a passing answer to a question you can't fully answer. Freezing and bluffing are the only real fails.
The company research: thirty minutes that changes every answer
Know four things: what they sell and to whom, how they make money if it's not obvious, what their users or customers complain about, and one recent real development (a launch, a layoff, a funding round, a market shift). That's half an hour of reading their site, reviews, and news. The payoff isn't the trivia — it's that your answers get pointed. "How would you handle a support escalation?" becomes answerable with their actual product in mind, and "do you have questions for us?" becomes a round instead of a formality. Prepare three genuine questions: about the team's biggest current problem, about how the role's first six months would be judged, about something specific you read that you want to understand better. Questions signal level — a junior asks about the process, a strong candidate asks about the problem.
The day of and the hour of
In-person: know the exact route and arrive ten to fifteen minutes early — earlier turns into awkward waiting, later turns into adrenaline. Documents printed or ready offline, phone silent, outfit chosen the night before so the morning has no decisions in it. Virtual: test the camera, microphone, and platform the day before, not at minus two minutes; plain background, light in front of you, resume open in a second window, notifications off. In both: eat, actually. A shaky, under-fueled candidate reads as a nervous one.
In the room, three mechanics carry more weight than any clever answer. Slow down: nervous candidates speed up, and a deliberate pace reads as control. Answer the question that was asked — when you drift into a related story, the interviewer has to conclude you can't be steered. And treat everyone as a person: the receptionist and the junior engineer on the loop tell the hiring manager things, and "how was I with the team" is a real input on real decisions.
Salary, offers, and the questions that feel rude
When they ask expectations, give a researched range anchored to the market and your target, not to your current salary — the full playbook is in our salary negotiation guide. When asked why you're leaving, keep it forward and true: you're moving toward something, not escaping a villain. If a question feels inappropriate — marriage, religion, children — you're allowed to answer the professional core ("I'm fully available for the travel this role requires") without disclosing, and to notice what kind of company asks.
The formats that ambush people
Beyond the standard behavioral loop, a few formats reliably trip prepared candidates because they feel like tricks. The case or hypothetical round ("how would you cut this store's costs?" / "design a feature for X") tests structured thinking, not the right answer — narrate your assumptions, ask one clarifying question, then walk a framework aloud; a messy but reasoned path beats a confident wrong guess. The "weakness" question wants a real gap plus what you actively do about it, not a humble-brag; interviewers have heard "I work too hard" so many times it has lost all meaning. The group or panel round watches how you treat peers as much as what you say — building on someone else's point reads as leadership, steamrolling reads as risk. And the "do you have any questions" moment, covered above, is a scored round at most companies, not a polite wind-down. Knowing these shapes in advance means the surprise is content, not format — which is the kind of surprise you can actually handle on the day.
Nervousness, and what to actually do about it
Preparation and anxiety aren't opposites; you can do everything above and still walk in shaking, and pretending otherwise just adds panic about the panic. Reframe the physiology first: a racing heart and sharp attention are the same arousal state, and "I'm energized" is a truer, more usable story than "I'm nervous" — tell it out loud in the two minutes before you join. Then lower the stakes you have invented: an interview is a mutual conversation about whether you both want the same thing, not an exam where one wrong answer ends your career, and you're allowed to take a beat, ask someone to repeat a question, or say "let me think for a second." Slow your breathing deliberately for a minute beforehand; it works whether or not you believe in it. Have your opening thirty seconds pre-loaded, because the first sentences are where nerves hit hardest and a rehearsed, warm "thank you for making the time, I have been looking forward to this conversation" gets you over the hump and into the groove. And give yourself permission to be a person, not a performance — interviewers consistently rate an honest, slightly nervous human who recovers above a slick candidate who never shows a seam. The shaking fades by the third well-prepared loop; the goal isn't to eliminate it but to stop it from steering.
After the interview: the part almost everyone skips
Write a ten-line debrief while it's fresh: every question asked, every place you went vague, every gap that got exposed. Those notes are tomorrow's study list and next week's better answers — interviews repeat their patterns within a field, and one clean debrief of a bad loop is worth more than another course. Send the promised follow-up within a day: short, one specific reference to a real conversation moment, one line re-affirming fit. Then, hardest and most important: let the outcome go for the day and start the next loop's preparation, because the search from the strategy article runs on volume of quality attempts, and any single interview is one sample from it.
Prepared isn't scripted. The goal of all this work is that when you sit down, the stories are yours, the facts are researched, the gaps are known, and the mechanics are automatic — so the only thing left in the room is a person having a conversation about work they've actually done. And it compounds in a way that's genuinely encouraging: the fifth interview of a well-run search feels nothing like the first, mostly because you stop arguing with yourself mid-answer.