ANSWER GUIDE
Why should we hire you?
This is not a request for a personality summary. The interviewer is asking you to connect the job’s outcomes to evidence they can verify — and to do it without repeating your resume.
What the interviewer is actually checking
A hiring manager asking this question is testing four things at once: whether you understand the role, whether your evidence is real, whether you would be a risk to the team, and whether you actually want this job rather than any job. A generic “I am hard-working and passionate” answer fails all four because it gives the interviewer nothing to verify.
The strongest answers sound like a short business case, not a sales pitch. You are not claiming to be better than every other candidate. You are making a specific claim about the work: here is what the role needs, here is what I have done that is relevant, and here is how I would start.
A four-part structure that works in almost any role
- Mirror the outcomes. Read the job description and turn it into two or three results the hire must produce: faster resolutions, reliable releases, accurate close, happier patients, more qualified pipeline. Use the employer’s language, not a list of technologies or traits.
- Prove it with your own work. Pick one or two examples where you personally owned the action. State the situation briefly, explain the decision you made, and give the result. A number helps, but only if you can explain how it was measured.
- Name the difference. What do you bring that is not already assumed by the job description? It might be a rare combination of domain and technical experience, a method you have used in a messy environment, or experience serving the same customer under pressure. Do not claim a difference you cannot evidence.
- Close with relevance, not gratitude. Say how you would apply that to the team’s first 90 days, then ask a question that invites the interviewer to tell you which outcome matters most.
The 30-second version
You need someone who can take a messy reporting request, find the right data, and explain the result to a non-technical stakeholder. In my last role I owned the weekly retention report for a subscription product. I rebuilt the query logic, cut the report from three days to half a day, and walked the growth team through the two metrics that actually predicted churn. The part I would bring here is the habit of checking the definition before building the dashboard. Which of those outcomes is most urgent for this team in the first three months?
Notice what the answer does not do: it does not start with “I am a data analyst with five years of experience”, it does not list every tool, and it does not claim to be the hardest worker. It makes one clear claim, supports it, and hands the conversation back to the interviewer.
The 90-second version, built from the same pieces
For a longer answer, keep the same order but add one sentence of context and one sentence about what you learned. Do not add a second unrelated achievement. A single example developed properly is stronger than three examples that each get four seconds.
The role is about keeping customers when something has already gone wrong. In my last support role I handled the escalations that came in after a failed delivery. I started by separating the customers who needed a replacement from the ones who needed a realistic timeline, because promising the same thing to everyone was making the second group angrier. I wrote three short templates, tracked repeat contacts, and within two months the repeat-contact rate on my queue fell from about one in five to one in eight. What I would bring here is the same approach: diagnose the failure point before writing a nicer apology. What does a good resolution look like on your team?
“Why should we choose you over other candidates?”
This is the same question with the comparison made explicit. The trap is to put other candidates down or to claim you are simply “the best”. The useful move is to define the comparison on the employer’s terms: if the role needs someone who can work with incomplete data and explain it to executives, show evidence of both, and say why that combination is relevant to the work ahead.
You can also acknowledge the trade-off. “Someone with more years in one industry may ramp up faster on the domain. What I bring is experience building the process from scratch in two smaller companies, which is closer to the situation you described.” That is more credible than claiming to have no weaknesses.
“Why should we hire you for this role?”
When the interviewer adds “for this role”, they want the job description reflected back accurately. Pick the top three requirements and map one piece of evidence to each. If you cannot evidence one of them, say so and describe the closest adjacent experience. Do not invent a match; interviewers can usually tell, and a candid gap is less damaging than a bluff.
| Job description says | What to prove | What to say |
|---|---|---|
| “Own the roadmap” | You have made prioritisation decisions with trade-offs | “I cut two features to protect the launch date and explained the trade-off to sales.” |
| “Work with senior stakeholders” | You have changed a decision through evidence | “I showed the finance lead the churn data and we changed the discount policy.” |
| “Comfortable with ambiguity” | You have created structure without a playbook | “There was no onboarding process, so I wrote the first six weeks and tested it with three hires.” |
Fresher or career changer?
Without a long work history, the evidence has to come from projects, part-time work, volunteering, coursework or a previous career. The structure stays the same: outcome, evidence, difference, relevance. The difference is that you explain the transferable mechanism, not just the activity. “I built a booking system for a student society” is an activity; “I diagnosed why people abandoned the booking form and changed the flow, which cut no-shows” is evidence.
For a fuller walkthrough, use the fresher answer guide. If you are applying as an engineer, the software engineer version goes deeper on ownership and technical trade-offs.
The mistakes that cost you the answer
- Repeating the resume. The interviewer already has it. Use one line of context, then spend the time on the decision and the result.
- Talking about traits instead of work. “Hard-working” and “passionate” are conclusions you want the interviewer to reach; give them the evidence instead.
- Using a result you cannot explain. If you cite a percentage, know the baseline, the period and how it was measured. “It improved a lot” is safer than a number you cannot defend.
- Sounding entitled. “I am the best candidate” is a claim about other people you cannot support. Make a claim about the work.
- Forgetting the role. A brilliant answer to a different job is still a bad answer. Mirror the language of this job description.
Follow-up questions to prepare for
- “What makes you different from someone with more experience?” — acknowledge the gap, then name the specific combination you bring.
- “What would you do in your first 90 days?” — connect your evidence to one or two outcomes, not a complete transformation plan.
- “Where do you think you would struggle?” — choose a real, non-core gap and describe the support or habit you would use.
- “Why this company?” — use the company research guide to prepare a specific answer.
- “What questions do you have for us?” — have two ready; the interviewer question guide explains how to choose them.
A 20-minute practice plan
- Write the top three outcomes from the job description in your own words. Do not copy the bullet points.
- Choose two examples. For each, write four lines: situation, your action, the result, what you learned.
- Say the 30-second version out loud twice. Then say it again without looking at the notes.
- Record yourself and listen for filler, apology and length. Cut anything that does not support the claim.
- Ask a friend to interrupt with one follow-up. Answer it in two sentences, then stop.
These guides are written and maintained by MockInterview as original practice material. They are not leaked employer questions, and no employer has reviewed or endorsed them. Sample answers are illustrative; use your own examples and verify role requirements, licensing and local policy with the employer. Last updated 2026-11-03.