--- title: The week before your interview: what to actually do (and stop doing) description: A working engineer's honest week-before-interview plan — what's worth doing, what to stop, and what nobody warns you about the last 48 hours. url: https://usegreenroom.app/blog/week-before-interview-checklist last_updated: 2026-06-11 --- ← Back to blog Interview prep # The week before your interview: what to actually do (and stop doing) May 21, 2026 · 8 min read ![The week before your interview: what to actually do (and stop doing) — cover illustration from Greenroom, the AI mock interviewer](/assets/blog/week-before-interview-checklist-hero.webp) Most of the advice you'll find for the week before an interview is bad. Not malicious, just useless. "Get a good night's sleep." Yeah, thanks. "Review your projects." Sure, how exactly. I've coached engineers through this week probably forty or fifty times by now — friends, ex-coworkers, people who saw I tweeted about interviews and slid into my DMs. The same patterns repeat. The people who do well in the final loop are usually doing the same three or four things in the week before. The people who flame out are usually doing one of the same two or three things wrong. This is that playbook. ## The framing that makes everything else click You are not learning new things this week. You are reducing variance. The version of you who shows up to the interview should be the lowest-variance version of you — the one who reliably gives a solid answer, not the one who occasionally gives a brilliant one and occasionally freezes. This reframing matters because it tells you what to do and what to skip. Cramming a new topic two days before? Variance goes up. Practicing a question type you're already decent at, until you can give a consistent answer? Variance goes down. The interview rewards floors, not ceilings. ## Day-by-day, roughly ### 7 days out: audit, don't add Look at the role description and write down — actually write down, on paper or in a doc — the three or four things you'd ask a candidate about if you were the hiring manager. These are your likely interview topics. Now honestly grade yourself on each one: solid, shaky, would embarrass myself. The "shaky" ones are where this week goes. Do not, at this point, start a new course or read a new book. You don't have time for the loop of "learn → forget → relearn." You have time for "practice → consolidate → recall." ### 6-5 days out: re-read your own work If you're an engineer, this means rereading your two or three most relevant repos like an interviewer would. Read the README. Open the most-changed files. Look at recent commits. You're not studying — you're refamiliarizing yourself with decisions you made months ago that you're going to have to defend out loud. Write down, for each project: *one thing I'm proud of, one thing I'd do differently, one trade-off I made*. Three bullets per project. These will become the spine of every "tell me about a project" answer. ### 4-3 days out: speak, don't read This is where most people get the prep wrong. They keep *reading*. Watching videos. Skimming explanations. None of it transfers to an interview because the interview is verbal. Reading and recall are different muscles. Pick the three topics from Day 7 you graded "shaky." For each one, open a voice recorder on your phone. Talk for two minutes about it as if you were explaining to an interviewer. Listen back. Wince. Do it again. Three times each. That's 18 minutes of recording. It's exhausting and effective. ### 2 days out: one full mock, no exceptions Schedule one full-length mock interview. With a friend, with a paid service, with an AI tool, with your patient partner who has no idea what a binary tree is — doesn't matter. The point isn't the feedback, the point is the dress rehearsal. You want to have already felt the cognitive load of a 45-minute conversation before the real one. If you can only do this once, do it on the day-minus-two slot. Not the day before. You need a recovery day between dress rehearsal and the real show. ### 1 day out: actively do less The hardest day. The instinct is to cram. The instinct is wrong. The marginal hour of prep on the day before is worth almost nothing — your brain is at saturation, and anything new will displace something better-rehearsed. What helps: walk, eat well, sleep at your normal time. Yes, "get a good night's sleep" is real advice. The kind I hated when I was 23 and now reluctantly admit was right. If you absolutely cannot relax, allow yourself one thing: re-read the three bullets you wrote about each project on Day 6. Five minutes total. Then close the laptop. ### Day of: the boring playbook Eat something. Drink water, not three coffees. Test your camera, mic, internet 30 minutes early — not 3 minutes early. Have the JD open in a tab. Have your three-bullet project notes open in another tab. Have a glass of water within arm's reach. Stand up and pace for five minutes before the call. Then sit down two minutes early. None of this is glamorous and all of it matters. ![Greenroom's 10-second reset card for interview panic: long exhale, buy time out loud, grab a structure, ground yourself](/assets/blog/pool-calm-checklist.webp) The 10-second reset — keep it in your head for the real thing. ## The things to actively stop doing This is the part nobody puts in checklists, so it ends up being the thing that quietly tanks people. ### Stop doing new LeetCode If you've been grinding LeetCode for weeks, this week isn't where you make up ground. New problems eat time and confidence — you'll inevitably hit one you can't solve and spiral. Instead, redo three problems you already solved well. The point is to reinforce the patterns you have, not to discover gaps you can't close in time. ### Stop reading interview "advice" threads The "I got rejected from [BigCo] and here's what I learned" Twitter thread is going to make you anxious without making you better. Anxiety this week is the enemy. If you must read something, read one thing — a book chapter, a short post you've read before — and re-read it. Familiar inputs are calming. Novelty is not. ### Stop telling everyone you're interviewing Every time you tell someone, your brain logs a tiny social cost if it goes badly. By the end of the week you've manufactured fifteen extra units of pressure for no upside. Tell two or three people who'll actually help. Not your group chat. ### Stop trying to predict the questions The list of "questions Stripe asks for senior backend engineers" you found on Reddit is partially right and mostly outdated. Memorizing it makes you brittle — when the real interviewer asks something adjacent, you panic because you prepared for the wrong thing. Prepare topics, not questions. ## The thing nobody warns you about the last 48 hours Your confidence will fluctuate wildly. At 9pm two nights before, you'll feel sharp and ready. At 7am the day before, you'll feel like you've forgotten how to write a for loop. By 9pm the night before, you'll feel calm again. This is normal. Do not over-interpret the troughs. Your actual skill is whatever you've practiced — it doesn't disappear in a panic spike. The people who do worst in interviews are often the ones who make a decision based on a low-confidence moment — they cram extra material, they pull an all-nighter, they email the recruiter to ask for advice. Don't do this. Trust that the version of you who walks into the interview is the median of the last week, not the worst hour of it. ## If you have less than a week Compress, don't skip. The day-by-day above can collapse into 48 hours: audit your weak spots, re-read your projects, do one mock, take half a day off. The structure is what matters, not the calendar. The thing you cannot compress is the "stop doing new things" part — which is doubly important when the timeline is tight. If you want the "Day 4-3" voice-recording drill but with someone (something) actually responding, that's what Greenroom does. Free tier gives you one full voice mock — use it as your Day 2 dress rehearsal. ## Frequently asked questions ### What should I do the week before an interview? Shift from learning to rehearsing: mock interviews out loud, your two project stories polished, the company's product actually used, and logistics tested. New topics this week add anxiety, not ability. ### Should I cram LeetCode the week before an interview? Light, timed maintenance only — two or three familiar-pattern problems a day. Grinding new hard problems the final week erodes confidence exactly when you need it most. ### What should I do the night before an interview? Stop by early evening, prepare logistics (setup, water, notes), and protect sleep — one bad night measurably hurts working memory, which is what interviews tax hardest. A 30-minute spoken warm-up that morning beats any last-minute study. ### What's the highest-leverage prep in the final week? Spoken mocks under realistic pressure. They surface your actual weak spots while there's still time to patch them — a full Greenroom mock takes 25 minutes and tells you exactly what to fix tomorrow.