When an interviewer asks "Why should we hire you?", they want a short, confident summary of how your skills match what this job needs — backed by proof. The strongest answers take 45–60 seconds and follow three beats: what the role needs, the evidence that you've already done it, and what you'd deliver in your first few months. Adjectives like "hard-working" and "passionate" don't count as evidence; a specific result does.
Below: what the interviewer is really checking, a fill-in formula, 12 example answers for different roles and situations, and the phrases to delete before you say them out loud.
What the interviewer is really asking
"Why should we hire you?" sounds like an invitation to brag. It isn't. It's a test of three things:
- Do you understand the job? If your answer could be pasted into any interview for any role, you've failed this part.
- Can you prove you can do it? Interviewers have heard "I'm a fast learner" thousands of times. They remember the person who said "I cut our ticket backlog from 300 to 40 in six weeks."
- Do you actually want this job? A good answer sounds like someone who has thought about the first month in the role, not someone reciting their CV.
It usually comes near the end of an interview, so treat it as your closing statement: the one-minute version of why everything you said earlier adds up.
The formula: Need → Proof → Payoff
| Beat | What to say | Length |
|---|---|---|
| 1. Need | Name the 1–2 things this role most needs. Take them from the job description or from what the interviewer told you. | 1 sentence |
| 2. Proof | One or two specific examples where you've done exactly that — with a number, a before/after, or a named outcome. | 2–3 sentences |
| 3. Payoff | What you'd focus on or deliver early on, in their context. | 1 sentence |
A template to fill in:
"From what you've described, the role really needs [need 1] and [need 2]. That's what I've been doing at [place]: [specific example with a result]. I'd want to bring the same approach here, starting with [a concrete first focus]."
That's it. No list of seven strengths, no life story.
How to prepare your answer in 15 minutes
- Read the job ad and circle the top three requirements — usually the first bullets, or the ones that appear twice.
- For each one, write down a real example where you did it. Add a number if one exists: time saved, tickets closed, revenue, students, complaints, errors. If you don't have a number, use a concrete before/after ("the report used to take a day; now it runs on Monday morning").
- Pick the two strongest pairs (requirement + example). That's your answer.
- Add one sentence about your first months: what you'd look at, learn or fix first.
- Time it. If it runs past 60 seconds, cut the setup, not the result.
If you've prepared STAR stories for behavioral interview questions, you already have the raw material: this answer is the highlight reel of those stories.
12 example answers (by role and situation)
Read these for structure, not for copying. The details in yours have to be true and yours.
1. Customer support specialist
"This role is about solving problems on the first contact and keeping customers calm while you do it. In my current job I handle about 60 chats a day, and I rewrote our five most-used reply templates so customers got the fix in the first message — our reopened tickets dropped noticeably within a month. I'd love to bring that to your team, starting with the questions customers ask most."
Practise more: customer support interview questions.
2. Software engineer
"You need someone who can ship features in an existing codebase without breaking what's already there. At my last company I owned our payments service: I added a retry queue that ended a weekly incident we'd had for a year, and I wrote the tests that made it safe to change. I'd start by learning your release process and picking up a small bug end to end in my first week."
Practise more: software engineer questions.
3. Data analyst
"It sounds like the team needs reporting people actually trust and use. I rebuilt our sales dashboard after finding three different definitions of 'active customer' in use — I got finance and sales to agree on one, and the Monday meeting now starts from the same numbers. I'd want to do the same here: understand which numbers drive decisions, then make sure they're right."
Practise more: data analyst questions.
4. Sales representative
"You're looking for someone who can build a pipeline, not just close what comes in. Last year I booked most of my own meetings through outbound calls, and I learned to change my opener based on which ones actually got a second call. I'd start by learning why your best customers bought from you, and build my outreach around that."
Practise more: sales interview questions.
5. Digital marketer
"The role needs someone who can run campaigns and tell you honestly what worked. I managed paid social for a small online shop on a tight budget; by cutting the two ads that brought clicks but no sales, we spent less and sold more. I'd begin with an audit of where your current leads really come from."
Practise more: digital marketer questions.
6. Project coordinator
"You need projects to finish on time without the team feeling chased. I coordinated an office move for 40 people with a shared checklist and a 10-minute daily stand-up, and we moved over one weekend with no lost equipment. Here, I'd start by mapping every open project's next deadline and owner so nothing surprises anyone."
Practise more: project coordinator questions.
7. Teacher
"You're looking for someone who can manage a mixed-ability class and show progress. Last year I grouped my Year 8 students by the skill they were missing rather than by overall level, and most of the students who'd been behind caught up by the end of term. I'd want to get to know my classes quickly through short, low-stakes check-ins."
Practise more: teacher interview questions.
8. Retail store associate
"In a busy store you need people who keep the floor tidy and still notice customers. On Saturdays at my current job I'm usually the one restocking and serving, and I suggested moving our most-asked-for items near the till, which cut the 'where is…' questions. I'd bring the same eye for small fixes here."
Practise more: retail interview questions.
9. Recent graduate (no full-time experience yet)
"The job needs someone organised who learns new tools fast. For my final-year project I built a survey, collected answers from over 200 students and presented the findings to the university's student services team, who changed two of their opening hours as a result. I don't have years of experience, but I can show you work I've finished, and I'd put the same effort into learning your systems."
Tip: proof doesn't have to come from a job. Projects, volunteering and part-time work all count — and you can prove a skill with a short assessment instead of a line on your CV.
10. Career changer
"This role needs strong communication with customers and careful record-keeping. I've done both for eight years as a nurse — explaining difficult news clearly and keeping notes that other people relied on. I've spent the last six months learning [the software you use], and I'd bring a calm head and a habit of writing things down properly from day one."
11. Internal candidate (applying for a promotion)
"You need someone who already knows how this team works and can start improving it without a long ramp-up. For the past year I've been the person new hires come to — I wrote our onboarding checklist, and new starters now handle tickets on their own sooner. I'd want to use this role to fix the handover gaps between our shifts."
12. Returning after a career break
"The role needs someone reliable who can handle several things at once. Before my break I ran the front desk of a busy clinic, managing bookings for six doctors. During my time away I kept my skills current with an online course in [system], and I'm ready to commit fully. I'd start by learning your booking process inside out."
Delete these phrases before you say them
The corporate buzzword problem is worst in this exact answer, because nerves push people toward safe-sounding clichés.
| Instead of… | Say what it looks like |
|---|---|
| "I'm a hard worker." | "I covered two colleagues' accounts for a month without anything slipping." |
| "I'm passionate about…" | "I've been doing this in my spare time for two years — here's what I built." |
| "I'm a team player." | "I set up the shared tracker the whole team now uses." |
| "I'm a fast learner." | "I learned our new CRM in a week and wrote the guide for everyone else." |
| "I think outside the box." | "I suggested we stop sending the weekly report nobody read, and replaced it with a 3-line summary." |
| "I'm a perfectionist." | (Just don't.) |
Common mistakes
- Comparing yourself to other candidates. You don't know them. "I'm better than the others" sounds arrogant and is unprovable. Talk about the job, not the competition.
- Reciting your CV. They've read it. Pick two things, not ten.
- Going generic. If your answer would work for any job at any company, it isn't an answer to this question.
- Making it about what you'll get. "It's a great step for my career" is true, but it answers a different question. Lead with what they get.
- Rambling. Past 90 seconds, people stop listening. Aim for under a minute.
Other ways they might ask it
The same answer works, with small adjustments, for:
- "What makes you the right person for this role?"
- "Why are you a good fit?"
- "What can you bring to the team?"
- "What makes you stand out from other candidates?" (still don't compare — just make your proof specific)
- "Sell yourself in one minute."
What if you don't meet every requirement?
Almost nobody does. Lead with the requirements you clearly meet, then name the gap honestly and show how you close gaps: "I haven't used Salesforce, but I learned HubSpot in two weeks at my last job, and I've already started the Salesforce basics course." Honesty plus a plan beats pretending.
Practise it out loud
Reading a good answer and saying one are different skills. Write your Need → Proof → Payoff answer, then say it against the pitch timer until it fits in a minute without sounding memorised. Then practise the other questions for your role on Provitude's interview practice — privately, with a checklist that shows what your answer covered.
Frequently asked questions
How long should my answer to "Why should we hire you?" be?
About 45–60 seconds — roughly 100–150 words spoken. Long enough for two specific examples, short enough that the interviewer is still listening at the end.
Should I mention salary or benefits?
No. This question is about what you bring to them. Save pay for when they raise it or when you get an offer.
Is it OK to say "I don't know why you should hire me"?
No — even as a joke. If you genuinely aren't sure, use the formula: name what the job needs and one real example where you did it. That's enough.
Can I use the same answer in every interview?
Keep the structure, change the content. The "Need" part has to come from each specific job, or the whole answer falls flat.