How to Answer “Why Do You Want This Job?”
“Why do you want this job?” is not a test of whether you can flatter the employer. It is a test of motivation, role understanding and judgement. The interviewer wants to know whether you have chosen the role for a reason, whether you understand what the work actually involves, and whether your reasons are likely to produce good performance rather than quick disappointment.
A strong answer connects three things: the work the role involves, the evidence that you can do or learn that work, and the contribution you want to make. If your answer only says the company is impressive, it sounds generic. If it only says the job helps your career, it sounds self-centred. If it only repeats the job description, it sounds rehearsed. The best answer explains why this specific opportunity makes sense from both sides.
1. Understand what the question is really testing
The surface question is about desire. The deeper question is about decision quality. An employer is trying to reduce the risk of hiring someone who has applied randomly, misunderstood the role, or will lose interest once the difficult parts of the job become real.
A useful answer therefore proves four things:
- You understand the role beyond the job title.
- You can explain why the responsibilities match your interests or strengths.
- You have evidence that makes your motivation credible.
- You can connect your motivation to value for the organisation.
For example, saying “I want this job because I like working with people” is too broad. Many jobs involve people. A stronger answer would explain that the role combines customer discovery, problem solving and cross-functional delivery, then give evidence that you have enjoyed and performed well in similar situations.
2. Use the Work → Evidence → Contribution structure
A reliable answer can be built in three parts. First, identify the work that attracts you. Second, connect that work to evidence from your experience, study or projects. Third, explain the contribution you expect to make if hired.
Work: What part of the role, problem or environment genuinely interests you?
Evidence: What have you done that proves this interest is informed rather than vague?
Contribution: How will that motivation help the employer, team, customers or users?
Example answer: I want this job because it combines customer insight with operational improvement. In my current role, the work I have enjoyed most has been identifying where customers get stuck and then changing the process so the same issue does not repeat. For example, I helped redesign our query triage checklist, which made responses more consistent across the team. This role appeals to me because that kind of improvement work is central, and I think I could contribute a practical, customer-focused approach from day one.
Notice the answer does not claim that the company is perfect. It proves motivation through a pattern of behaviour. The candidate has enjoyed a type of work, has evidence of doing it, and can explain why the new role is a logical next step.
3. Start from the employer's resources, not only your ambition
Candidates often answer this question by explaining what they want to gain: training, progression, exposure, stability or a better title. Those may be legitimate reasons, but they are not enough. A stronger answer starts from what the employer already has: a platform, customer base, data, product, public mission, brand, technical environment, specialist team or operating challenge.
This matters because a job is not only a private career move. It is access to a system of resources. The employer wants to hear that you understand those resources and will use them responsibly to create value.
Weak answer: I want this job because it would help me develop my career in marketing.
Stronger answer: I want this job because your team has a large base of returning customers and a strong content channel, which means marketing decisions can be tested against real behaviour rather than assumptions. My strongest experience is using campaign data to improve retention, so I am interested in a role where I can turn that existing customer insight into more focused lifecycle campaigns.
The stronger answer still includes career direction, but it places the employer's resources at the centre. It says, in effect: I understand what this organisation has, I know why that creates an opportunity, and I can help turn that opportunity into results.
4. Make the answer specific without overdoing praise
Many candidates try to sound enthusiastic by praising the organisation: “You are an industry leader,” “I admire your culture,” or “I have always wanted to work here.” These lines can be true, but they are weak unless they are specific and connected to the role.
Specificity comes from naming the real work. Instead of saying you like the company culture, explain what kind of working environment the role suggests and why that suits you. Instead of saying you admire the product, explain the user problem it solves and why you want to work on that problem.
Generic praise: I want to work here because you are a respected company with a great reputation.
Specific motivation: I want this role because your product is used by small finance teams that do not have large operations departments. That makes clarity and reliability especially important. I have enjoyed support roles where the aim is not just to answer a ticket, but to remove confusion from the process, so this customer success position fits the kind of impact I want to have.
A good rule is simple: if the sentence could be used for fifty different employers, revise it. Add the role, the users, the operating problem, the team context or the type of work.
5. Avoid making the answer only about personal benefits
It is normal to care about pay, progression, flexibility and stability. The problem is not that these motives exist. The problem is that they do not prove fit. If the answer centres only on what the job gives you, the interviewer may wonder whether you will still care when the work is demanding.
Too self-focused: I want this job because it offers better progression and would help me move into management.
Balanced answer: I am interested in this role because it gives me the chance to take ownership of a larger service area while still staying close to delivery. In my current role, I have started coaching newer team members and improving handover processes, and that has shown me that I enjoy building systems that help other people perform well. Progression matters to me, but what attracts me here is the chance to grow by solving a real team performance problem.
The balanced answer does not hide ambition. It makes ambition useful. It shows that the candidate wants progression through contribution, not instead of contribution.
6. Answer the question differently by career stage
The same structure works at every level, but the evidence changes. A recent graduate may use coursework, projects, volunteering, internships or part-time work. An experienced candidate should use professional patterns and results. A career changer should show that the move is deliberate and informed.
Recent graduate example
Answer: I want this job because it combines analysis with practical business decisions. During my degree, the projects I found most engaging were the ones where data had to be translated into a recommendation rather than left as a report. In my final project, I analysed customer review data and presented three service improvements to a mixed audience. This analyst role interests me because it would let me keep developing that skill in a commercial setting, while contributing clear evidence for team decisions.
Experienced candidate example
Answer: I want this job because it sits at the point where process improvement, team leadership and customer outcomes meet. In my current operations role, my strongest results have come from simplifying handovers between teams and making performance data easier for managers to act on. Your service is scaling, so those operating habits appear especially important. I am interested in the role because I can bring practical delivery experience while helping the team build more repeatable ways of working.
Career changer example
Answer: I want this job because it uses the part of my teaching experience that I want to build on: understanding learner needs, structuring information and measuring whether people can apply it. Over the last year, I have completed a workplace learning course and created onboarding materials for new staff, which confirmed that learning design is the right direction for me. This role is attractive because it focuses on practical employee training rather than abstract content creation, and I can bring strong facilitation and curriculum planning skills from my previous work.
For any version, prepare follow-up evidence. If you mention users, be ready to explain what you understand about them. If you mention a technical environment, be ready to describe what you have learned. If you mention leadership, be ready to give an example. This question often leads naturally into competency based interview questions.
7. Connect motivation to proof
Motivation without proof sounds like preference. Proof without motivation sounds like a CV summary. The strongest answers combine both.
Use evidence that shows you have already moved toward this kind of work. Evidence can be a project you chose, a problem you repeatedly solve, a responsibility you asked for, a course you completed, a pattern in your achievements or feedback you received from others.
Motivation claim: I enjoy stakeholder management.
Proof: In my last project, I volunteered to run the weekly stakeholder update because the team was getting conflicting feedback. I created a simple decision log and used it to clarify priorities with the product and operations teams.
Role connection: That is why this project coordinator role appeals to me: stakeholder alignment is not an occasional task, it is central to the work.
This is also how to avoid sounding scripted. Real evidence makes the answer feel grounded. You do not need dramatic achievements; you need relevant ones.
8. Prepare a 60-second answer
A good default answer is about 60 seconds. It should be long enough to prove fit, but short enough to invite follow-up questions.
Sentence 1: Name the role feature, problem or responsibility that attracts you.
Sentence 2: Explain why that feature matters to you professionally.
Sentence 3: Give one piece of evidence from your background.
Sentence 4: Connect the evidence to the employer's context.
Sentence 5: End with the contribution you hope to make.
60-second answer: I want this job because it focuses on improving the customer journey after someone has already chosen the product. That interests me because retention problems often reveal where a service is confusing, inconsistent or not delivering its full value. In my current role, I analysed cancellation reasons and found that many customers were leaving because they had not understood one setup step. I worked with support and product colleagues to improve the onboarding email and help article, which reduced repeated questions. Your team already has a strong user base, so I would be excited to use that kind of customer evidence to improve activation and long-term satisfaction.
If the interviewer asks a shorter version, reduce the evidence to one sentence. If they ask for more detail, expand the example. The structure should stay stable even when the length changes.
9. Common mistakes to avoid
- Giving generic praise: admiration is not enough unless it is tied to the role, product, users or work.
- Talking only about benefits: training and progression matter, but the employer also needs to hear contribution.
- Repeating the job advert: show understanding by interpreting the responsibilities, not copying the wording.
- Overclaiming passion: specific interest is usually more credible than exaggerated enthusiasm.
- Ignoring difficult parts of the job: a mature answer shows awareness of the real work, including pressure, ambiguity or routine tasks.
- Using the same answer everywhere: keep your core motivation, but adapt the employer context and evidence.
- Forgetting the contribution: finish by showing how your motivation helps the team, users or organisation.
10. Practice worksheet
Before writing your final answer, complete these prompts in short notes. This prevents the answer from becoming either too generic or too self-focused.
Role: Which responsibility in the job description appears most central?
System: What platform, users, data, product, mission, brand or team resource does the employer already have?
Motivation: Why does that work genuinely interest me?
Evidence: What have I done that proves this interest?
Contribution: What practical value could I bring in the first months?
Risk: What might sound generic, exaggerated or self-centred if I leave it unchanged?
Turn the notes into five or six sentences. Then practise answering without reading. If the answer sounds like a cover letter, make it more conversational. If it sounds like a personal wish list, add employer value. If it sounds like flattery, add evidence.
11. Final checklist
- Have I named a specific part of the role that attracts me?
- Have I shown that I understand the work beyond the job title?
- Have I connected my motivation to real evidence?
- Have I explained why this employer's context matters?
- Have I included what I can contribute, not only what I can gain?
- Can I deliver the answer in about 60 seconds?
- Can I answer likely follow-up questions about the evidence I mention?
- Would this answer still make sense if the interviewer removed the company name?
- Have I removed generic praise and unsupported enthusiasm?
- Does the answer sound like a decision, not a slogan?
Frequently asked questions
What if I mainly want the job for career progression?
You can mention growth, but connect it to contribution. For example, explain that you want broader ownership because you have already taken responsibility for process improvement and want to apply that skill at greater scale.
Should I talk about the company or the role?
Talk about both, but keep the role central. The organisation creates the context; the role explains what you will actually do each day.
What if I do not know much about the company?
Research the product, customers, mission, recent work and job description before the interview. If information is limited, focus on the responsibilities and the problem the role appears designed to solve.
How is this different from “Tell me about yourself”?
“Tell me about yourself” asks for a focused professional introduction. “Why do you want this job?” asks for the decision logic behind this application. You can prepare both together using the MockBase tell me about yourself guide.