When a hiring manager asks "Why do you want this job?" they're really asking two questions stacked on top of each other:
- Do you understand what this job actually is? (Or are you applying to anything that moves?)
- Are you going to still want it in 12 months? (Or are you using us as a stepping stone to the next thing?)
The candidates who get hired are the ones whose answer makes both questions land cleanly. The candidates who don't are the ones who either give a generic "I love the mission" answer or a transactional "I need a job" answer.
The structure that works is two beats, 45-75 seconds total:
- Beat 1: One specific reason this job, at this company, right now. Something a competitor couldn't claim.
- Beat 2: Why this fits the work you actually want to be doing for the next 2-3 years. Honest, specific, not aspirational filler.
That's the whole pattern. Below: the formula, the things to avoid, 12 sample answers across roles and seniority levels, and the prep work that makes any of these answers land.
The 2-beat formula
Beat 1: Why this job, this company, this moment
The mistake most candidates make is giving a reason that could fit any company. "Great mission." "Strong culture." "Smart team." These describe every employer the candidate would consider — so they describe none of them well.
The fix: pick one of these four anchors and make it specific:
- The product or work itself — "Your billing platform is the only one I've seen that handles dunning for both subscription and usage-based pricing in the same flow."
- The stage — "You're 18 months past general availability. That's the stretch where the product needs the most product-eng iteration, and that's the work I'm best at."
- The team or people — "I read [name]'s post on rebuilding your data platform last year and it changed how I thought about the same problem in my own work."
- The market or customer — "I want to spend the next few years selling into healthcare; I've sold into adjacent verticals and the long sales cycles and procurement quirks are the work I actually like."
The test: read your answer back and ask "could I say this about any of the other companies on my interview list?" If yes, get more specific.
Beat 2: Why this fits what you want to do
The hiring manager is silently calculating: *will this person still be motivated here in a year, or are they going to bounce the moment the next thing comes along?*
The answer that addresses this isn't "I'm so committed and loyal" — it's *concrete continuity*. Show that the work you'd do in this role is something you want to be doing for a meaningful stretch.
Examples:
- "I want to spend the next 2-3 years going deep on backend systems at this scale. I haven't had that at the size of company I've been at."
- "I want my next role to be team lead, not staff IC. This role is the only one I've found at a Series B company with a real team underneath it."
- "I want to keep working on healthcare. I'm not interested in jumping verticals every two years; I want to build deep domain expertise."
This is the part most candidates skip. Adding it makes the answer dramatically more credible.
What "why do you want this job" is NOT asking
Three traps:
- It's not asking "what's wrong with your current job?" Don't lead with reasons you're leaving. That's a different question, and venting about your current employer always backfires.
- It's not asking "what do you want out of this job?" Subtle but important — that's about benefits, growth, compensation. This question is about why this *specific* job appeals.
- It's not asking for a marketing pitch. Don't recite the company's mission statement or values back to them. The interviewer wrote those words; you reciting them tells them nothing.
12 sample answers (by role and situation)
Adapt these to your actual background and the actual job. Don't memorize them.
1. Software engineer (mid-level, joining a startup)
> *"Two things. One: you're rebuilding the data platform from scratch — I read the engineering blog post about that. I spent the last 18 months at [Previous Co.] doing exactly that migration on a smaller team, and the design choices you've made map closely to what I'd want to do again. Two: I've spent four years at a 2,000-person company and want to be at a stage where I'm closer to product decisions, not three layers down from them. A Series B engineering org is that stage."*
2. Senior engineer (joining a large company)
> *"I've spent the last six years at startups, and I want my next role to be at a company that operates real production infrastructure at scale — payment volumes, regulatory complexity, on-call expectations I haven't lived with before. Your platform processes about 4x the volume of any system I've built on, and that's the specific thing I want to spend the next 2-3 years on."*
3. Product manager
> *"I want this role specifically because it's a metric-owning PM job, not a feature-owning one — the JD explicitly says ownership of activation as the success metric across whatever surface area moves it. That's how I worked at [Previous Co.] and the thing I keep noticing in other PM roles I've interviewed for is that the ownership is narrower than what I want. The other thing is that the team has shipped meaningful product velocity in the last six months — I followed [specific product] launch and the cadence is what I'd want to be part of."*
4. Sales (enterprise AE)
> *"Honestly, the segment. You're pushing into enterprise after years of mid-market success, and I love the work of opening a new segment — the deal structure, the procurement chess, the figuring-out-what-plays-work part. I did that at [Previous Co.] when we went from mid-market into enterprise, and it's the part of sales I'm best at. The next 18 months at this company will be exactly that motion."*
5. Designer (product designer)
> *"Two pulls. The team is small enough that I'd be working across product surfaces — not just owning one feature for two years. That's the kind of design role I want for the next phase of my career; I've had the deep-feature-ownership job and want the breadth. And: the way design and engineering work here — the JD mentioned weekly pairing — is the model I've seen produce the best work. I'd much rather be on a team that operates that way."*
6. Marketing manager
> *"The role is to build the demand-gen function from the ground up — paid acquisition, lifecycle, conversion. That's the build I want to be on. I did this at [Previous Co.] from $0 to $400K monthly paid spend over 18 months, and the work of building the engine — choosing the channels, setting the CAC targets, defining the funnel — is what I'm best at. Most roles I look at are tuning an existing function. You're hiring me to build one."*
7. Customer success manager
> *"The specific reason is the customer segment. Mid-market customers in regulated industries operate differently — long security reviews, multi-stakeholder buying committees, renewal politics. I've spent three years on this segment at [Previous Co.] and the standard CS playbook doesn't quite fit. I want to keep working on this customer; I just want to do it at a product that's earlier in its lifecycle and moves faster. Your product is at exactly that stage."*
8. Career changer (consulting → product)
> *"I was a consultant for three years, and the part of the work I kept being pulled toward was product strategy — defining roadmaps, sizing markets, talking to users — rather than the operational pieces. I want to move from advising on these decisions to making them. This PM role is at the right intersection of the consulting work I liked most plus the operational continuity I missed. I'd be making the calls instead of recommending them."*
9. Career changer (teacher → instructional design)
> *"I taught for seven years and the part of the work that energized me most was redesigning curriculum — figuring out what landed for students and what didn't, iterating on materials, designing assessments. Instructional design at a company-scale problem is the same work I loved, applied to adult learners. I'm not leaving teaching because I'm burnt out on education; I'm moving because the part of education I love most is design, and this role is design full-time."*
10. Returning to work (parent returning after a break)
> *"I was a marketing manager for six years before taking four years out to be a primary parent. I kept current — freelance copywriting, certifications, reading. I want to come back to a B2B marketing manager role specifically because that's the work I know how to do well, and I want it at a company at your stage — Series B, post-product-market-fit, building the marketing function rather than running an established one — because that's where I can contribute the most from day one rather than spending six months catching up to how the function already operates."*
11. Entry-level (recent grad)
> *"What pulled me in is that the JD says the role wears multiple hats — analytics, ops, and customer research. I've had two internships at large companies where the role was narrow, and I just finished a senior project where I had to do five different things and I learned dramatically more. I want my first full-time role to be one where the breadth comes before the specialization, and this is the only first-job posting I've seen that's framed that way."*
12. Senior leader (VP / Director)
> *"The reason I'm interested in this role specifically: you're building a function that doesn't exist yet — there's no current Head of Platform, the JD says the team is currently distributed across two adjacent VPs. That's the work I want to do for the next four to five years. I built the platform function at [Previous Co.] from 8 to 60 engineers, and I want my next role to be earlier in that same arc, at a different company stage. I've had the 'inherit a 200-person org' role; I want the 'build the org from scratch' role next."*
How to actually prepare a specific answer
A few hours of prep beats memorizing a script. Three sources of useful material:
- The hiring manager's recent activity. What did they post on LinkedIn in the last 30 days? What blog posts, podcasts, conference talks have they done? You can almost always pull one specific theme from one post.
- The company's engineering / product / customer blog. Look for posts about what the team is actually building — not the marketing blog about the company's mission, but the work the team is doing.
- One conversation with a current employee. A 15-minute call with someone on the team gives you 5x what a JD can. Worth doing for any role you actually want.
The single highest-leverage prep move is talking to someone inside the company. If you don't have a contact, you can find the right person on the team directly — describe what team and seniority you'd want to talk to and get a short list of likely matches. From there, a short personalized message that asks for 15 minutes has a reply rate around 40-60% versus 5-8% for cold applications — and the call itself usually gives you the specific material that turns "I'd love to work here" into a specific, credible answer.
If you've already been asked the related question — what specifically interests you about the role itself — your answer here should complement rather than overlap. "Why do you want this job" leans toward company and motivation; "why are you interested in this position" leans toward the role and the work. Most interviewers ask one or the other; some ask both. Have one good answer for each, with different specifics.
Common mistakes to avoid
- Talking too long. 45-75 seconds is the target. 2-minute answers lose the room.
- Leading with what you'll get. "I'd grow my skills, learn from senior people, expand my network." Flip it to what you'd contribute first.
- Trashing your current employer. Even if true. The interviewer will project that energy onto themselves a year from now.
- Reciting the mission. "Your mission to empower X really resonates with me." Generic. The interviewer wrote those words.
- Vague aspirations. "I want to make an impact." Make an impact on *what*?
- Lying about loving the product if you don't use it. Interviewers can tell. It's fine to not be a power user; just talk about the work instead.
When you're not actually that excited about the job
Be honest with yourself first. If the answer is "I need a job and this one pays" — that's fine, but it won't land in an interview. The fix is to find one specific thing about the role you can genuinely engage with, even if the broader situation is utilitarian:
- "The team is doing X, which I haven't done before but want to learn."
- "The stage of the company is right for me — I've been wanting to move from a larger company to a smaller one."
- "The work would let me keep developing the skills I'm best at while testing new ones."
If you genuinely can't find one specific thing that interests you about the role, that's a signal worth listening to. Either you haven't done enough research, or the role isn't actually the one for you.
FAQ
What's the best way to answer "Why do you want this job?"
Use a two-beat structure: one specific reason for this job at this company right now, plus why it fits the work you want to be doing for the next 2-3 years. Aim for 45-75 seconds.
How is "Why do you want this job?" different from "Why are you interested in this position?"
They overlap, but "why do you want this job" tilts toward company, motivation, and continuity; "why are you interested in this position" tilts toward the role itself and what you'd do. If you get both questions, give different answers for each.
What if the real reason is the salary or location?
Don't say so directly. Reframe in terms of the work or the level of responsibility. Compensation usually signals that the role is bigger or more senior — talk about why that fits where you want to be.
Should I mention the company's mission in my answer?
Only if it genuinely fits your background or values in a specific way. Reciting the mission statement reads as filler. If you do mention the mission, tie it to something concrete you've done or care about.
How long should the answer be?
45-75 seconds. Under 30 is too thin; over 90 loses focus.
Can I say "I want to make a difference"?
Only if you can be specific about what kind of difference, in what area, and why this role lets you make it. The generic version is forgettable.
What if I'm being asked this for a job I don't really want?
Find one specific thing about the role that you can engage with honestly — the team, the technology, the customer, the stage — and lead with that. If you genuinely can't find one, that's a signal about the fit.