How to Prepare for an Interview in One Week — A Day-by-Day Plan
A week is enough — if you spend it on the right things. Most candidates burn their remaining days re-reading generic question lists and cramming facts they'll never be asked. The candidates who improve fastest do three things instead: they extract the real interview topics from the job posting itself, they practice answering out loud rather than in their head, and they spend disproportionate time on their weakest area instead of polishing what's already fine. This guide answers the questions people actually ask with seven days on the clock, in roughly the order you'll face them.
Interview questions to expect
What should I do first with 7 days left?
Re-read the job posting like an exam syllabus, not an ad. Every responsibility line implies interview topics: 'own the roadmap' means prioritization frameworks and trade-off stories; 'work cross-functionally' means stakeholder-conflict questions. Write down the 5-8 topics the posting implies, then rank yourself honestly on each. That ranked list IS your week — everything else in this guide hangs off it.
Should I research the company or the role first?
Role first, company second. Interviewers forgive a thin answer about company history; they don't forgive a candidate who can't connect their experience to the job's actual responsibilities. Cap company research at an hour: product, business model, recent news, and one sharp question per interviewer. Depth on the role's topics beats breadth on trivia.
How do I find my weak spots fast?
Answer one question per topic out loud, cold, and notice where you ramble, stall, or reach for filler. That discomfort map is more accurate than any self-assessment. Spend days 2-3 drilling the two worst topics only — a weak area moved from failing to solid changes your outcome more than a strong area polished further.
How many hours a day should I prepare?
Two focused hours beat six distracted ones. Practice retrieval (answering questions) rather than recognition (re-reading notes) — retrieval is what the interview tests. If you have a full-time job, one hour of out-loud practice in the evening, every day, compounds fast over a week.
When should I do my first mock interview?
Day 4 at the latest — early enough that what it exposes is still fixable. A mock's value is the gap it reveals between how good your answers feel in your head and how they sound out loud. Record it or use a tool that gives you a transcript: filler words, buried conclusions, and 4-minute rambles are invisible until you see them written down.
How do I practice behavioral questions in a week?
Build a story bank of 5-6 real experiences covering conflict, failure, leadership, ambiguity, and initiative — most behavioral questions are one of these wearing different clothes. Practice telling each in under two minutes with the result stated first, then the how. Re-using stories across questions is expected; interviewers care about the quality of the reflection, not the variety of the anecdotes.
What if the role has a technical or case component?
Do at least two full timed run-throughs, not fragments. The failure mode in cases and technical rounds is pacing, not knowledge — candidates spend eight minutes on setup and starve the analysis. A timed run teaches you what five minutes of case time feels like; no amount of reading does.
What should the day before the interview look like?
One light mock in the morning to stay warm, then logistics: confirm the time and timezone, test your camera and mic for remote loops, plan the commute for onsite, re-read your own resume (they will ask about it line by line), and prepare two questions per interviewer. No new topics after noon — late cramming adds anxiety, not ability.
What should I do in the final hours before the interview?
Warm up your voice: answer two easy questions out loud — 'walk me through your background' and your best story — so the interview isn't the first time you've spoken in sentences that day. Review your topic list once, eat something, arrive or log in ten minutes early. Trust the week; the work is already done.
Is one week actually enough to prepare?
For most loops, yes — because interviews test a narrow band: can you structure an answer, do you know your own experience, and have you thought about their specific problems. A focused week covers that band. What a week can't do is build years of missing domain expertise, so aim it at presentation and structure, where a week genuinely moves the needle.
What are the biggest time-wasters to avoid?
Memorizing answers word-for-word (it collapses on the first follow-up), watching interview-prep videos passively for hours, polishing your resume mid-week (that decision already happened), and grinding generic question lists that ignore the actual job posting. Every hour should end with you having said something out loud that you'd say in the room.
How do I manage nerves with so little time?
Nerves shrink with reps, not reassurance. Every out-loud answer you give during the week is exposure therapy — by rep twenty, the format is familiar even if the questions aren't. On the day, remember the base rate: you were invited because they think you might be the answer to their problem. Act like a future colleague discussing the work, not a defendant.
How to prepare
- Anchor the whole week to the job posting — it is the closest thing to a leaked exam paper you will ever get.
- Out loud beats in your head, every day of the week. Reading answers is recognition; interviews test retrieval.
- Spend your hours where you're weakest. Fixing a failing topic changes outcomes more than polishing a strong one.
- Mock early (day 4, not day 6) so what it exposes is still fixable.
- Stop learning new material 24 hours out — the last day is for warmth and logistics, not knowledge.
Practice these questions out loud
Paste the actual job post into Preppara: get a study plan, drill the exact topics, and run a voice mock interview. Your first mock is free.
Try Preppara freeInterview coming up? The Interview Sprint gives you 30 days of everything — one payment, no subscription.