How to use this checklist
Most interview failures are not knowledge failures. They are preparation failures: the candidate who forgot to test their webcam, who never practised saying their own story out loud, who walked in without one researched question for the interviewer. Knowledge gaps you can rarely close in a week. Preparation gaps you can close in an afternoon. This checklist is built around that distinction. It is deliberately mechanical, because the point of a checklist is to move decisions out of your head and onto paper so that nothing depends on you remembering it under pressure.
Print this page, or copy the boxes into a notes app, and tick items off as you go. The plan is split into four windows: four weeks out, the week before, the night before, and the morning of. If you have less than four weeks, start wherever you are and compress; the later sections matter more than the earlier ones, because a calm, well-rehearsed candidate with a few gaps beats a panicked expert every time.
This is general preparation guidance, not a guarantee of any outcome. Adapt it to your role, your seniority, and the specific company. A staff-level system design loop and a graduate coding screen need very different emphasis, and the role-specific question sets linked at the end of this guide will tell you where to put your hours.
Four weeks out: build the foundation
This is the only window where you can genuinely move your skill level, so spend it on the hardest, slowest-to-improve things first.
- Confirm the format in writing. Email the recruiter and ask exactly what each round covers: coding, system design, behavioural, take-home, domain-specific. Ask how long each is and what tools you will use (their platform, a shared editor, a whiteboard). You cannot prepare for a format you are guessing at.
- Map the gap. List the topics each round will test, then rate yourself honestly on each. Your prep time goes to the lowest-rated, highest-weighted topics, not to the ones you already enjoy.
- Schedule daily reps, not a weekend cram. Spaced practice beats one long session. Block thirty to sixty minutes a day for the slow-to-build skills: coding patterns, system design fundamentals, or your domain.
- Start a story bank. Write down six to eight real situations from your work that show impact, conflict, failure, leadership, and ambiguity. You will reshape these into answers later; right now just get the raw material on paper.
- Do one timed mock per week. Untimed practice hides the thing that actually breaks in interviews: the clock. A weekly timed run, ideally with another person, surfaces your real failure modes early enough to fix them.
- Research the company properly. Read the product, the engineering blog, recent news, and the values. Note two or three specifics you can reference naturally. This is the raw material for "why this company" and for your questions to the interviewer.
The week before: rehearse and tighten
Skill is mostly set by now. This week is about turning what you know into smooth, repeatable performance.
- Rehearse your two-minute story out loud. "Tell me about yourself" opens most loops and sets the tone. Say it aloud until it is fluent and under two minutes. Reading it silently is not rehearsal.
- Convert your story bank into STAR answers. For each of the six to eight situations, structure it as Situation, Task, Action, Result, and make sure the Result has a number or a concrete outcome. Practise the three or four most likely ones out loud.
- Drill your weakest technical area one more pass. Do not start anything new this week. Reinforce the patterns you already half-know so they are reliable under pressure.
- Prepare three questions for the interviewer. Make them specific to the team and the role, not generic. Good questions signal genuine interest and give you information you actually need.
- Write your "why this company" and "why this role" answers. Anchor them to the specifics you researched, not to flattery. Two or three honest sentences each.
- Do a full dress-rehearsal mock. One end-to-end run under real conditions: same time of day if you can, camera on, no notes you would not have on the day.
The night before: logistics and rest
The night before is not for cramming. Cramming the night before a cognitively demanding interview trades a tiny knowledge gain for a large performance loss. Spend tonight removing every source of morning-of friction.
- Test the technology. For a remote interview, test the exact platform link, your camera, your microphone, your headphones, and your internet on the device you will actually use. Restart the machine so updates do not ambush you mid-call.
- Set up your space. Tidy, neutral background, good front-facing light, phone on silent and out of reach, a "do not disturb" note on the door. Have water within reach.
- Lay out everything physical. For an onsite: clothes, ID, printed directions, the building and floor, the contact's name and number, and travel time with a buffer. For remote: a charged laptop and a backup way to join (phone hotspot, dial-in number).
- Re-read the basics, lightly. A calm fifteen-minute skim of your STAR answers and your questions list is fine. A three-hour panic session is not.
- Plan the timeline. Know exactly when each round starts, factoring in time zones for remote loops. Set two alarms.
- Sleep. A rested brain recalls and reasons far better than a tired one that crammed. This is the single highest-return item on the entire list.
The morning of: arrive calm
The goal this morning is to walk in regulated, not wired. Small physical habits do more for your performance than any last-minute fact.
- Eat something steady. Avoid a sugar spike and crash. You want even energy for sixty to ninety minutes.
- Arrive or log in early. Ten minutes early for remote, fifteen to twenty for onsite. Early means you absorb a small delay without panic; late poisons the first impression before you say a word.
- Do a two-minute reset. Slow breathing for a couple of minutes genuinely lowers the physical symptoms of nerves. A shaky voice and a racing mind are largely a breathing problem.
- Have your anchors visible. Your two or three interviewer questions and the headline of each STAR story on a single sticky note, where you can glance without reading from a script.
- Warm up your voice. Say a few sentences out loud before you join so your first words are not the first you have spoken all day.
- Reframe the nerves. The physical sensation of anxiety and of excitement is nearly identical. Naming it as readiness rather than dread measurably helps. You prepared for this; now you get to show it.
After the interview: close the loop
The work is not quite done when the call ends.
- Note what came up while it is fresh. Write down the questions you were asked and where you stumbled. This is gold for the next round and the next company.
- Send a short thank-you within a day. Two or three genuine sentences referencing something specific from the conversation. It is a small, polite signal that costs nothing and occasionally tips a close decision.
- If an offer follows, do not negotiate from the gut. Check whether it is competitive against real market data before you respond, and counter in writing rather than on the spot.
Turn this into action
A checklist works best when it points at the specific things you still have to practise. Once you have confirmed your format, go straight to the role-specific question sets below and spend your daily reps where the gap is widest. Pair the behavioural items above with worked STAR examples, and when an offer arrives, use the salary and offer tools to make sure the number is right before you accept.
- Browse interview questions by role to target your weakest round.
- Work through behavioural questions with STAR example answers.
- When an offer lands, check it with the free offer evaluator and prepare your reply with the counter-offer email templates.