How to Prepare for an Interview: A Week Out to the Hour Before

By Mustafa Tarabya, founder of CVBooster · Published 2026-08-01 · Updated 2026-09-03

8 min read

Preparation is the only part of an interview you fully control. The conversation itself is improvisation under pressure. Everything before it is homework, and homework is where the gap between two similar candidates gets built. This article covers that part only: the week, the evening, the morning and the hour before anyone sees you.

Most people do not skip preparation. They do all of it in one panicked evening, in the wrong order, and arrive knowing the company mission statement but unable to explain a job on their own resume. Good preparation produces three things: something specific to say about them, something specific to say about you, and a logistics plan boring enough that nothing on the day surprises you.

A week out: research that gives you something to say

Company research fails when it stops at the homepage. The homepage is written for customers and says what the company wishes were true. You want what was written for people who can punish them for being wrong: investors, regulators, users. Two hours across several days beats four the night before.

If the company is public, open investor relations. The latest earnings call transcript says which segment is growing and what management promised. The risk section of the annual report says what worries them.
If it is private: funding announcements, founders on podcasts, published case studies. Case studies are marketing, but they name the real buyer and the real problem.
Product releases from the last quarter: changelog, release notes, app store history, pricing page. What changed recently beats what the product does.
Open roles on the careers page, counted by function. Hiring everywhere means growth or a rebuild. Hiring in one function is a bet, and your role is part of it.
News from the last 90 days with the date filter on: funding, leadership changes, layoffs, a large customer win, a lawsuit.
Each interviewer on LinkedIn: tenure, promoted in or hired in, where they worked before.
The job posting, twice. The order of the bullets is usually the order of priority.
Two competitors by name, and one thing that separates them.

Then convert the reading into speech, because research you cannot say out loud does nothing for you. A usable sentence runs under twenty seconds, contains one fact that was not in the posting, and ends in something that matters for the job: "I saw on the last earnings call that self-serve is the fastest growing segment, and self-serve volume tends to land on support first." Two or three of those is the point of the research. Facts you cannot connect to the role are trivia.

Tip: Write your research sentences down and say them out loud once. Anything that sounds like a press release when spoken is not usable. Cut it and keep the one fact underneath.

A week out: mining your resume for six stories

The second half of preparation is about you, and it is the half people skip. Open your resume and go role by role. For every bullet, ask what actually happened: when, who else was there, what you decided, how it ended. You want episodes, not responsibilities. "Managed the vendor relationship" is a responsibility. "The vendor missed two deliveries in March and I moved half the volume to a second supplier" is an episode.

Six covers almost everything a panel asks. Aim for one episode per slot.

Something you delivered against a hard deadline or a real constraint: no budget, no team.
Something that went wrong where part of the decision was yours. Not one where circumstances were the villain.
A disagreement with a peer or a manager, and how it ended. What you conceded matters more than who was right.
Something you changed or led without formal authority. Few people have this one ready and most interviewers want it.
The hardest thing you have done technically or operationally, explained so a non specialist follows it.
A time you worked with no brief and no owner, and had to set the goal before you could start.

Write each one in note form: the date, the scale, numbers you could defend if someone checked, and the two or three decisions that were yours. Notes, not a script. One episode answers several questions depending on which part you emphasize. The missed delivery is a supplier story, a prioritization story and a conflict story, and you choose in the moment. Told in Situation, Task, Action, Result order, that is structure enough.

Why memorized answers fall apart

Preparing thirty scripted answers feels like more work, so people assume it is better. It is worse. The wording is never what you rehearsed, so you spend the opening seconds fitting the question to the answer you have, and the pause is visible. Memorized text also comes out at a different speed and rhythm than your normal speech, and interviewers hear the switch.

Then there are follow-ups. Structured interviews probe: who disagreed, what you would do differently, how you knew it worked. A script has nothing behind it, so the second question is where it collapses. And under stress nobody recalls thirty rehearsed paragraphs. You can recall six things that happened to you, because you were there.

Prepare for the format, not only the questions

Panel interviews

Ask the recruiter for the names and titles of everyone on the panel. That is a normal request and they usually answer. Map each person to a concern: the hiring manager wants capability, a peer wants to know what working with you is like, someone from another function wants to know whether you will make their life harder. Assign one of your six episodes to each concern, and prepare a version of your background a non specialist can follow.

Sequential rounds in one day

Four conversations in a day is a different exercise. The interviewers compare notes afterward, so telling all four the same story makes your experience look thin when it is not. Spread your six episodes across the schedule deliberately. Ask for the agenda in advance with names, roles, durations and breaks. Eat beforehand. The last conversation is often the most senior one, and it has to sound like your first.

Take-home tasks

Read the brief the day you receive it, even if you will not start for three days. Your questions take a day to come back, and asking good ones early is part of the assessment. Respect the stated time limit. If it says four hours, spend four hours and add one line on what you would have done with more. Gold plating reads as poor judgment about scope, not enthusiasm. Keep notes on the options you rejected, because the next round is usually a walkthrough where someone asks why you chose this approach.

Remote and async first rounds

A recorded video screen or a timed written form is now the common first stage, and it needs its own preparation. There is no interviewer to read, so you supply the structure: state the answer, give the example, stop. If the platform offers a practice recording, use it: seeing your framing once removes most problems. Finish inside the stated time rather than being cut off mid sentence. Notes off camera are fine, but do not read from them, because reading is obvious on a recording. For written rounds, draft in a plain text editor and paste in, since browser sessions time out and take the answer with them.

The day before: logistics that cause the real disasters

Nobody loses an offer over lighting. People do lose the first ten minutes to a link that will not open, and those minutes are expensive. Do this the day before.

Open the actual link on the actual device, signed into the account you will use. Zoom, Teams and Meet handle guest access differently, and some corporate links refuse personal accounts.
Camera at eye level, on books if the laptop sits low. Light in front of you, never behind: a window behind your head turns you into a silhouette.
Check what is behind you, and what is on your screen if you will share it.
Headphones with a microphone. Record thirty seconds and listen back.
Notifications off, phone face down, anyone at home warned.
In person: the real route to the real building at the same time of day, plus parking or the transit connection. Be in the area thirty minutes early, at the desk ten.
Packed the night before: printed resumes, notebook and pen, ID, the job posting, and your contact phone number.

When you cannot tell the dress code, look at the photos on their own site, the careers page, and recent posts from employees. If it is still unclear, ask the recruiter. It is a normal question and they answer it. Failing that, go one step above what you saw, keep it plain, and make sure it fits. Nobody ever lost an offer for looking slightly too plain. For video, only the top half is on camera, but wear the rest anyway, because people stand up.

Tip: Save your recruiter as a phone contact the day before. When a link fails you have about two minutes to reach someone, and that is not the moment to be searching an inbox on a frozen screen.

The morning of

One pass over your notes, not five. Rereading all morning produces recall of your notes rather than of the events, and it raises your nerves for no return. Read your resume out loud once, then the job posting. Eat something, because nerves plus no food is how people get lightheaded at eleven. Block thirty minutes afterward to write down what was asked. If you are working that day, find the private space early. A glass walled room with colleagues walking past is a bad hour.

The hour before

The last hour is for settling, not learning. Nothing you absorb now will come out well.

Restart the machine, plug it into power, close everything you are not using.
Water within reach, notes off camera, phone silent but reachable.
Read your research sentences and the six story headlines once. Headlines only.
Move. Walk ten minutes, or stand up and breathe slowly. Nerves are physical, and sitting still with them makes them worse.
Join the call five minutes early, not one and not fifteen.
Stop preparing.

When the tech fails anyway

Decide now what you will do. If the link fails or the connection drops, message your contact within two minutes and offer to continue by phone. A candidate who fixes it calmly in three minutes is barely remembered. One who vanishes for fifteen is remembered clearly. Test your phone hotspot beforehand, so switching is a decision rather than an experiment. If the interviewer audio breaks up, say so in the first minute instead of guessing at half the question for twenty. And if you are running late in person, call. Arriving late in silence is what costs you.

If you only have one evening

Sometimes the interview is tomorrow, and then the order matters more than the total. Read your resume out loud first. Get the six episodes into note form second. Read the job posting third. Give the company thirty minutes, aimed only at the two or three sentences you can say. Run the tech check last, then stop. The common mistake is spending the whole evening on the company and none on yourself, then freezing on a job you held four years ago.

Tip: If you have time for one rehearsal only, make it your own resume, read out loud, top to bottom. Every date, every title, every claim. The interviewer is reading from that document, and it is the one thing you are guaranteed to be asked about.

Looking for a worked example for your job title? Browse the resume examples by job title.

Get your free ATS score · All articles