Hiring managers ask "Why do you want this job?" for a pretty boring reason: a resume can't prove you want the daily work. They already have your titles. What they can't see on paper is whether you understand the duties, whether your skills map onto them, and whether this role is a next step you can actually explain.
So how do you say all that without sounding like everyone else who memorized something?
Name the work, plus one real detail about the company. Give a result you can defend. Stop talking before you drift into pay, schedule, or how great the "opportunity" is.
What they are listening for
Nobody is scoring charm here. They want proof of three things: you read the posting, you want the responsibilities on it, and you could do them without a long warmup.
Turns out the exact same speech can flop or land on one point, and that point is specificity. "I love your culture" is empty calories. "I want to own the onboarding sequence in your posting because I built a similar flow that cut repeat tickets" hands them something they can actually use.
Charm doesn't survive a follow-up question. Proof does.
If you can't name the work, they'll quietly assume you can't do the work, which is why the answer has to stay about this job, this posting, this set of Tuesday tasks, and not a general hunger to get hired somewhere, because once you slide off the duties they need to staff, they stop hearing you. Not any job.
Build the answer in three parts
Keep it under two minutes. Three beats is enough.
- Role fit. Pull two duties from the posting and connect them to work you already do.
- Impact. One result, with a number if you have a real one.
- Growth. Tie the role to a direction you can defend, not a vague climb up something.
Stop after the third beat. A short close like "That's why I applied here instead of spraying applications" is plenty. Skip the speech about being passionate. Show the fit and let them react.
Research that actually shows up in the answer
Thing is, most weak answers fail before anyone sits down. People skim the listing on the job board, skip the company page, and hope raw energy covers the gap, which it never does, energy without facts just sounds louder and you can hear it when someone has no duty to name.
Work through this the night before:
- [ ] Open the posting you applied to and highlight 2-3 duties you can already do.
- [ ] Skim the company site and one recent product note, launch, or hiring update.
- [ ] Read a cluster of Glassdoor reviews for repeated patterns, not one rant.
- [ ] Check the LinkedIn company page and a few teammates for tools, customers, or phrases they keep repeating.
- [ ] Write one sentence on why this team, not a generic competitor.
The last item, the one sentence, is where it pays off. Most of this takes minutes, not hours.
A tighter Glassdoor pass looks for repeated comments about process, tools, and management and tunes out the isolated venting. Our Glassdoor research walkthrough is built for exactly that kind of read.
Your facts still have to come from the job itself. Practice once out loud. LinkedIn Interview Prep can flag pacing if you already use LinkedIn. A canned script can't do that part for you.
12 sample answers you can rewrite
Don't memorize these. Swap in your company facts and your own numbers.
No metric? Use a clear before-and-after. Do not invent a statistic in the room. A follow-up question will find it.
The bones stay the same every time. Duties from the posting, one proof point, and one reason it's this seat rather than some other one.
1. Entry-level, first full-time role
Use this shape when internships, class projects, or campus jobs are most of your proof.
"I want this job because the posting is built around work I've already started, not a vague interest in the field. In my internship I cleaned messy exports in SQL and built a weekly report the ops team actually used. Your role asks for that same mix of analysis and plain-language updates, and the training path gives me structure while I get faster. I applied here because the job is the work, not a title I hope turns into the work later."
2. Career changer
"I applied because this role uses the parts of my last job I want to keep, and drops the parts I'm leaving on purpose. I spent five years in account work, so I already run discovery calls, write follow-ups, and keep a pipeline honest. Your posting is a sales-development seat with a real product, not a cold-call mill, and that's the shift I planned. I want the quota, the CRM discipline, and a team that coaches the craft."
Say it only if you can point to transferable tasks. Not a vibe.
3. Software or data individual contributor
Name a tool or a problem from their page. Don't recite their whole tech list back at them.
"I want this job because the stack and the problem match what I already ship. I've been writing Python services against messy customer data, and your posting calls out the same mix of APIs, tests, and on-call. I also noticed your team talks publicly about reducing incident noise, which is work I've done by adding better alerts instead of more dashboards. I'm looking for a codebase with real users, and this one has them."
4. Sales
"I want this seat because it's full-cycle work against a product I can explain, not a logo chase. In my last role I ran outbound and close on a similar ACV, and I built a weekly review that kept stale deals from rotting in the CRM. Your posting mentions a defined territory and a sales-engineer partner, which is the support model I work best in. I want to sell this line, in this motion, not 'a sales job.'"
Replace the motion with theirs: inbound, outbound, expansion, whatever the posting actually says.
5. Marketing
If you can't name the channel they need, you're not ready for the room yet.
"I want this job because the work is campaigns with a constraint, not generic 'content.' I've run lifecycle email and landing pages for one product line, and I care about the unglamorous part: the brief, the test, the readout. Your team is hiring someone to own that loop for [product], and your recent launch notes make the audience clear. I applied because I want to be measured on pipeline or qualified signups, not vanity traffic."
6. Remote role
"I want this job because the posting is written for someone who can run work without a hallway. I've worked remote for two years, and I keep a written weekly plan, recorded walkthroughs, and tickets a teammate can pick up cold. Your job lists async updates and documented handoffs, which is how I already operate. I'm not looking for a remote perk. I'm looking for a team that runs that way on purpose."
Prove independence with a habit. "I like flexibility" proves nothing.
7. Manager
Managers should sound like operators. Skip the leadership-poster language.
"I want this job because it's a team-scaling problem I've already lived through. I managed a group of six, set a simple operating cadence, and hired two people into roles we'd been covering with overtime. Your posting is about taking a working function and making it repeatable as you add headcount, not about a founder still doing every review. I want to coach the work, clean up the process, and be accountable for output, not just morale."
8. Internal move or promotion
"I want this job because I already see the gap from the seat next to it. I've been supporting this team for 18 months, I know the backlog, and I've covered the role during leave. The posting matches work I've been stretching into: stakeholder updates, prioritization, the weekly metrics review. I applied because this is the next scope I'm already doing pieces of, and I'd rather do it with the title and the authority."
Only use this one if your current manager won't be blindsided.
9. Why this company, not a lookalike
One contrast is enough. Don't trash other employers while you make it.
"I want this job here because the specialist focus matches the sector I'm doubling down on. Other postings were broader generalist seats. Yours is tied to [industry or product line], and that's the book of work I want. I also read how your team talks about customers on LinkedIn, and it matches the problems I've been solving, not a polished brand story. I chose this posting on purpose."
10. Customer support or success
"I want this job because it's problem-solving with a queue, and that's work I like when it's measured fairly. I've handled live tickets, written help-center updates, and flagged repeat issues so product could fix the root cause. Your posting mentions macros, a knowledge base, and an escalation path, which tells me you care about the system, not just speed. I want to make customers faster and feed cleaner bugs upstream."
Name the tools in their listing if you've used them. If you haven't, say how you learn tools.
11. Mission-driven or nonprofit-style role
Mission without tasks sounds like a donation, not a hire.
"I want this job because the program work is specific and I've done adjacent work, not because the mission page is moving. I've coordinated volunteers, tracked outcomes in a simple spreadsheet, and written the monthly note funders actually read. Your role is program coordination with reporting, which is the job I want to get better at. I care about the cause, and I'm applying because I can do the operations behind it."
12. Mid-career specialist who wants the craft
"I want this job because I want to stay deep in the work, not slide into a generic senior title. Your posting still has hands-on time: reviews, design docs, a clear problem space in [domain]. That's the mix I'm protecting. I've led projects without leaving the craft, and I'm looking for a team that still values that. I applied because the job description reads like the week I want to have."
This one collapses if you can't point to a duty in their posting.
Entry-level vs manager
| Piece of the answer | Entry-level | Manager |
|---|---|---|
| Center of gravity | Hunger to do the listed tasks, plus proof you learn fast | Proof you've already run people, process, or a number |
| Evidence | Internship, project, campus job, or class work with a result | Hiring, coaching, throughput, quality, or revenue you owned |
| Risk to avoid | Sounding like you want any first job | Sounding like you want status more than this team's problem |
Entry-level answers can run shorter. Manager answers still need a job in them, not a biography.
When they turn it into a behavioral question
Sometimes they follow up with "Tell me about a time that shows why this work fits." Now they want a story, not another pitch. The STAR method keeps it from rambling: situation, task, action, result.
Most of your airtime belongs in the action and the result. Keep the setup to a couple of sentences and get moving.
Sales example. Inbound leads sat untouched for two days. That was the situation. The task was cutting response time without dumping junk into the pipeline. The action was a same-day triage in the CRM and a three-question qualify script. Result: we stopped losing the hot ones to competitors, and my manager copied the script. Close the loop: "I want your job because your posting is that same problem at a larger scale."
Remote example. The team was split across time zones. Updates lived in chat. The task was making progress visible without more meetings. The action was moving status into a written Friday note and recording short walkthroughs. Result: handoffs stopped breaking on Monday. "Your role lists async habits, so that's the job I'm choosing."
Write three stories before the interview. You'll reuse them for other questions too.
Answers that stall the room
| What people say | Why it hurts | What to do instead |
|---|---|---|
| "It's a great opportunity" / "I need a job" | Sounds unfocused | Name the duties you want |
| "The salary and the hybrid days work for me" | Sounds transactional | Save compensation for the offer conversation |
| "You are an industry leader" with no role tie | Feels copied from the homepage | Connect one company fact to one task you'd do |
| "I am the best person you will meet" | Reads as swagger, not proof | Offer one result and one way you'd help the team |
If pay is genuinely part of the picture, that's normal. Lead with the work anyway and let money come up in its own conversation.
Mistakes that waste the question
To be honest, the version I hear most is a pile of compliments with no job in it, people name the brand, the mission page, the snacks, a podcast the CEO did, and then they never say which part of the role they'd actually do on a Tuesday, which is the part the hiring manager has to staff.
Other ways to miss:
- Generic enthusiasm with zero research behind it
- Talking only about growth for you, none for them
- Dragging in a complaint about your current boss
- Reciting the posting back with no proof attached
- Going past two minutes
- Inventing a metric because a blog told you to quantify
If you don't know a number, describe the change. "The report went from ad hoc to weekly and people used it" beats a fake percentage every time.
Questions people ask after they draft an answer
Is "Why this job?" the same as "Why this company?" Close, not identical. Company covers mission, product, customers, and how they work. Job covers the duties on the posting. Strong answers hit both in a few sentences. Weak ones praise the brand and never mention the seat.
What if I really do need the paycheck? Almost everyone does. Don't lead with it. They already know you want to be paid, so spend the answer proving you want these tasks. Compensation has its own conversation, later.
How long should this be? About 45 to 90 seconds for the core answer. Two minutes is the ceiling. If they lean in, they'll ask a follow-up, which is the outcome you want.
Should I mention apps I used to apply? Only if it's relevant. "I first saw the role on your LinkedIn posting, then read the team page" is enough. Nobody needs the full tour of your job-search stack.
Open the posting you applied to. Highlight two duties. Rewrite sample 1, 7, or 12 with those duties and one real result from your own work. Say it once out loud and time it. If you can't hear the job in the first 20 seconds, cut until you can.