The Complete Job Interview Preparation Guide

Your CV did its job. Someone read it, believed it, and set aside an hour of their week. From here the outcome depends almost entirely on preparation, and preparation is not the same thing as rehearsing answers.

Answers matter, and we cover the ten questions you should expect in a separate guide on interview questions. This one is about everything around them: what to research, how each interview format changes what you do, what the day itself looks like, and what happens after.

Start with the week before

Research with a purpose

Most advice says "research the company", which is useless because it does not tell you what you are looking for. You are looking for three things.

What the business actually sells, and to whom. Not the mission statement. If you cannot explain in one sentence how the company makes money and who pays it, you are not ready. For a listed company, skim the most recent annual report summary. For a startup, read the pricing page and any funding announcement.

What has changed recently. A new product, a new market, a funding round, a merger, a public setback. Recent change is where the hiring need usually comes from, and referring to it shows you looked past the homepage.

Who you will be talking to. Look them up. Their background tells you what they will care about. An interview with the head of finance goes differently from one with the person who will sit next to you, and knowing which you have got is half the battle.

Map yourself to the advert, line by line

Print the job description. For every requirement, write the specific thing you have done that proves it. Where you have nothing, decide now how you will answer, because you will be asked.

This exercise does something more useful than preparing answers. It tells you which two or three things they actually care about, so you can steer toward them rather than waiting to be asked.

Prepare your stories, not your script

Write three to five short accounts of real things you did: something you delivered, something you fixed, something that went wrong, something you led, something you learned. Bullet points only. These get reshaped to fit whatever question arrives, which is why scripts fail and stories do not.

Match your preparation to the format

Phone screen

Usually thirty minutes with a recruiter, and the goal is to be passed on rather than to win the job. They are checking three things: that you are real and coherent, that your salary expectation is not out of range, and that you can leave your current role in a reasonable timeframe.

Take it somewhere quiet, standing up if you can, with the advert and your CV in front of you. Keep answers shorter than you think. Do not negotiate here; recruiters are gatekeepers, not decision makers.

Video interview

Test the actual platform, not just your camera, the day before. Check that the link works, the microphone is the one you think it is, and the browser is not going to ask permission at the worst moment.

Sit with a light source in front of you rather than behind you, put the window with the interviewer's face directly under your camera so your eyeline is close to correct, and close everything that makes a noise. Have water. Have a single page of notes off camera. Tell anyone else at home when it starts.

If the connection drops, do not panic, and do not disappear. Message or email immediately and rejoin. It happens constantly and nobody holds it against you.

In person

Work out the journey and add a buffer. Arrive in the area early and wait somewhere nearby rather than walking in twenty minutes ahead, which is awkward for everyone.

Bring printed copies of your CV, a notebook, and any portfolio material. Dress one notch above whatever the workplace normally wears; if you cannot tell, ask the recruiter, which is a completely normal question.

Be pleasant to whoever is on reception. It is the right thing to do anyway, and their opinion is sometimes asked for.

Panel

Answer to the person who asked, but bring your eyes across the others as you speak. Note names at the start; you will not remember them otherwise, and using them later helps.

Panels usually have one person leading and one who is quieter and evaluating. The quiet one is often the person whose objection matters most, so do not write them off.

Technical or task based

Ask in advance what the format is, what you can use, and how long you have. Nobody will refuse to tell you.

While solving something, narrate your reasoning. The interviewer is assessing how you think far more than whether you arrive at the correct answer, and silence gives them nothing to assess. If you are stuck, say what you would try next and why.

For take home tasks, ask how long they expect it to take and respect that limit. Going far beyond it does not read as commitment, it reads as poor judgement about scope.

The day itself

Eat something. Reread your notes once in the morning and then stop; more rereading past that point turns into anxiety rather than recall.

The first two minutes are small talk, and they matter more than they should. Have something ready that is not the weather.

During the interview: pause before answering, which reads as considered rather than slow. Ask for clarification if a question is vague, because guessing at what was meant is how good candidates give irrelevant answers. Take brief notes, particularly of anything you want to return to at the end.

If you realise mid answer that you have wandered off, say so and reset. "I have gone a bit wide of your question, let me come back to it" is a sign of self awareness, not a failure.

Have questions ready

"Do you have any questions for us?" is part of the assessment. Prepare four, because two will get answered during the conversation.

Good ones are specific and about doing the work: what the first ninety days look like, what people underestimate about the role, how the team decides priorities when everything is urgent, why the role is open. Avoid holiday, hours, and benefits at this stage; those belong at offer.

Afterwards

Send a short thank you email within twenty four hours to whoever you met, or to the recruiter if you do not have addresses. Three or four sentences: thank them, refer to one specific thing from the conversation, restate your interest. It is a small courtesy that a surprising number of candidates skip.

Then write down, while it is fresh, which questions caught you out. That list is the whole reason your third interview goes better than your first.

If you are rejected, it is reasonable to ask for feedback once, politely, and to accept whatever you get, including nothing.

What that message should contain, and templates including one that repairs a weak answer, are in the thank you email after an interview.

Frequently asked questions

How long should I spend preparing?

Two to three hours for a first interview: an hour on research, an hour on mapping and stories, and the rest on logistics. More than that has diminishing returns and tends to make people rigid.

Can I take notes into the interview?

Yes. One page, and do not read from it. It generally reads as prepared rather than uncertain.

What if I do not know the answer to a technical question?

Say so, then reason out loud about how you would approach it or where you would look it up. That answer is usually worth more than a memorised fact.

Should I bring printed copies of my CV?

For in person interviews, yes, two or three. Interviewers frequently do not have one in front of them, and handing one over is a small moment of competence.

How do I explain a gap or a short stint?

Briefly and without apology, then move on. A factual sentence closes the subject; a defensive paragraph opens it.

Is it acceptable to ask how I did at the end?

Asking directly puts people on the spot. Better: "is there anything about my background you have concerns about?" That gives you a chance to answer the objection while you are still in the room.

Before any of this, check what they are reading

Interviewers ask about what is in front of them, so what your CV emphasises decides most of the conversation. If it emphasises the wrong things, you will spend the hour defending them instead of making your case. Tailoring your CV to the job description fixes that, and CvLaunch shows you what an employer's system actually extracted from your file. It takes seconds, it is free, and it needs no sign up.