TD
Key Takeaways
- Connect three things: the role, the company, and your own direction.
- Be specific about the company — "I like your mission" is what everyone says.
- Show what you bring, not only what you want to get.
- Never let money or convenience be the headline reason.
Why Interviewers Ask It
This question tests whether you actually researched them or are firing off applications at random. A specific, genuine answer signals you will be motivated and are likely to accept and stay. A vague one signals a filler application. It is one of the easiest questions to prepare and one of the most commonly fumbled.
The Three-Part Framework
[Something specific about the role] + [something specific about the company] + [how it fits where you're heading].
All three matter. Role-only sounds like you would take the same job anywhere; company-only sounds like a fan, not a candidate; direction-only centers you instead of them.
Example Answers
"The role is squarely on the backend reliability work I want to go deeper in. And I've followed how your team writes publicly about incident response — that culture of learning from failure instead of hiding it is rare, and it's exactly where I do my best work."
Marketer:
"I've watched your content go from good to genuinely category-defining this past year, and this role owns the strategy behind that. I want to build that kind of organic engine, and doing it somewhere that already values content over paid shortcuts is the right environment for me."
"After years in operations, I want to move into data analysis, and this role sits right at that intersection — analytics applied to the operational problems I already understand. Your team's focus on decisions over dashboards is exactly the practical approach I was hoping to find."
Mistakes That Cost You
- Leading with pay, benefits, or the commute. True or not, it signals the wrong priorities.
- Generic flattery. "You're a leader in the industry" applies to a thousand companies.
- Making it all about you. Balance what you want with what you will contribute.
- Winging it. This question is predictable; not preparing it reads as not caring.
Do Ten Minutes of Homework
Read the company's recent blog, product updates, or news, and the full job posting. One genuinely specific detail — a feature, a value they wrote down, a recent launch — is what turns a generic answer into a memorable one. Practice it in a mock interview so it sounds natural, not recited.
The Research Checklist
You cannot give a specific answer without a specific fact, and you can gather several in ten minutes:
- The full job posting. The problems it describes are the problems you should say you want to solve. Reference them directly.
- The company's recent blog or changelog. A launch, a decision, or a point of view you genuinely find interesting.
- Recent news or funding. A new market, a milestone, a strategic shift.
- The product itself. If you can try it, one honest observation from real use is the strongest hook of all.
- Your interviewers' public work. A talk, an article, a project — something that tells you what the team values.
Turn any one of these into a sentence, and your answer instantly separates you from every candidate who said "you're a leader in the industry."
Full Sample Answers, Annotated
Backend engineer at a fintech:
"Two things. The role is squarely on the payment-reliability work I want to specialize in — that's the role fit. And I read your engineering blog's post-mortem on last quarter's outage, and the fact that you publish those instead of hiding them tells me a lot about the culture — that's the company fit. I want to grow into a senior reliability role, and I'd rather do it somewhere that treats failure as something to learn from."
Notice all three parts: role, company, and direction, each anchored to a specific fact.
Marketing manager at a consumer app:
"I've actually recommended your app to three friends this year, so I come at this as a genuine user first. Professionally, the role owns exactly the organic-growth engine I've spent my career building, and I'd love to build it somewhere that already values content over paid shortcuts — which your last year of work clearly shows."
Analyst switching from operations:
"I've spent four years in operations, and the part I kept gravitating toward was the data behind the decisions. This role sits right at that intersection — analytics applied to operational problems I already understand deeply. Your team's focus on decisions over dashboards is exactly the practical approach I was hoping to find."
How This Connects to Other Common Questions
"Why do you want this job?" rarely arrives alone. It sits alongside "Why are you leaving your current role?", "Where do you see yourself in five years?", and "Why should we hire you?" — and your answers should form one coherent story. If you say you want this role for its architectural ownership, your five-year answer should point in the same direction. Interviewers notice when the threads connect, and they notice when they contradict. Prepare these as a set, and rehearse them together in an AI mock interview so the whole narrative sounds consistent and natural. Our interview prep tool can generate the exact questions you are likely to face for a specific role, so you are never caught flat.
Tailor Your Whole Application, Not Just the Answer
A specific answer to "why this job" is far easier to give when your entire application is already pointed at the role. If you have tailored your resume to the posting — mirroring its language and emphasizing the relevant work — you have already done most of the thinking this question requires. The reasons you are a fit on paper are the same reasons you can articulate out loud. Candidates who spray generic applications struggle with this question precisely because they never engaged with what makes each role different.
Mistakes That Quietly Cost You the Offer, Revisited
Beyond the obvious flubs, these subtler ones do real damage:
- A rehearsed monologue. Memorized word-for-word, it sounds hollow. Know your three beats; let the exact words vary.
- Praising the company but not the role. It sounds like you would take any job there, not this one.
- Praising the role but not the company. It sounds like you would take this job anywhere.
- All ambition, no contribution. "This role will help me grow" centers you. Balance it with what you will give.
- Contradicting your other answers. If "why leaving" and "why this job" tell different stories, the interviewer trusts neither.
Adapting the Answer to Company Size and Stage
The same three-part structure works everywhere, but the emphasis shifts with the kind of company you are talking to. At an early-stage startup, lean into impact, breadth, and mission — they want people energized by ambiguity and ownership: "I want to work somewhere my decisions visibly move the product, and being early enough to shape how things are built is exactly what excites me." At a large, established company, emphasize depth, craft, and scale — the chance to work on hard problems at a size few places offer: "I want to go deep on reliability, and doing it on a system that serves millions is a problem I can't get anywhere smaller." Reading the company's stage and tailoring which of your genuine reasons you lead with makes the answer feel native rather than generic — the same instinct that makes a tailored resume outperform a one-size-fits-all one.
Practicing Until It Sounds Natural
The paradox of this question is that a memorized answer sounds worse than an unprepared one — recited word-for-word, it goes flat and hollow. The goal is not to memorize a script but to internalize your three beats (the role reason, the company reason, your direction) so well that you can say them freshly each time, in slightly different words. The way to get there is to practice out loud, not in your head. Say it a dozen times, varying the phrasing, until the ideas are automatic but the delivery stays alive. Running it in an AI mock interview alongside the other common questions helps you hear whether your whole narrative hangs together — because "why do you want this job" should rhyme with your answers to "why are you leaving" and "where do you see yourself," not contradict them. When all your answers point the same direction, you come across as someone who knows exactly what they want and why this role is it.
Frequently Asked Questions
What if I mostly want the job for the money?
Almost everyone needs the income; interviewers know that. Find a genuine secondary reason — the work, the team, the growth — and lead with that instead.
How long should my answer be?
30–60 seconds. Long enough for all three parts, short enough to stay sharp.
What if I don't know much about the company?
Then research before the interview. Ten minutes on their site and recent news is the difference between a specific answer and a forgettable one.
How do I answer if it's genuinely just a stepping-stone role?
Find the true part of your interest and lead with that — a specific skill you will build, a problem you will get to solve, a team you respect. You do not have to pretend it is your dream job, but you do have to show genuine, specific interest in something about it.
Is it okay to say I want the job for career growth?
Yes, as one part of the answer, framed around what you will contribute while you grow. "I want to deepen my backend skills, and I can help you scale your payments system while I do" balances your growth with their gain.
How long should the answer be?
Thirty to sixty seconds. Long enough to hit role, company, and direction; short enough to stay sharp. If you are still talking after a minute, you have drifted into rambling.
What if I'm interviewing at several similar companies?
Then the company half of your answer matters most — it is what differentiates otherwise similar roles. Find the specific thing that makes each company distinct (their culture, a product decision, a value they wrote down) so your answer could not be swapped between them.
Should I mention the specific team or product?
Yes, when you can. Referencing the actual team, product, or problem you would work on shows you read the posting closely and thought about the day-to-day, not just the company name. Specificity is always more convincing than generality.
Is enthusiasm enough, or do I need substance?
You need both, but substance carries more weight. Genuine energy is attractive, yet without a specific reason behind it, it reads as generic. Pair your enthusiasm with a concrete detail about the role and company, and it becomes credible rather than performed.
How is this different from "why should we hire you?"
"Why do you want this job?" is about your motivation and fit — what draws you to the role. "Why should we hire you?" is about your value — what you bring to them. Prepare them as a pair: one points at the company, the other at your contribution, and together they tell a consistent story.
What if the interviewer seems unconvinced by my answer?
Add a specific, concrete detail. Vague answers get lukewarm reactions; naming an actual project, value, or problem you would work on usually shifts the energy. If you sense doubt, it is a signal to get more specific, not more enthusiastic.
Putting It All Together
"Why do you want this job?" is one of the most predictable interview questions and one of the most commonly fumbled. Connect three things — something specific about the role, something specific about the company, and how it fits your direction — and anchor each to a real fact you gathered in ten minutes of research. Keep your answer consistent with your other responses, and rehearse the whole set together. Do that and you turn a throwaway question into clear proof that you did your homework and genuinely want this role, not just any role.
Was this guide useful?
Be the first to rate it.
