Why You Want This Job? — The Answer That Loses Offers

Of all the questions an interviewer can ask you, 'Why do you want this job?' might sound like the easiest. It isn't. It's one of the most revealing questions in the entire interview — and most candidates blow it without realising. They either sound desperate ('I really need the money'), vague ('It seems like a great opportunity'), or self-centred ('It would be great for my career'). None of those answers tell the interviewer what they actually need to know.

The interviewer is trying to solve a real problem: they need to fill a role with someone who genuinely cares about it. Hiring the wrong person costs companies thousands of pounds or dollars — in training, lost productivity, and then repeating the whole hiring process. So when they ask this question, they're essentially asking: 'Are you going to stick around, contribute, and care? Or are you just here until something better comes along?'

By the end of this article, you'll know exactly why interviewers ask this question, what a perfect answer actually looks like, how to build your own answer from scratch even if you're not sure what to say, and the exact mistakes that kill otherwise strong candidates. You won't just survive this question — you'll use it to stand out.

The Question That Makes or Breaks Your Interview

Every interviewer asks 'Why do you want this job?' expecting more than a rehearsed answer. This question tests your alignment with the role, company, and team. A weak response signals you haven't done your homework or you're just looking for any job. A strong response shows you understand the company's challenges, the role's responsibilities, and how your skills fit. Treat this as a chance to demonstrate your research and genuine interest. Avoid generic answers like 'I love your mission' or 'I want to grow.' Instead, tie your answer to specific projects, technologies, or problems the company is solving. For example, if the company recently migrated to microservices, mention your experience with distributed systems and how you can contribute to their architecture. The goal is to make the interviewer think, 'This person gets us.'

Weak: "I really admire your company's mission and I think I can learn a lot here."
Strong: "I've been following your blog on scaling event-driven systems. My last project involved building a Kafka-based pipeline that handled 10k events/sec. I see you're tackling similar challenges, and I'd love to help optimize your stream processing."

Decode the Hidden Intent Behind the Question

Interviewers aren't just curious—they're evaluating three things: your motivation, your fit, and your longevity. They want to know if you'll stay, if you'll contribute, and if you'll mesh with the team. The question is a proxy for 'Will you be happy here?' and 'Will you make us better?' Your answer should address all three. For motivation, talk about the specific technical challenges that excite you. For fit, mention how your work style aligns with their engineering culture (e.g., code reviews, pair programming). For longevity, hint at how this role fits your career trajectory. Avoid mentioning salary, remote work, or commute—those are for later. Focus on the work itself. For example, if the company uses Go and you love Go, say that. If they have a strong DevOps culture and you're passionate about CI/CD, mention that. The key is to show you've thought about what it's like to work there day-to-day.

Interviewer's mental checklist:
- Motivation: Does this person care about our tech stack?
- Fit: Will they thrive in our engineering culture?
- Longevity: Will they stay for at least 2 years?

Your answer should hit all three without being asked directly.

Structure Your Answer Like a Senior Engineer

A great answer has three parts: hook, body, and close. The hook grabs attention—start with a specific detail about the company. The body explains why you're a fit, using concrete examples from your experience. The close ties it back to the role and expresses enthusiasm. Keep it under 2 minutes. For example: 'I've been following your work on distributed tracing. At my last job, I built a tracing system using OpenTelemetry that reduced debugging time by 30%. I see you're scaling your observability, and I'd love to help improve your monitoring stack.' This structure shows you're concise, focused, and relevant. Practice it until it feels natural. Avoid rambling or listing everything you've done. Stick to one or two key points that align with the job description.

Hook: "I noticed your team recently open-sourced a Kubernetes operator for PostgreSQL."
Body: "I've worked extensively with K8s operators—I built one for Redis that automated failover. I see you're tackling similar HA challenges."
Close: "I'm excited about the opportunity to contribute to your infrastructure reliability and learn from your team's expertise."

Tailor Your Answer to the Company's Stage

Your answer should adapt to the company's maturity. At a startup, emphasize versatility and ownership. At a mid-size company, highlight your ability to scale systems. At a large enterprise, focus on process and collaboration. For example, if it's a Series A startup, say: 'I want to build foundational infrastructure from scratch—I've done it before and I thrive in ambiguity.' For a FAANG company, say: 'I'm drawn to the scale of your systems and the rigor of your engineering reviews.' Research the company's stage by checking Crunchbase, LinkedIn, or recent funding news. Also, look at their engineering blog to understand their current challenges. A startup might be dealing with monolith-to-microservices migration, while a large company might be optimizing cost. Tailor your answer to their pain points.

Startup: "I want to own the entire deployment pipeline and help you move from manual deploys to CI/CD."
Mid-size: "I see you're hitting performance bottlenecks. I've optimized SQL queries that reduced latency by 50%."
Enterprise: "I appreciate your focus on compliance and code reviews. I have experience with SOC2 audits and can help maintain quality."

Use the Job Description as Your Cheat Sheet

The job description (JD) is a goldmine of keywords and priorities. Identify the top 3-5 requirements and weave them into your answer. If the JD mentions 'Kubernetes,' 'Go,' and 'distributed systems,' your answer should include those exact terms. For example: 'Your JD emphasizes Kubernetes and Go. I've been using Go for 3 years and built a custom scheduler on K8s. I'm excited to apply that to your platform.' This shows you've read the JD carefully and you match their needs. Also, look for 'nice-to-haves'—if you have them, mention them. If you lack something, don't lie, but frame it as a learning opportunity. For example: 'I haven't used Cassandra in production, but I've worked with DynamoDB and understand the trade-offs.' Be honest but positive.

JD Requirements:
- 5+ years in backend development
- Experience with microservices
- Knowledge of Kafka

Your answer: "I have 6 years of backend experience, built microservices with gRPC, and designed a Kafka-based event bus for order processing."

Show, Don't Tell: Use Stories with Metrics

Instead of saying 'I'm good at scaling,' tell a story with numbers. 'I optimized a database query that reduced page load time from 3s to 200ms, improving user retention by 15%.' Metrics make your answer credible and memorable. Use the STAR method (Situation, Task, Action, Result) to structure your story. Keep it relevant to the role. If the job is about performance, talk about a performance optimization. If it's about reliability, talk about reducing pager duty alerts. For example: 'Our team was getting 50 alerts per night. I implemented a circuit breaker pattern that cut alerts to 5 per week, and we slept better.' Stories with metrics show you understand impact, not just activity.

Situation: Our API latency was >2s during peak hours.
Task: Reduce latency to <500ms.
Action: I profiled the code, found a N+1 query, and added caching with Redis.
Result: Latency dropped to 300ms, and server costs decreased by 20%.

Address Potential Red Flags Proactively

If you have a gap in your resume, a career change, or lack a required skill, address it head-on. Don't wait for the interviewer to ask. For example, if you're switching from frontend to backend, say: 'I've spent 5 years in frontend, but I've been building backend services in my spare time. I'm committed to making the switch and I've already contributed to open-source backend projects.' This shows self-awareness and initiative. If you're overqualified, explain why you want this specific role. For example: 'I've been a manager, but I miss coding. I want to get back to hands-on engineering, and your team's tech stack is exactly what I'm looking for.' Proactive honesty builds trust.

Career change: "I know my background is in QA, but I've been writing automation frameworks in Python for 2 years. I'm ready to move into a dev role."
Overqualified: "I've led teams, but I want to focus on technical contributions. Your company's emphasis on individual contributors is appealing."

Practice Your Delivery: Tone and Body Language

Your answer's content matters, but so does delivery. Speak with enthusiasm—monotone answers signal disinterest. Maintain eye contact (or look at the camera for remote interviews). Use hand gestures naturally. Avoid filler words like 'um' and 'like.' Record yourself and watch the playback. Notice if you're fidgeting or looking away. Practice with a friend who can give feedback. The goal is to sound confident and genuine. If you're nervous, it's okay to say 'I'm excited about this opportunity'—it shows passion. Also, pace yourself: speak slowly enough to be understood, but not so slow that you seem unsure. A well-delivered answer can compensate for a slightly weaker story.

Tips:
- Record yourself on your phone.
- Watch without sound first: check body language.
- Then listen: check for filler words.
- Practice 5 times until it feels natural.

Follow Up with a Written Summary

After the interview, send a thank-you email that reinforces your answer. Reference a specific point from the conversation. For example: 'Thank you for the insightful discussion about your microservices migration. I'm even more excited about the opportunity to contribute to your event-driven architecture.' This shows you were listening and you're serious. It also keeps you top of mind. Keep it short—3-4 sentences. Don't rehash your entire answer. Just reinforce one key point. Also, if you forgot to mention something important, include it here. For example: 'I also wanted to mention my experience with Terraform, which I think would be useful for your infrastructure as code initiative.'

Subject: Thank you - [Your Name]

Hi [Interviewer Name],

Thank you for the conversation about your team's work on [specific topic]. I was particularly interested in your approach to [something discussed]. I'm confident my experience with [relevant skill] would be a great fit.

Looking forward to the next steps.

Best,
[Your Name]

Common Pitfalls and How to Avoid Them

Many candidates make these mistakes: being too generic, talking too much about what you want (e.g., 'I want to learn'), badmouthing previous employers, or sounding desperate. Avoid these at all costs. Instead, focus on what you can contribute. Another pitfall is not having an answer ready—winging it leads to rambling. Prepare and practice. Also, don't be overly humble. You're there to sell yourself. If you've done great work, say it. Finally, don't forget to smile. It sounds trivial, but a smile conveys confidence and approachability. If you're stuck, take a breath and say 'That's a great question. Let me think about it.' It's better than a rushed answer.

Pitfalls:
- "I want this job because I need a job." (Desperation)
- "I heard the pay is good." (Wrong motivation)
- "My last company was terrible." (Negativity)
- "I don't know, what do you think?" (Lack of preparation)

Researching the Company: Mission, Tech Stack, Engineering Culture

To answer 'Why do you want this job?' convincingly, you must demonstrate deep knowledge of the company beyond surface-level facts. Start by researching the company's mission statement—understand what problems they solve and why they exist. For example, if the company is a fintech startup focused on financial inclusion, mention how your previous work in accessible banking aligns with their mission. Next, investigate their tech stack: look at job descriptions, engineering blogs, GitHub repositories, and tech talks. If they use Python and Kubernetes, and you have experience with both, highlight that. Finally, understand their engineering culture: do they practice agile, pair programming, or have a strong DevOps culture? Mention specific practices you admire, like 'I appreciate your emphasis on CI/CD and automated testing, which I've championed at my current role.' This shows you've done your homework and are genuinely interested in how they work.

{
  "mission": "Read 'About Us' page, recent press releases, and CEO interviews.",
  "tech_stack": "Check job postings, Stackshare, GitHub, and engineering blogs.",
  "engineering_culture": "Look for mentions of agile, code reviews, testing practices, and remote work policies.",
  "products": "Use the product yourself, read user reviews, and note recent features.",
  "team": "Find team members on LinkedIn, read their posts or talks."
}

Aligning Career Goals with Company Growth

Employers want to know that your career trajectory aligns with the company's growth. Start by identifying where the company is heading—are they pre-IPO, expanding to new markets, or investing heavily in AI? Then, articulate how your professional goals fit into that journey. For example, if the company is scaling its engineering team, you might say: 'I'm looking to take on more technical leadership as I grow, and your plans to double the engineering team over the next year offer exactly that opportunity.' Be specific: mention the next role you aspire to (e.g., staff engineer, tech lead) and how this position is a stepping stone. Avoid vague statements like 'I want to learn and grow.' Instead, say: 'I want to deepen my expertise in distributed systems, and your work on real-time data pipelines is the perfect challenge.' This shows you've thought about your future and see a mutual benefit.

Answering Without Sounding Desperate or Generic

A common pitfall is sounding desperate ('I really need this job') or generic ('I love technology'). To avoid this, focus on specific, authentic reasons. First, avoid any mention of salary, benefits, or location unless asked. Instead, emphasize the work itself: 'I'm excited about the challenge of migrating your monolithic app to microservices, which aligns with my experience in breaking down complex systems.' Second, use concrete examples from your research. For instance, 'I read your blog post about reducing latency by 40%—I've tackled similar performance issues using caching strategies.' Third, show enthusiasm without overdoing it. Use measured language: 'This role stands out because...' rather than 'This is my dream job.' Finally, practice your delivery to sound confident, not rehearsed. Record yourself and check for filler words or overly eager tone.