📝Blog Post

How to Prepare for a Job Interview: A Timeline

Talent Cat✍️ Talent Cat
•📅 February 27, 2026

In short

  • Spread your preparation over a week. Each day gets one task, so nothing piles up the night before.
  • Research the company and the role first, then map one real example to each key requirement in the job ad.
  • Practise your answers out loud before the day. Thinking them through silently is not the same.

Contents

  • The timeline at a glance
  • As soon as the invitation arrives
  • One week before: research the company and the role
  • Five days before: map your examples to the job ad
  • Three days before: practise out loud
  • Two days before: prepare your questions
  • The day before: logistics
  • On the day
  • FAQ

The invitation arrives on Monday. The interview is next Tuesday. Most people spend the first few days doing nothing, then try to do everything on Monday night.

This guide shows how to prepare for a job interview step by step, as a timeline. Each step has a day and a clear output: a page of notes, a list of examples, a set of questions. By the time the interview starts, the work is already done.

How to prepare for a job interview: the timeline at a glance

Use this as your plan. If you have less than a week, compress it, but keep the order.

WhenMain taskWhat you have at the end
Invitation dayConfirm and ask about the formatDate, format, names of the interviewers
One week beforeResearch the company and the roleOne page of notes
Five days beforeMap your examples to the job adOne example per key requirement
Three days beforePractise out loudAnswers you have said, not just thought
Two days beforePrepare your questionsThree to five questions for them
The day beforeLogisticsRoute or tech checked, documents ready
On the dayWarm up and arrive calmA short review, no new material
Preparation works when every day has one task and one result.

As soon as the invitation arrives

Reply quickly and confirm the date. Then ask the questions that shape the rest of your preparation:

  • Is it on site, by video or by phone?
  • Who will you speak to, and in which role?
  • How long will it take?
  • Is there a task, a presentation or a technical part?

Asking these is normal. A short, polite email is enough. The answers decide how you spend the next week: a presentation needs slides, a panel interview needs examples for different listeners, a technical round needs practice of its own.

Save the job ad now as a file or a copy. Ads are sometimes taken offline once the interviews start, and you will need the text all week.

One week before: research the company and the role

Research is not about memorising facts. It is about being able to explain why this company and this role make sense for you.

What to look for

Spend an hour or two and write down what you find on one page:

  • What the company sells, and to whom
  • Recent news: a product launch, an expansion, a new office
  • How the company describes itself: values, mission, the tone of its careers page
  • The team you would join, if it is visible
  • The interviewers' roles, for example on LinkedIn

You do not need everything. You need enough to answer "Why do you want to work here?" with something only this company could hear.

Read the job ad line by line

Go through the ad with a highlighter. Mark three kinds of lines:

  1. Must-have requirements: skills and experience they name directly
  2. Tasks you will do in the first months
  3. Signals about the culture: words like "independent", "fast-paced" or "close collaboration"

The must-haves become the core of your preparation. The interviewer will very likely ask about them, directly or through a behavioural question.

Five days before: map your examples to the job ad

This is the step most candidates skip. They prepare answers to common questions. Then a question comes from the job ad and they have no example ready.

Take each must-have from the ad. Next to it, write one real situation from your experience where you showed it. Use the STAR structure: Situation, Task, Action, Result.

The mapping below is illustrative, for a project coordinator role. It is not taken from a real candidate.

Requirement in the adYour exampleResult to mention
Coordinating several stakeholdersOffice move with IT, facilities and three teamsMove done over one weekend, no lost workdays
Working with tight deadlinesTrade fair materials after a supplier cancelledFound a new supplier, delivered two days before the fair
Clear written communicationWeekly status email for a project with remote teamsFewer follow-up questions in meetings

One example can cover two requirements. That is fine. What matters is that no must-have is left without a story.

Also prepare short answers to the questions that come up in almost every interview: "Tell me about yourself", "Why this role?", "Why are you leaving your current job?" and "What are your salary expectations?" Write down key points, not full scripts.

If a requirement in the job ad has no example next to it, that is where the interview will catch you.

Three days before: practise out loud

Reading your notes makes you feel prepared. Saying the answer out loud shows you where you are not. You find out where you ramble, which example takes too long, and where you forget the result.

Practise in three rounds:

  1. Say each answer out loud once, alone. Time it. Most answers work best at around one to two minutes.
  2. Record yourself or ask someone to listen. Notice where you lose the thread.
  3. Answer questions you did not prepare, so you get used to adapting an example on the spot.

A mock interview is a good way to do round three. In a TalentVP mock interview you enter the job title, your seniority and the job ad. You then answer seven questions: an opening question, five questions generated from the job title, your seniority, the ad and your earlier answers, and a final one where you ask the questions. You can type or speak. Spoken answers are transcribed and assessed as text.

After each answer you get a score from 0 to 100, strengths, areas to improve and a model answer, structured as STAR, PAR or CARL. Interviews run in English, German or Turkish, and a free account includes one mock interview.

Two days before: prepare your questions

Most interviews end with "Do you have any questions for us?" Having none can come across as low interest. Good questions show that you have thought about the job itself.

Prepare three to five, so you still have some left if a few get answered during the conversation. Questions that usually work:

  • What would success look like in this role after six months?
  • What is the biggest challenge for the team right now?
  • How does the team work together day to day?
  • How is feedback given, and how often?
  • What are the next steps in the process, and when can I expect to hear back?

Leave salary, holidays and benefits for later in the process, unless the interviewer brings them up.

The day before: logistics

The day before is for logistics, not for learning new material. Check each point once:

  • On site: the address, the route, how long it takes, where to go at reception. Plan to arrive about ten minutes early.
  • By video: the link, the app, camera, microphone, light and a quiet room. Test them at the time of day the interview will happen.
  • Documents: your CV, the job ad, your page of notes and your questions, printed or open in one place.
  • Clothes: chosen and ready. When in doubt, dress one level more formal than the team does day to day.
  • Contact: the phone number of your contact person, in case you are delayed.

Then go through your mapping table once and stop. Sleep is part of the preparation.

On the day

Keep the morning simple. Eat something, leave early, and read only your one page of notes and your questions. Do not try to learn anything new.

A few minutes before the start, say your answer to "Tell me about yourself" out loud once. The first question is often an opener, and a smooth start makes the rest easier.

During the interview, it is fine to pause before answering. If a question is unclear, ask what exactly they mean. If an example runs long, finish with the result and stop.

After the interview, write down which questions came up and what you would answer differently. Those notes are the start of your preparation for the next round.

The interview itself is not the moment to prepare. It is the moment to use what you prepared.

If you want a list to print and tick off, our job interview preparation checklist puts every step on one page.

Frequently Asked Questions

How long should I prepare for a job interview?

About a week is comfortable for most roles. If you only have two or three days, keep the same order: research, examples, practice out loud, questions, logistics. Spend less time on each step instead of skipping one.

What should I research about the company?

What the company sells and to whom, recent news, how it describes itself, and the roles of the people interviewing you. The goal is to explain why this company and this role fit you, not to recite facts.

How many examples should I prepare?

At least one for each must-have requirement in the job ad. Five to seven well-prepared examples usually cover most questions, because one example can often show more than one skill.

Should I memorise my answers?

No. Memorised answers sound stiff and break when the question is phrased differently. Prepare key points and an example for each, then practise saying them out loud until the structure feels natural.

🌍 Read this guide in: English | Deutsch | Türkçe

🔗 Related Posts