Job Interview Tips: A Timeline From Preparation to Follow-Up

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

9 min read

An interview is not a test of whether you can do the job. It is a test of whether a few people, in under an hour, can build enough confidence to bet a headcount on you. It is also two people pretending to be relaxed, and whoever pretends slightly less usually wins.

What follows is organized the way an interview runs: the week before, the first five minutes, the middle, the questions you ask, the close, and the follow-up. Each stage has a different job.

What the interviewer is actually deciding

Behind every question sit three decisions. Can you do the work. Will the team be able to work with you. Will you still be here in two years. Knowing which is in play tells you what a good answer looks like. A hiring manager asking about a failed project is not collecting failures. They are checking whether you can see your own part in an outcome, because someone who cannot is expensive to manage. A peer asking how you handle disagreement is imagining a Tuesday with you in the room.

This is why memorized answers underperform. You cannot predict the wording, and you do not need to if you prepared the raw material instead: six or seven real situations, and a clean explanation of every line on your resume.

The week before: preparation that pays

Preparation is not reading the company homepage the night before. Two or three hours is enough, spread over several days rather than crammed into one evening.

Reread the posting and mark every requirement. Next to each, write the project where you did that thing. Anything left blank is the question you will struggle with.
Learn what the company sells, who pays for it, and who they lose deals to. The revenue model tells you more than the mission statement does.
Read the recent public news: funding, launches, leadership changes, layoffs. One specific reference beats general enthusiasm.
Look up each interviewer. A hiring manager tests capability, a peer tests working style, a skip level tests judgment and whether you will stay.
Write out your own resume story. For every role: why you joined, what you owned, why you left. Hesitation on any of these reads as concealment.
Prepare six or seven situations, not thirty answers. Cover a delivery under pressure, a conflict, a failure, and something you led.
Decide your salary range before you walk in. Deciding it live is how people underprice themselves.

Tip: Practice out loud with a timer, not silently in your head. Spoken answers run longer than you expect, and two minutes is the ceiling for most behavioral answers. If a story takes four minutes, the problem is the setup, not the evidence.

The STAR interview technique, properly

STAR stands for Situation, Task, Action, Result. It is the format most structured interviews are scored against, and it fixes one problem. Asked "tell me about a time when", people tell the story in the order it happened to them, which buries the part the interviewer needs. STAR moves the useful material forward.

Situation: two sentences of context. When it was, how big it was, what was going wrong. Skip the org chart.
Task: what you were responsible for, stated separately from what the team was responsible for. This is the line most candidates blur.
Action: the longest part, and the part being scored. What you did, in order, including the decisions you made and why. Say "I", not "we".
Result: what changed. Give a number if you have a real one. If not, name the observable outcome and what happened as a consequence.

A weak answer rewritten into a STAR answer

Take a question you will be asked in some form: "Tell me about a time you dealt with a difficult stakeholder." Most candidates answer like this.

"We had this client who was really difficult. They kept changing what they wanted and it was frustrating for the team. I have always been strong on communication, so I stayed in touch and kept everything professional, and in the end we delivered and they were happy with it."

Nothing in that is a lie and it still scores near zero. No time, no scale, no sequence of events. Everything is "we", so the interviewer learns nothing about what this person did. The one personal claim is a trait, asserted rather than shown. And "they were happy" could mean anything.

The same events as STAR: "Last spring we were four weeks into a six week website rebuild for our largest retail client, and their marketing director had changed the scope three times. I was the account lead, so the launch date and the margin were mine. I stopped taking change requests by email and set a standing thirty minute call every Monday. Before the first one I priced every outstanding request in days of work and showed which ones pushed the launch past their trade show. Then I asked her to choose what fit inside the original date and what became a paid second phase. She picked three and deferred five, and after each call I sent both teams a one page summary. We launched two days before the trade show, the deferred work became a paid second phase, and we used the Monday format on two other accounts."

Same story, about a minute to say, and now checkable. A timeframe, a defined responsibility, four actions in sequence, a decision with its reasoning, and an ending the company kept using. The interviewer can picture you working, which is all an interview can really give them.

Tip: Never invent a metric to make a Result sound better. Interviewers ask follow-ups and references get called, so a number you cannot defend is worse than none. If you do not have one, say what people could see change: escalations stopped, the backlog cleared, the process is still in use.

The first five minutes

The opening is small talk followed by "tell me about yourself", and it frames everything after. Answer in about ninety seconds: where you are now, the two or three things you have done that matter for this job, and why you are in this room. Not a chronological account from university onward. The interviewer is building a filing system, and this answer decides which folders they open.

Arrive ten minutes early, not thirty. For video, put the camera at eye level, test the microphone an hour ahead, and look at the lens rather than at your own face. Nerves speed your voice up, so slow down deliberately.

The middle: common interview questions and what they test

The wording varies, the underlying questions barely do. Answer the question behind each one.

"Why do you want to work here?" Tests whether you know anything specific about them. Name a product, a market position or a recent decision, and connect it to what you want next.
"Why are you leaving your current role?" Tests risk. Answer forward, about what you want to do, never backward about what went wrong.
"What is your greatest weakness?" Tests self-awareness. Name a real one and the mechanism you use to contain it. A disguised strength reads as evasion.
"Tell me about a time you failed." Tests accountability. Own the decision, not the circumstances, and finish with what you now do differently.
"Tell me about a disagreement with a colleague." Tests behavior under friction, not whether you were right. Say how it resolved and what you conceded.
"Walk me through your resume." Tests whether the document is really yours. Every date, gap and job title needs a one sentence explanation ready.
"What are your salary expectations?" Tests whether you did any homework. Give the range you decided in advance and note that it depends on the full package.

The questions to ask in an interview

The last ten minutes are yours, and asking nothing is read as low interest. Skip anything answered on the careers page, and leave benefits until there is an offer. What the answers reveal matters as much as what the questions signal.

"What does this person need to have done by the end of six months for you to be glad you hired them?" A specific answer means the role is defined and you can be judged fairly. Vagueness means the priorities will move under you.
"Who did this work before, and where are they now?" Separates new headcount from a backfill. How they talk about the last person is how they will talk about you.
"What is the hardest part of this job that is not in the posting?" Surfaces the real friction: a legacy system, a difficult internal stakeholder, a reorg in progress.
"How does the team decide what to work on, and who makes the call when people disagree?" Shows you the actual decision structure, which is often not the org chart.
"What has changed about this team in the last year?" Picks up turnover, new leadership and shifting mandates without asking about any of them directly.
"What are the next steps and the timeline?" Practical, and it gives you a date you can legitimately follow up on.

Tip: Write down two questions during the interview itself, taken from something the interviewer said. Asking about a problem they raised twenty minutes earlier proves you were listening in a way no prepared question can.

The close

Before you leave, ask whether anything about your background gives them hesitation. It is the highest value question in the interview because it turns a silent objection into one you can answer now instead of never. If the answer is "you have not worked in a regulated environment", you get thirty seconds to name the closest thing you have done. Otherwise that doubt goes into the debrief unchallenged. Then say plainly that you want the job. Interest is not obvious from across the table, and it often breaks a tie.

The follow-up

Send a short email within a day, to each interviewer if you have their addresses. Three to five sentences: thank them, name one specific thing from the conversation, add the sentence you wish you had said. If you fumbled a question, this is your only legitimate chance to fix it. Do not send three people the same text.

If they gave you a date, wait one business day past it. If they gave you nothing, wait a week. Follow up twice, then let it go. Keep interviewing elsewhere the whole time, because a process that feels certain from your side has other candidates in it.

Five ways capable people lose interviews

These come up over and over, and each is fixable.

Rambling. A four minute answer to a two minute question crowds out the questions where you would have scored well, and it makes strong material feel unfocused. Time yourself out loud beforehand and cut the setup, not the evidence.

No examples ready. Candidates who prepared opinions instead of situations answer in the abstract, describing how they generally approach things. Interviewers score specifics. Six real situations cover most of what any panel asks.

Badmouthing a former employer. The interviewer cannot verify your version and has every reason to imagine you describing them the same way in a year. Say what you were looking for that you could not get there, and stop.

No questions at the end. "No, you covered everything" is heard as indifference, and it wastes the only stretch of the interview where you control the topic. Two questions is the floor, and one should come from something said in the room.

Being unable to explain your own resume. Vague dates, a title nobody understands, a six month gap you visibly did not expect to be asked about. That reads as concealment rather than forgetfulness. Read your resume line by line the night before and make sure you can defend every claim on it. The person opposite you is reading from that document.

The short version

Prepare situations, not scripts. Tell them in Situation, Task, Action, Result order and keep them near two minutes. Open with ninety seconds explaining why you are in the room. Answer the question behind the question. Ask what is giving them pause, say you want the job, then follow up once.

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

Get your free ATS score · All articles