This is your closing argument, and it's a gift. The interviewer is handing you the chance to make the case for yourself directly. Yet most people waffle through it, either too modest to actually sell or too vague to be convincing. A strong answer is specific, confident, and aimed precisely at what this role needs. It's the moment to connect the dots between their problem and you being the solution.
What the interviewer is really looking for
They're testing: Do you understand what the role actually needs? A generic "I'm hardworking and a team player" shows you haven't thought about this job. A targeted answer shows you have. Can you make a case without arrogance? They want confidence backed by evidence, not empty bravado or, at the other end, mumbling modesty. Have you connected yourself to their problem? The best answers frame you as the answer to a need they have, not just a list of your qualities in a vacuum. This question rewards people who've done the work of understanding the role and can articulate their fit crisply. It punishes both the arrogant and the vague.
The structure: Their need, your fit, your evidence
- 1
Name what the role needs
Show you understand the actual challenge or requirement, from the job spec and the conversation.
- 2
Position yourself as the fit
Connect your specific strengths and experience to that need.
- 3
Back it with evidence
A concrete result or example that proves it, not just a claim.
Three beats: Keep it confident and tight, around 30 to 60 seconds. This is a pitch, not a monologue. You're making a clear, evidenced case and then stopping.
Example answers
For a growth marketing role at an early-stage company
You've said the big challenge here is building paid acquisition from scratch, with no existing playbook. That's exactly the kind of thing I've done. At my last company I built the entire content and lifecycle channel from nothing, and grew organic traffic from 12,000 to 140,000 monthly sessions in under three years. I'm comfortable in the ambiguity of a blank page, which is what this role needs, and I'd rather build something than optimise something that already works.
For a project manager role
From our conversation, the thing that matters most here is landing complex cross-team projects where the PM doesn't have direct authority over the people involved. That's the core of what I do. My last role was migrating a billing system across engineering, finance, and support, and the hardest part wasn't the tech, it was getting three teams with different priorities aligned. We shipped early with no outages. I think I'd hit the ground running here because it's the same shape of problem.
Why these work
Each starts by naming the role's actual need, not a generic pitch, connects specific experience to it, and closes with concrete evidence. They're confident but grounded in proof, and they're tailored. You couldn't paste either answer into a different job.
Common mistakes
- The generic list. "I'm hardworking, reliable, and a team player." True of everyone, convincing of no one, and not aimed at the role.
- No evidence. Claiming strengths without a single concrete result to back them.
- Arrogance. "I'm the best candidate you'll ever see." Confidence is good. Bravado without proof is off-putting.
- Excessive modesty. Mumbling "well, I'd do my best." This is the moment to sell, so take it.
- Not connecting to their need. Listing your qualities in a vacuum instead of tying them to what the role requires.
Knowing the answer isn't delivering it.
Have the actual conversation with a video AI interviewer that listens, follows up on what you say and pushes back — then writes you an honest coaching report.
Frequently asked questions
What's the best way to answer "why should we hire you"?
Name what the role actually needs, position your specific strengths as the fit, and back it with a concrete result. Keep it to 30 to 60 seconds. It's a confident, evidenced pitch aimed precisely at this job, not a generic list of your good qualities.
How do I answer "why should we hire you" without sounding arrogant?
Ground every claim in evidence. Confidence backed by a concrete result ("I did X and it produced Y") reads as credible, not arrogant. It's unsupported bravado, claims with no proof, that comes across badly.
What should I not say when asked why they should hire me?
Avoid generic lists like "hardworking, reliable, team player" that apply to everyone, claims with no evidence, and false modesty. Also avoid answers that could fit any job, because the whole point is to show you understand and fit this role.