"Why are you interested in this position?" is the most-asked interview question that candidates underestimate. It feels easy. The honest answer — "I need a job" or "the salary is good" — is the wrong answer. The generic answer — "I really admire your company culture" — is somehow even worse, because every other candidate said the same thing.
The interviewer is looking for one signal: do you actually understand what this role is, and is there a real reason you want it specifically? Candidates who can't show that get filtered out, even when their resume is stronger.
The structure that consistently works in 2026 is a three-part answer, 60-90 seconds long:
- One specific thing about the role itself — not the company, the *role*. Reference something from the job description, the team, or the work.
- One concrete reason it fits your background — a project, skill, or stage of your career that maps directly.
- One reason it's the next thing you want to do — what you're trying to build toward.
That's it. Skip the company-mission preamble. Skip the "I've been a fan of your brand for years" line — interviewers hear it dozens of times a week and it doesn't land.
Below: the formula, the common mistakes, and 10 sample answers across functions you can adapt for the specific role you're interviewing for.
The 3-part formula in detail
Part 1: Something specific about the role
This is the part most candidates skip. The fix: open the job description before the interview and pick one sentence that's actually interesting to you. It might be:
- A specific responsibility ("owning the migration to event-driven architecture")
- A specific stage ("building the first analytics function from scratch")
- A specific team or product ("the work the design team is doing on the onboarding flow")
- A specific technology, market, or customer ("focusing on mid-market customers in financial services")
Name it. By naming a specific thing, you prove you read the JD and that you're not interviewing for the same role at five companies with the same answer.
Part 2: A concrete reason it fits your background
This is where most candidates default to "I have all the skills listed." That's true of every shortlisted candidate. Better: name one specific thing you've done that maps to one specific thing about the role.
- "I led the same kind of migration at [previous company] from monolith to event-driven."
- "I built the first analytics function at a Series B startup, so I know what the first six months look like."
- "I spent two years on the same customer segment at [previous company] and know the buying patterns."
The mapping has to be concrete. Skill-list matching is what the recruiter screened you on. The hiring manager wants to know what *you specifically* would do in week one.
Part 3: Why it's the right next step
This is where you signal *intent and direction*, not just availability. Good versions:
- "I want to move from a team of 3 to leading a team of 10 — this role is that step."
- "I've spent five years on the platform side; I want to move closer to the customer, and this PM role is exactly that pivot."
- "I want to work on infrastructure at the scale this company operates at — I haven't had that in a startup."
The intent answer rules out "you'd be bored here" and "you'd leave in six months" — two things hiring managers are silently worrying about.
What NOT to say (the common traps)
A few patterns that kill the answer:
"I really love your company culture." Generic and unfalsifiable. The interviewer can't tell if you mean it or you Googled "best companies to work for."
"I've always wanted to work at [Company]." Too vague. If pressed, "always wanted" rarely holds up.
"The salary and benefits are great." True for everyone. The interviewer wants to know what makes the *work* attractive.
"I'm a great fit for the listed requirements." Skill matching is table stakes. The recruiter already verified this; the hiring manager is asking something different.
"It's a good next step for my career." Too generic without saying what kind of step. Be specific about what step.
Reciting the company's mission statement. Tells the interviewer you read the About page. Doesn't tell them anything about you.
Talking exclusively about what you'd get. ("I'd learn so much, grow my career, expand my skills.") Flip it to what you'd contribute first.
Bashing your current role. Even if true. "I'm leaving because my manager is terrible" makes you sound like the problem, even when you're not.
10 sample answers by role
Adapt these to the specifics of the job you're interviewing for. Don't memorize — use the structure and swap in real details from your background and the JD.
1. Software engineer (mid-level)
> *"What caught my eye in the JD is that the team is moving from a monolith to event-driven services on Kafka. I spent the last two years at [Previous Co.] doing the same kind of migration on a smaller scale — about 30 services — and I've seen what works and what creates more problems than it solves. I want my next role to be on a team that's doing this work at production scale, with the volume to actually stress-test the architecture, and that's exactly what this role is."*
2. Product manager
> *"The thing I'm interested in is that you're hiring a PM specifically for the onboarding and activation surface area. Most PM roles I've seen are owning a feature; you're framing this as owning a metric — first-week activation — across whatever surface area moves it. That maps to how I led growth at [Previous Co.], where I owned the trial-to-paid conversion number and got to shape three different product surfaces to move it. I want my next role to be metric-owning, not feature-owning, and that's the read I got from your JD."*
3. Sales (account executive)
> *"What pulled me in is that you're early in mid-market — the JD said you've got maybe ten customers in that segment so far. That's the stage I love selling into. At [Previous Co.] I was one of the first two AEs hired to open mid-market after years of SMB-only, and the work of figuring out what plays work in a new segment — pricing, deal structure, ICP — is what I'm best at. I'd rather be helping shape mid-market motion at a company that's still figuring it out than running plays someone else built five years ago."*
4. Designer (product designer)
> *"What stood out is that the role is explicitly cross-functional with engineering and research — not just design owning the spec. I've been on design teams where design hands off and on teams where design pairs with engineering through implementation. The second model produces dramatically better work, and from the way this JD is written, that's how your team operates. I want my next role to be on a team that takes that integration seriously, and what you've described matches it."*
5. Marketing manager
> *"What I noticed is that you're looking for someone to build the demand-gen function from the ground up — the JD says you currently rely on inbound and want to build outbound paid acquisition. That's exactly what I did at [Previous Co.] over the last two years, going from $0 to $400K monthly paid spend with a target CAC. I want my next role to be a build, not a tune, and the chance to do that at a company that's already found product-market fit but hasn't operationalized acquisition is what makes this specifically interesting."*
6. Customer success manager
> *"The thing I'm interested in is the segment — mid-market customers in regulated industries. I've spent the last three years on this segment at [Previous Co.] and the interesting part of the work is that the standard CS playbook doesn't quite fit; security reviews, procurement timelines, and renewal politics all look different. I want my next CS role to be on the same segment but at a product that's earlier and faster-moving — the JD said you're 18 months past general availability, which is the sweet spot for that work."*
7. Nurse (registered nurse, hospital)
> *"What drew me to this position is that you're a Magnet-designated hospital and the JD mentioned the unit specifically does shared governance with nursing leadership. I've worked at two hospitals where staff nurses had no real input on protocols, and I've worked at one with shared governance — the difference in patient outcomes and burnout was night and day. I'm looking for my next role to be at a place that takes nurse-led process seriously, and your unit is set up that way."*
8. Teacher (elementary)
> *"What caught my attention is that the school explicitly uses a workshop model for literacy. I student-taught at a school that used basal reading, and I just finished a year at a school that does workshop, and the difference for emerging readers is striking. I want to spend the next few years building a classroom around workshop, ideally on a grade team with other teachers doing the same — and from the JD, that's exactly what your 2nd-grade team is doing."*
9. Career changer (consulting → product management)
> *"I was a strategy consultant for three years covering B2B SaaS, and the part of the work I kept gravitating toward was the product-strategy projects — defining roadmaps, sizing markets, talking to customers — rather than the operational ones. I wanted to move closer to building, not advising, and the JD for this role specifically calls out PM ownership across roadmap, customer research, and exec partnership — which is the cross-section of the consulting work I liked most plus the operational continuity I missed. That's why this role, not just any PM role."*
10. Entry-level (recent graduate, any function)
> *"The thing that pulled me in is that the JD says the team is small enough that this role wears multiple hats — analytics, ops, and customer research. I just spent two internships at large companies where roles were narrow and clear, and I learned more from a senior project that had me wear three hats than I did from either internship. I want my first full-time role to be one where I can do work that spans functions for a few years before specializing, and that's how you've described this role."*
When the company is the reason — how to make it specific
Sometimes the company itself really is part of the answer — you've used the product for years, you've worked in the space, you have a personal connection to the mission. That's fine. The rule is: be specific enough that you couldn't have said it about any other company in the industry.
Bad: "I love your mission."
Good: "I switched my entire team off [Competitor] to your product two years ago because the API ergonomics were better, and I've been a paying customer since. I want to work on the product I already trust enough to bet my team on."
Bad: "I admire your leadership."
Good: "I read [specific person]'s blog post on the [specific topic] last year and changed how I thought about [specific thing] in my own work. Working under someone whose thinking I've already learned from is rare."
The bar is: a competitor's recruiter couldn't read your answer and say "yeah, that applies to us too."
How to find the specifics if the JD is thin
Some job descriptions are just bullet points and a paragraph of corporate boilerplate. To find specifics for your answer, check:
- The hiring manager's LinkedIn. What did they post in the last month? What projects are they talking about? You can usually pull a specific theme from one post.
- The company's engineering or product blog. Real technical detail about what the team is actually building.
- Recent product launches or company news. Reference one specific thing.
- Talking to a current employee. Even a 15-minute call with someone on the team or an adjacent team gives you 5x the material a JD can.
The best preparation is talking to someone inside before the interview. If you can find the hiring manager or a peer on the team directly, a short conversation gives you the specifics that make this question land. For roles where you can't easily reach an insider, a personalized note to the hiring manager before the interview often produces enough context to answer this question with real depth — and frequently gets you in front of them in the first place. The same logic applies on whatever channel is most natural for your target company — what matters is getting one real conversation.
What good answers have in common
If you look at the sample answers above, three things hold:
- They name a specific thing about the role, not a generic company attribute.
- They map a concrete past experience to that specific thing.
- They're 60-90 seconds long — not 2 minutes, not 20 seconds.
Practice the answer out loud before the interview. The version in your head is always shorter than the version that comes out of your mouth. Time it once, trim, time it again.
FAQ
What's the best way to answer "Why are you interested in this position?"
Use a three-part structure: name something specific about the role itself (from the JD), connect it to a concrete experience in your background, and explain why it's the right next step in your career. Aim for 60-90 seconds total.
How long should my answer be?
60-90 seconds is the sweet spot. Under 30 seconds reads as unprepared; over 2 minutes loses the interviewer.
Should I mention salary or benefits in my answer?
No. Even though compensation matters, mentioning it here signals the wrong priorities. Save salary discussion for when the interviewer or recruiter raises it.
Is it OK to say "I want to learn"?
Only if you pair it with what you specifically want to learn and why this role offers it. "I want to learn how to scale a platform from 1M to 100M users" works. "I'm always learning" does not.
What if I'm interested because the salary is much higher?
Don't say so. Reframe in terms of the work, the level of responsibility, or the stage of company. Compensation is usually a signal that the role is bigger — talk about why bigger fits your trajectory.
How is "Why are you interested in this position?" different from "Why this company?"
"This position" wants you to talk about the role and the work; "this company" wants you to talk about the organization, mission, or culture. If you only get one, default to talking about the role — it's almost always the more interesting answer.
What if I'm just looking for any job?
The interviewer will probably know. Pick one specific thing about *this* role that genuinely interests you, even if it's small, and lead with that. Honesty about wanting a job is fine; the absence of any specific reason to want *this* job is not.