Interview questions are mostly the same twenty questions in different clothing, and each one is asked for a reason. If you know what the interviewer is trying to find out, you can answer the real question instead of the literal one. Below are the questions that come up most, what each is genuinely testing, and worked answers you can adapt rather than recite.
Preparation that actually helps
Do three things before any interview.
Build a story bank. Write out six to eight work situations in detail: a difficult project, a conflict, a failure, a time you led, a time you influenced without authority, a time you handled ambiguity, your proudest result. Most behavioural questions can be answered from a bank of eight if you frame them correctly. This is more efficient than preparing an answer per question.
Structure each story. Situation, task, action, result. Keep situation and task to a couple of sentences and spend most of the time on action, because that is the part being assessed. Always finish with the result, including what you learned if the result was mixed.
Research three things: what the company does and how it makes money, something recent (funding, launch, leadership change, reorganisation), and who is interviewing you. Fifteen minutes is enough and it shows in every answer.
Tell me about yourself
What they want: a two-minute professional narrative that explains how you arrived at this conversation. Not your biography.
Structure: where you are now, the two or three steps that got you here, and why this role is the logical next one.
Example: "I am a data analyst at a subscription media company, where I own retention reporting. I started in finance doing management accounts, which is where I learned SQL to stop waiting on other people for extracts. That turned into a full analytics role, and over the past four years I have moved from reporting into modelling: the churn model I built is now what the commercial team prices against. I am looking for a role where analytics feeds product decisions rather than just commercial ones, which is what drew me to this posting."
Two minutes maximum. Do not start with where you were born.
Why do you want to work here?
What they want: evidence you are choosing them, not applying to everything.
Give one reason about the work, one about the organisation. "The role sits across product and data, which is the combination I have been moving towards. And you are at the point after the Series B where the analytics function is being built rather than maintained, which is the stage I enjoy and have done before."
Avoid pure flattery and avoid answers that are really about you: "great career opportunity", "good for my development".
Why are you leaving your current job?
What they want: to check for red flags and to hear whether you speak badly about employers.
Frame it towards what you are moving to. "I have done the same work for three years and the next step is not available there for a while. I want to own a function rather than a workstream." That is honest and forward-looking.
If you were made redundant, say so plainly: "My role was cut when the team consolidated in January." Redundancy is common and carries no stigma. If you were dismissed, be brief and factual, state what changed, and do not litigate it.
Never criticise a former manager, however deserved. The interviewer has no way to verify it and will assume you would speak the same way about them.
What is your greatest weakness?
What they want: self-awareness and evidence you act on feedback. They are not looking for a confession.
Name something real but not disqualifying, then describe the correction. The correction is the answer.
Example: "I take on too much of the delivery myself when a deadline is close, because it feels faster than explaining it. It cost me on a project last year where I became the bottleneck. Since then I brief work out at the start of the week even when it feels slower, and I have made myself write handover notes as I go rather than after."
Avoid "I am a perfectionist", "I work too hard" and "I care too much". Interviewers have heard them and score them as evasion. Also avoid naming a weakness central to the job.
Tell me about a time you failed
What they want: whether you take responsibility.
Pick a genuine failure with a real consequence, own your part without blaming, and be specific about what changed afterwards.
Example: "I launched a pricing change without running it past the support team. It was defensible commercially, but they got the calls and had no answers, and we spent two weeks on avoidable escalations. I had treated it as a pricing decision when it was a customer communications decision. Every change I have shipped since goes through a one-page brief that names who has to know and when, and support signs it off before launch."
Do not use a disguised success, and do not use a failure so trivial it insults the question.
Tell me about a conflict with a colleague
What they want: whether you can disagree professionally.
Choose a genuine professional disagreement, not a personality clash. Show that you understood the other position, what you did to resolve it, and what the working relationship was like afterwards. Resolution matters more than being proved right, and an answer where you turned out to be partly wrong is often the strongest one.
Where do you see yourself in five years?
What they want: reassurance you have direction and that this role fits it. Nobody expects a plan.
Talk about capability rather than titles. "In five years I would like to be running an analytics team rather than being an individual contributor. Before that I want two or three years of doing the work in a product context, which is why this role interests me."
Do not say you want the interviewer's job, and do not say you have no idea.
What are your salary expectations?
What they want: to check you are in range.
Research the market first. If asked early, deflecting once is reasonable: "I would rather understand the scope first. Do you have a band for the role?" Many employers will simply tell you.
If pressed, give a researched range with your target near the bottom of it, since offers tend to land at the lower end. "Based on what I am seeing for similar roles in this market, I am looking at 55,000 to 65,000, depending on the wider package." Do not give your current salary unprompted; in several jurisdictions they are not allowed to ask.
Why should we hire you?
What they want: a closing argument.
Name the two or three things the role most needs and match yourself to each with evidence. "You need someone who can build the reporting layer from scratch and then explain it to a commercial team that does not trust data yet. I have done both: I built the warehouse models at my current company, and I spent a year running fortnightly sessions with sales until they stopped keeping their own spreadsheets."
Questions on gaps, job hopping and being overqualified
All three are checks for risk, and all three are best handled briefly and without defensiveness.
| Question | Approach |
|---|---|
| You have a gap in 2024 | State the reason in one sentence, then say what you did to stay current and that you are ready now |
| You have moved every eighteen months | Give the reason for each move, ideally showing progression, and be explicit that you are looking for something longer here |
| You seem overqualified | Explain why you want this specific role. A deliberate reason (scope, sector, work-life change) is credible; "I need a job" is not |
What questions do you have for us?
Having none reads as indifference. Prepare five, since some will be answered during the conversation. Good ones are specific and about the work:
- What does success look like in this role in the first six months?
- What is the hardest part of this job that would not be obvious from the posting?
- How does this team make decisions when people disagree?
- Why is the role open?
- What would you want the person in this seat to have changed a year from now?
Save benefits and holiday for after an offer, unless the interviewer opens the topic.
Practical points that change outcomes
- Pause before answering. Three seconds of thought reads as considered, not slow.
- Answer the question asked. Interviewers notice when a prepared story is being forced onto a different question.
- Keep answers to about two minutes. Long answers lose the room and crowd out questions you would have answered better.
- Bring your own examples back to the role. One closing sentence linking the story to their situation does a lot of work.
- Take notes. It looks engaged and it gives you material for the follow-up.
- For video calls, check camera, microphone and lighting beforehand, and look at the lens rather than the thumbnail when making a point.
Afterwards
Send a short thank-you email within a day. Four sentences: thanks, one specific thing from the conversation, one line addressing anything you answered poorly, and a restatement of interest. It rarely wins the job on its own, but it keeps you in mind during a close decision and gives you a chance to repair a weak answer.
If you are called back, expect harder versions of the same questions and more depth on the technical side. Prepare by extending your story bank rather than memorising scripts, and make sure your resume supports everything you say, since interviewers frequently read from it. Keeping the document accurate and current in our free resume builder means you are never explaining a mismatch between what you wrote and what you said. It is also worth checking your LinkedIn profile tells the same story, because most interviewers will have looked at it before you sat down.
