Hiring managers ask this because they need a reason to pick you. They've got a stack of similar resumes and one seat to fill. So they're testing fit, proof, and whether you actually read the posting.
A strong reply runs 30 to 60 seconds. That's it.
You name two or three strengths the job genuinely requires. You back each one with a result. Then you point the whole thing at their team.
So what do you say when they lean in?
Not your resume. Pull the live posting off the job board, park it next to your resume in your builder or tracker, and circle the three requirements you can prove. Say them out loud until they sound like you.
Why they ask why they should hire you
Swagger isn't what they're hunting for. The question is really a value test, and they want evidence on three fronts: that you'll do the work, that you'll get along with the people in the room, and that you care about the problems written into the job description. Specific proof only.
LinkedIn's advice on using STAR frames it the same way. Show a situation, what you owned, what you did, and what changed. Keep the ending measurable and concrete.
Vague praise dies fast. Tell them "I'm a hard worker" and you've handed them nothing they can repeat to a hiring committee.
Thing is, people freeze here because the question sounds like a trap. It isn't. It's a prompt to connect proof you already have to needs they already published.
If you applied through an ATS-heavy board, they've already seen your keyword overlap. Now they want the story behind those bullets.
Build your answer in six steps
You don't need a speechwriter. You need a short map from their posting to your proof.
- Copy the job description into a doc and highlight must-have skills, tools, and outcomes.
- Match three of those lines to real work on your resume, whether it's a job, internship, class project, or volunteer gig.
- Attach a number or a clear before-and-after to each match. Only the ones you honestly have.
- Name one specific thing about the company: a product, a customer type, a goal they stated.
- Close with what you'll do in your first months, not a request to be chosen.
- Time yourself and cut anything that runs past a minute.
Practice once while standing. You'll hear filler you never notice on a screen.
Use STAR so the story actually lands
STAR stands for Situation, Task, Action, Result. Big Interview's STAR walkthrough is worth a look if you want extra drills.
Situation and Task stay tight. Action and Result get your time.
Plenty of candidates write these answers like a cover letter. They stack in every tool they've touched and every class they passed, then run out of air right before they name a result the hiring manager could repeat to someone else on the panel. Cut the archive. Keep the result.
Here's a customer-success shape you can steal. Situation: the team was losing enterprise clients in the first 90 days. Task: I owned onboarding for my book of accounts. Action: I built a 14-day check-in cadence and a simple health score the whole account team could see. Result: more of those accounts held through the next quarter, and first-week tickets dropped because people actually used the guide.
One story isn't enough, though. Pair it with two other strengths so you cover the job without lecturing.
Entry-level candidates can STAR a project or an internship. You still need an outcome. "We shipped it" is thinner than "the prototype hit 87% accuracy on more than 10,000 records," assuming that number is real.
Sample answers you can rewrite in your own voice
Don't paste these. Swap the numbers, tools, and company details for yours.
Entry-level or career switch
"I don't have five years in this title, but I can do the work you listed. In my internship I automated a scheduling sheet that cut coordination time about 40% and freed roughly 15 hours a week. My capstone built a recommendation model that hit 87% accuracy on more than 10,000 records. That matches your need for someone who ships small tools fast. I can start that work here on day one."
Keep it under a minute spoken. If you can't, cut a clause.
Sales or account work
"I'm a fit because I already do the hard parts of this job. At my last role I rebuilt the follow-up sequence for at-risk accounts, cut complaint volume 20% in a quarter, and grew revenue on that book. Your posting stresses relationship building and pipeline hygiene. That's the work I want to point at [Company]'s customers."
Tech or data
"Your stack and the line about messy handoffs are why I applied. I set up a CI/CD pipeline in GitHub Actions that brought deploys down to about 40 minutes and cut post-release bugs about 60%. After we moved to remote support, I built a knowledge base that trimmed repeat tickets about 30%. I can do that cleanup on your team without a long ramp."
Leadership
"I've led through messy growth, not just slide decks. I ran recruiting and training for more than 100 people and cut regrettable turnover with coaching, not slogans. I also cleaned an HR workflow that was creating payroll errors, and those errors fell about 30%. You asked for someone who can scale process without freezing the culture. That's the job I want."
Remote-first roles
"I've done this work without a hallway. I keep a quiet setup, camera at eye line, and written updates people can search later. When support went remote, the doc set I built cut repeat tickets about 30%. I also rebuilt a planning process that cut last-minute coverage gaps by 40%. I'll be easy to manage across time zones because I already work that way."
Borrow the shape. Keep your facts honest.
Weak answers compared with stronger ones
The left column sounds like a slogan. The right column gives the interviewer a sentence they can write down.
| Piece | Weak | Stronger | | Opening | I'm the best, and I have an uncanny gift for this. | I've already done the core of this job. I cut complaints 20% with a tighter follow-up loop. | | Proof | I fix problems and I'm a team player. | Payroll errors dropped about 30% after I cleaned the workflow. | | Fit | The pay and the remote policy work for me. | Your focus on [specific goal] matches the systems work I just described. | | Close | So yeah, I'd be great. | I'm ready to run that same play on your book in the first 90 days. |
Tailor it to the posting
Generic answers get forgotten. Open the job description beside your resume and highlight their verbs.
If they say "own the pipeline," don't answer with "I'm good with people." Say how you owned a pipeline.
Turns out the usual miss is lazy reading, not missing skill. You already had the example. You just never plugged it into their language.
If you've drafted with a resume tool or an AI question generator such as Kickresume's interview question generator, treat that output as raw material. Rewrite until it sounds like you at a coffee shop, not a brochure.
One walkthrough. They want someone who can "streamline operations," and you once cut invoice errors 18% in accounts payable. Your line becomes, "Your streamline-operations note is the 18% error drop I got after I rebuilt our invoice checks."
Don't stuff keywords in, either. People hear it.
Mistakes that make you sound risky
People dump their life story. They skip numbers they actually earned, call themselves brilliant, jump straight to salary, never mention the company, and talk past two minutes.
Then there's the version where you list every job you've held since college because silence feels dangerous, even though the interviewer asked about this job, this team, this quarter, and not your whole archive.
Arrogance fails fast. "My supervisor handed me the ugly accounts" lands cleaner than "I have an uncanny ability."
If you don't have a tidy metric, use a before-and-after in plain English. "Managers stopped texting at 5 a.m. because coverage gaps closed" beats a percentage you invented.
You don't need to sound perfect. You need to sound like the lowest-risk hire for this posting.
ATS screens, video calls, and prep tools
Plenty of U.S. applications still hit an applicant tracking system before a person reads anything. The keywords on your resume should show up in this answer too, in normal sentences. You're not tricking a bot on a video call. You're staying consistent.
On video, look at the camera when you hit the result. Keep the room quiet. Leave the job description open in a side window you can glance at, and don't read from a script.
Resume builders, job boards, and interview generators can help you rehearse. To be honest, those drafts only help if you already know which story is true. If a tool invents a gain you never earned, delete it.
Set a timer on your phone. Then stop.
Right before the interview
Open the posting. Write down three requirements you can actually prove, then attach one true result to each.
Stand up and say the whole answer once, under a minute. Cut a sentence if it runs long. Then walk in and give them something worth writing down.