How to answer "why are you interested in this position?"

"Why are you interested in this position?" sounds like small talk before the real questions start, but interviewers use it as a filter. It separates candidates who researched the role from candidates who applied everywhere and are hoping something sticks — and that distinction usually shows up in the first sentence of the answer, before the interviewer has heard anything else.

The three moves that make an answer specific instead of generic:

1. Research one real detail about the role or company beyond the job posting's headline.
2. Pick one skill or experience of yours that connects directly to that detail.
3. Say what you'd contribute — not what you'd get out of it.
4. Keep the whole answer to 20–30 seconds.
5. Practice it out loud until the specific detail sounds natural, not recited.
6. Adjust the detail if the interviewer mentions something more specific earlier in the conversation.

Why interviewers ask "why are you interested in this position"

Interviewers ask "why are you interested in this position" to check two things at once: whether you understand what the role actually involves, and whether your interest is specific to this job or is the same pitch you'd give anywhere. According to Indeed's guide to this question, employers are trying to separate candidates who are motivated by this particular opportunity from those who are, in their words, "window shopping" — applying broadly and taking whatever responds first.

That is also why it is easy to answer badly without realizing it. Most people prepare content — a story about their skills, a case for their fit — but never prepare specificity. An answer can be true and still sound generic if it never names anything unique to this employer.

The fill-in-the-blank template

Skip trying to sound enthusiastic in the abstract. Fill in these three blanks with something true and specific, in order:

Blank 1 — the specific detail: Not "I love your mission" but something you actually found: a product decision, a technical approach, a growth stage, a specific responsibility in the posting that stood out. If you can't name one, that is a sign you need to research more before the interview, not a sign to write around it.

Blank 2 — the matching skill or experience: Pick the one piece of your background that most directly connects to that detail. Not your whole résumé — the one thing that makes the connection obvious rather than asserted.

Blank 3 — the contribution: Close on what you'd bring to that specific thing, not on what the job would do for you. "I want to grow here" answers a different question than the one they asked.

Put together, it reads like: "[Specific detail] is what stood out to me, because [matching experience] — and I'd want to bring that to [contribution]." That is a skeleton, not a script; say it in your own words once you've filled in the blanks.

Three example answers

These map the template onto different situations. Swap in your own detail, experience, and contribution before using one.

Career changer, moving into a new field: "I noticed the job posting mentions this team is building out its first dedicated onboarding flow, which is exactly the kind of zero-to-one problem I want to work on. I spent the last three years doing customer support, so I've seen firsthand where new users get stuck — I'd bring that ground-level view to designing something that actually solves the confusion instead of guessing at it."

Internal promotion or lateral move: "What drew me to this role is that it owns the relationship with our biggest accounts end-to-end, instead of handing off between teams the way my current role does. I've spent two years managing the handoff points on the current process, so I know exactly where accounts fall through the cracks — I'd want to close those specific gaps rather than relearn them from scratch."

Industry switch, different sector, transferable skill: "I saw that this role is focused on scaling a support team that's growing fast, and that's the exact problem I solved in my last job — just in a different industry. I built the onboarding process that got a five-person team to fifteen without a drop in response time. I'd want to apply that same playbook here, adjusted for what's different about your customers."

What to avoid when answering this question

A few patterns turn an otherwise fine answer into a forgettable one:

• Generic company praise with no specifics. "I love your culture" or "you're an exciting company" could describe any employer that has a decent careers page. If a competitor could swap in for the company name and the answer still works, it isn't specific enough.
• Reciting the job description back. Restating the responsibilities they already wrote shows you read the posting, not that you thought about it.
• Making it about what you'd get. Better pay, a shorter commute, a recognizable name on your résumé — all real reasons people take jobs, and none of them belong in this answer. Keep the focus on what you'd contribute, not what you'd gain.
• An answer that would work for a different role at the same company. If your answer doesn't mention anything specific to this position, it's really an answer about the company, not the role you're interviewing for.

How to rehearse it so it sounds researched, not recited

The risk with a templated answer is that it can come out sounding read rather than felt, which undercuts the exact impression you're going for. Say the filled-in version out loud several times before the interview — not memorized word-for-word, just familiar enough that the specific detail rolls out naturally instead of landing like a fact you looked up an hour ago.

It also helps to rehearse against something that reacts, the same way mock interview practice surfaces an answer that sounds fine on paper but stumbles out loud. If the interviewer mentions a detail earlier in the conversation that's more specific than the one you prepared, swap it in — a live, responsive answer reads as more genuine than a fixed one, even if the structure underneath is the same.

Key takeaways

• Name one specific, researched detail about the role or company — not generic praise that could apply anywhere.
• Connect that detail to one matching skill or experience, not your whole background.
• Close on what you'd contribute, not on what you'd personally gain from the job.
• Keep the answer to 20–30 seconds; longer usually means it has drifted back into a general pitch.
• This question is not "tell me about yourself" (a narrative) or "why should we hire you" (a pitch about you) — it's specifically about the pull of this role.

Frequently asked questions

Why do you want this job?

Because of one specific thing about the role or company — a project, a problem it's solving, a way of working — that connects to a skill or experience you actually have, and what you'd contribute to it. Avoid generic reasons like salary, prestige, or location; keep the focus on the specific pull of this role and what you'd bring to it.

Why are you interested in this role specifically, and not just any job?

Because you can point to a detail unique to this role — something from the posting, the company's recent work, or the conversation so far — and connect it to something specific in your own background. If your answer would work unchanged for a different job at a different company, it isn't actually about this role yet.

Why do you want to work here?

Name something specific about how this company works or what it's building that you found through real research, not the "About Us" page's mission statement alone. Pair it with one concrete way your background connects, so the answer sounds like it required you to look past the job posting.

How is 'why are you interested in this position' different from 'why should we hire you'?

"Why are you interested in this position" asks what pulled you toward this specific role. "Why should we hire you" asks you to make the case for yourself over other candidates. The first is about the role's pull on you; the second is a pitch about your qualifications. Answering both the same way wastes one of them.

How to answer why do you want this job if you need the paycheck, not the mission?

Needing income is real, but it isn't the answer to this question. Find something genuine and specific about the role itself — a skill you'd get to use, a problem you'd get to solve, a way of working you're drawn to — and build the answer around that instead. There's almost always something true and specific to point to, even in a job you took partly out of necessity.

Conclusion

"Why are you interested in this position" rewards specificity over enthusiasm. Name one real detail about the role, connect it to one matching part of your background, and close on what you'd contribute — then say it out loud enough times that the specific detail sounds like something you noticed, not something you looked up to fill a blank.