Three strengths that match the posting. A result on each one. A read on this team's next problem, like you've already been staring at it. That is the honest test when they ask why you're the best person for the job. Nobody in the room is scoring polish. They need a fit they can defend to their own boss after you leave.
How do you say it out loud without turning into a walking resume?
Steal the skeleton, not the sentences. A plain version works almost anywhere: "I fit this role because I drive results, I coach people through messy work, and I adapt when the plan breaks. At my last job I cut cycle time 30% with a training sprint I can run here in the first 90 days."
Stuffed-with-targets postings want numbers instead of adjectives. Hit the STAR beats fast. Inbound stalled. You owned the turnaround. You rebuilt outreach around the accounts that actually converted. Closed revenue rose 25% in a quarter. Close the loop on the diagnostic habit behind that fix, because that is what their pipeline needs.
Culture screens run shorter still. The posting stresses async work and shipping without a lot of ceremony. You've done exactly that across time zones, handed work off faster than the baseline, and still mentored two juniors along the way. Week one help, not month three.
None of those lines get recited word for word. Your numbers go in. The shape stays.
What they actually want when they ask this
A resume can't show judgment. That is why the question exists. Thing is, they are not asking you to rank yourself against people you've never met. Half the time they haven't met those people either.
Proof you read the posting. Proof you know where you'd add value. Proof you can say it without fluff. "I'm a hard worker and a team player" dies on contact. Specifics survive.
How to build an answer that doesn't sound canned
People freeze because they try to invent a speech in their heads. Don't. Assemble it.
- Paste the job description somewhere and highlight the three skills that repeat.
- Match each skill to one real story from your work, not a personality trait.
- Put a number on every story: time saved, revenue, quality, retention, speed, error rate.
- Sketch the story as Situation, Task, Action, Result, with most of the words on Action.
- Name one pain in the posting and say how you'll touch it in the first 90 days.
- Read the company's latest product, funding, or hiring news so one sentence sounds local.
- Rehearse out loud until you can run it in about 60 to 90 seconds without looking down.
No speechwriting lives anywhere in that list. Eight skills on the posting? Let the long tail go. Three is memorable. Interviewers retain a triad. They forget a catalog.
Use STAR, but don't drown them in setup
MIT Career Advising treats behavioral questions as a test of past behavior, not vibes, and their worksheet splits the airtime that way: a small share for Situation, a sliver for Task, the bulk for Action, and a clean close on Result. Dartmouth's career office lands on the same practical advice from a different angle. Write 3 to 5 adaptable stories, use "I," and stay specific.
Turns out the common failure runs backwards. A candidate spends two minutes on office politics, then rushes the result, and the result is the only part that gets scored. Context matters just enough to keep the interviewer from getting lost.
Two sentences of Situation, max. Your job in one more. Walk through the steps you took. Land on a number and name what you'd repeat here.
Time gets tight on sales and exec screens. Pick three strengths and hang one proof off each. Nursing, teaching, and engineering interviews usually want the story.
Sample answers you can tailor by role
Tech. "I'm the right hire because I ship, I debug with other people, and I work fine without a shared office. Last year I found a slow path in our app and cut load time about 40%. I also ran design reviews across two time zones, which matches how your team already works." If they ask for more, add a product story: you led a UI pass, satisfaction scores moved, and you can explain the tradeoffs instead of just naming tools.
Sales. Hustle only counts if you can point at a quota. "I closed 150% of plan by working the accounts that already trusted us, not by spraying more emails. Slow months didn't scare me. When inbound dried up, I rebuilt the pipeline 25%. Your team lives in an always-on cycle. So do I."
Marketing. Lead with a campaign, not "I'm creative." "I built a video-and-social run that grew followers about 50%, and I can show the spend behind it. I also sat with sales on the brief, so the work wasn't pretty and useless. Your brand is digital-first. That's the work I already do."
Nursing. Empathy without a patient story sounds fake. "I stayed with high-acuity cases when the floor ran short, and I kept up small, calm check-ins that families mentioned later in feedback. A heavy shift doesn't stop me from teaching a newer nurse the why, not just the task. That's the load your unit described."
Teaching. Name the school, not teaching in the abstract. "Your STEAM block and device setup are why I applied. I used similar tools to get students to a state fair project, and I like the way your staff plans in teams. I won't need a semester to learn how this building runs."
Executive. Go past the CV. "You don't need another generalist who recites strategy. You need someone who has already sat in a growth stall like yours. I led a 30% revenue lift by cutting work that didn't serve the core offer, and I'll spend the first 90 days on the two constraints I already see in your public numbers."
None of those lines work if the number isn't yours. Borrow the logic. Keep your facts.
Generic answers vs tailored ones
One comparison settles the argument faster than any rule of thumb.
| Type | What it does | Where it breaks | Use it when |
|---|---|---|---|
| Generic triad | Easy to remember under stress | Sounds like every other candidate | Early screens, career changers, thin time |
| Tailored story | Shows you read this job | Takes homework | Final rounds, competitive U.S. roles |
Similar titles in the room? Tailoring is what separates them. The generic triad is a backup, not a strategy.
STAR versus a three-point close
| Frame | Strength | Weakness | Best fit |
|---|---|---|---|
| STAR | Proves behavior with a plot | Runs long if you love setup | Tech, nursing, teaching, ops |
| Three strengths | Fast, sticky | Thin if you skip proof | Sales, exec, phone screens |
STAR fits when they ask for an example. Three strengths fit when the question is why you, period. Mix them if you want: name three strengths, then back one with a STAR story.
STAR story checklist before you walk in
- Situation: one or two sentences, no villain monologue
- Task: your job, not the team's entire year
- Action: steps you took, with "I," the tools, and the tradeoffs
- Result: a number, plus what you'd do again here
- Spare stories: at least three, so one flop doesn't strand you
Bullets beat scripts. A script sounds like a script.
Where job apps actually help with this question
If you already hunt roles on LinkedIn, run Interview Prep on the questions that sit next to this one: "Why should we hire you," strengths, and "Tell me about yourself." The writing box in there is short on purpose. That constraint is useful. It stops you from rambling.
to be honest, the bigger miss happens earlier, people spend weeks polishing a resume for an applicant tracking system and then walk into the interview and answer this question with a totally different vocabulary than the posting used, which is a waste of the pass they already earned. If the ATS passed you for "pipeline hygiene" or "care coordination," those phrases belong in the interview too. Same skills. Spoken English. Not keyword stuffing.
Resume builders help you find metrics hiding in old reviews. Job boards help you steal language from adjacent postings without copying a single sentence into your mouth. None of that replaces a story you can defend.
Mistakes that make a good candidate sound average
| Mistake | Why it lands badly | Fix |
|---|---|---|
| Traits with no proof | Sounds unprepared | Attach one number |
| Ranking yourself vs the field | You haven't met the field | Rank your fit to their problems |
| Dumping your whole CV | They already have it | Pick three threads |
| Admitting you micromanage | They hear risk | Talk about checklists and quality bars instead |
| Skipping the close | The answer just stops | Add a 90-day picture |
Don't confess a weakness and call it honesty. This question is a sales question. Stay true. Stay relevant.
Then there's the candidate who over-explains the company, reads half a press release out loud, drops a value word from the careers page, and never once connects any of it to a thing they actually did, which is how you end up with two minutes of talking and zero evidence.
FAQ
What if I don't have a 30% story? Use a smaller number you can actually defend. Tickets closed, hours saved, a class that improved, a shift that didn't fall apart. Fake precision is worse than a modest fact.
What if I'm changing careers? Map the transferable work. Teaching becomes training. Clinic chaos becomes ops. Campus clubs become stakeholder management. Then say the gap out loud and explain how you'll close it in 90 days.
Should I mention other candidates? No. You don't know them. Talk about the job.
How long should this be? About a minute. If they lean in, add the STAR story. If they nod and move on, stop.
Open the posting tonight. Circle three skills. Write one STAR story in bullets. Say it once into your phone, then once into LinkedIn Interview Prep if you've got it. That's enough homework to walk in sounding like yourself, only clearer.