What is the best way to answer why do you want this job?
The best answer connects three elements: something specific about the company or role that genuinely interests you, how it aligns with your professional goals, and what you bring that makes you a particularly good fit. Generic enthusiasm — "I've heard great things about the culture" — is not compelling. Specific, informed interest — "Your approach to distributed data processing solves a problem I've been working around for two years" — is.
"Why do you want this job?" is one of the most common interview questions and one of the most commonly answered poorly. Candidates either give generic enthusiasm that could apply to any company ("great reputation," "exciting work") or answers that are entirely self-focused ("I want to grow my skills"). Neither approach demonstrates genuine preparation or genuine fit. This guide explains what interviewers are actually assessing with this question and how to craft an answer that sets you apart.
What Interviewers Are Looking for
The why-do-you-want-this-job question serves three purposes from the interviewer's perspective.
Genuine motivation — Is this candidate genuinely interested in this specific role, or are they interviewing everywhere and treating each opportunity identically? Candidates with genuine motivation perform better, stay longer, and engage more fully with the work. An interviewer can usually detect whether a candidate's interest is authentic or performative.
Alignment — Does this candidate actually understand what the role involves? Do their stated reasons make sense given the actual nature of the work? Candidates who want a role for reasons that do not match the reality of that role tend to be disappointed and churn quickly.
Fit — Does this candidate see the role as a meaningful next step, or as a desperate reach? Candidates whose reasons clearly connect their background to the role requirements and their future direction are easier to place in the role narrative.
"When a candidate tells me they want to work here because we have a great reputation and good compensation, I know they have not prepared. When they tell me they want to work here specifically because of a technical decision we made public six months ago and explain why that approach interests them, I am immediately more engaged with their candidacy." — Engineering Manager, data infrastructure company
The Three-Part Answer Structure
A strong why-do-you-want-this-job answer has three components, in order.
Part 1: What specifically interests you about this company or role
This is the hardest part to do well because it requires genuine preparation. You need to identify something specific about the company — the technology, the problem domain, the product, the company's mission, a specific technical decision they have made publicly — that actually interests you.
Sources for specific interest points:
- The company's engineering blog
- Talks by engineers at this company at conferences or on YouTube
- The product itself (use it)
- News coverage of technical decisions or company directions
- Job description language that reflects the team's actual priorities
- GitHub contributions or open source projects from the company
Part 2: How this connects to your professional direction
Connect the company's work to where you are trying to go professionally. This is not about what you will get from the role — it is about why this role is a logical expression of the direction your career is moving.
"I have been working in distributed systems for the past three years and have developed strong opinions about tradeoff management at scale. Your team's public work on consistent hashing and your talk at [conference] about handling partition failures are directly relevant to the problems I find most intellectually interesting right now."
Part 3: What you bring
Close by briefly connecting your background to the role's requirements. This is not the place for a full pitch — you have answered other questions that cover your qualifications. A brief connection between your specific experience and one or two key requirements of the role closes the loop.
Company Research: What to Look For
For a technology company interview, build specific interest points from these sources.
| Source | What to Look For | How to Use It |
|---|---|---|
| Engineering blog | Specific technical decisions, architectural approaches | "Your series on migrating from monolith to microservices describes exactly the challenge I am currently navigating" |
| Conference talks | Technical philosophy, problems the company is solving | "Your CTO's talk on consistency vs. availability tradeoffs shaped how I think about this class of problem" |
| Product usage | Real experience with the product | "Using [product] daily, I have noticed [specific feature] and have thoughts on how it could evolve" |
| Job description | Team priorities, specific tools and challenges | "The emphasis on observability in this role matches work I have been doing for the past year" |
| Company news | Recent strategic moves, product launches | "The expansion into enterprise security is a space I have direct experience in" |
Answers That Do Not Work
The Generic Answer
"I've heard great things about the culture here and I think it would be a great place to grow my career."
Why it fails: This could be said about any company. It contains no information about this specific company and signals minimal research.
The Compensation-Forward Answer
"I've heard the pay is competitive and the stock package is attractive."
Why it fails: Compensation is not a compelling reason to choose a role from the interviewer's perspective. Even if compensation is part of your actual motivation (which is legitimate), leading with it signals that you are primarily interested in the money, not the work.
The Desperation Answer
"I've been looking for a long time and this role seems like a good opportunity."
Why it fails: It signals that you are not in a position of genuine selection and may take any offer you can get. It also does not answer the question.
The Pure Self-Focus Answer
"I want to work in machine learning and this role would give me that experience."
Why it fails: This is about what you want to get, not about why this company and role specifically align with your interests. The interviewer's question has an implicit second half: "...rather than the dozens of other companies with similar openings?" If you cannot answer that, you have not answered the question.
Sample Answer by Role Type
Software Engineer Answer
"I have been working on payment processing infrastructure for the past four years, and the problem of global consistency at the scale your system operates at is something I have read about in depth. Specifically, your engineering team's published work on your saga pattern implementation for distributed transactions is the most sophisticated approach to this class of problem I have seen. The role is also a step up in ownership — moving from a team that executes on someone else's architecture to one where I would be defining it. That is the professional transition I am ready to make."
Product Manager Answer
"I have been following [company]'s approach to developer experience products closely for the past year. Your recent launch of [feature] was a significant departure from how the rest of the market approaches the problem — instead of abstracting away the underlying complexity, you exposed it with better tooling, which I think is the right call for your user segment. I want to work on products where deep technical understanding drives product decisions, and your team's track record suggests that is how you operate."
Data Scientist Answer
"The combination of experimental rigor and scale that your team operates at is rare. Most companies either have the scale without the rigor or the rigor without the scale. I have been specifically building toward this type of environment — I have run A/B tests at scale and I have read your published research on causal inference in observational data, which is directly relevant to the work I want to do next."
Frequently Asked Questions
What if I am genuinely applying everywhere and this company is not a particular favorite? Be honest in your research and find at least one specific, genuine reason to be interested. You do not need to be in love with the company — you need to be able to articulate a substantive reason why this role is a good fit for you and why you are a good fit for it. If you truly cannot find any specific reason after doing your research, that is information about whether you should be applying.
Is it acceptable to say that compensation or location is part of my reason? Compensation and location are valid factors in job decisions. They are not, however, compelling answers to why you want this specific job from an interviewer's perspective. Lead with professional reasons and substantive interest. If asked directly about other factors, acknowledge them honestly but keep them secondary.
What if I am changing industries and do not have obvious direct experience? Acknowledge the transition and frame it as intentional. Explain what has drawn you toward this new domain and what transferable skills and experience you bring. "I am moving from financial services software into consumer health products specifically because I want to build things that affect how people interact with their health daily" is an honest and compelling framing.
References
- Griffeth, R. W., Hom, P. W., & Gaertner, S. (2000). A meta-analysis of antecedents and correlates of employee turnover. Journal of Management, 26(3), 463-488.
- Judge, T. A., & Cable, D. M. (1997). Applicant personality, organizational culture, and organizational attraction. Personnel Psychology, 50(2), 359-394.
- Wanous, J. P. (1992). Organizational Entry: Recruitment, Selection, Orientation, and Socialization of Newcomers (2nd ed.). Addison-Wesley.
- Adkins, C. L., Russell, C. J., & Werbel, J. D. (1994). Judgments of fit in the selection process. Personnel Psychology, 47(3), 605-623.
- Tsai, W. C., & Yang, I. W. F. (2010). Does image matter to different job applicants? International Journal of Selection and Assessment, 18(1), 48-61.