Guide · English job interview practice

How to answer “Why do you want to work here?” in English

Eloquent Coaching Team · 20 October 2026

Answer “Why do you want to work here?” with two specific reasons about this company, such as its product, customers, or a problem it is solving, and connect each one to your own experience or goals. End with what you want to contribute. Avoid salary, location, or praise that could apply to any company. Keep it under a minute.

What is the interviewer really checking with “Why do you want to work here?”

Companies want people who chose them, not people who applied to fifty similar jobs and happened to get a call back. This question checks whether your interest is real and whether it will last past the first difficult month.

  • Research: did you look beyond the homepage?
  • Motivation: is your reason about the work, or only about pay, title, or location?
  • Fit: do the reasons you give match what the job actually involves?
  • Retention: will you still want to be here in two years?

A good answer is specific enough that it would sound strange if you said it to a competitor. That is the test.

What structure should you use?

Use company, connection, contribution. Two reasons are better than four.

  1. Company: one or two specific things about them. Their product, their customers, a market they are entering, how they work. “You’re one of the few logistics companies building your own routing software instead of buying it.”
  2. Connection: why that matters to you, linked to your experience. “I’ve spent three years working on routing problems from the outside, as a client of those tools, and I want to work on the core product.”
  3. Contribution: what you want to do there. “I’d like to bring the customer side of that experience to your product team.”

Where do the specifics come from? The product itself if you can try it, recent announcements, the job description, the careers page, talks or articles by people on the team, and customer reviews. Note two or three facts. You will only use one or two, but having spares helps when the interviewer has already mentioned your first choice.

What does a weak answer sound like compared with a strong one?

Generic reasons and specific versions

WeakStrong
“Because it’s a big, famous company with a great reputation.”“Because your platform is used by small clinics, and I’ve spent five years building software for exactly that kind of customer.”
“I’m looking for new challenges and opportunities to grow.”“I want to move from maintaining a mature product to building a new one, and this team is launching its first product in a new market.”
“The salary and the benefits are very good.”“I like that the role combines analysis and client work. In my current job those are split between two teams.”
“I love your company. It’s amazing. I’ve always dreamed of working here.”“I’ve used your accounting app for my freelance work for two years, and the invoicing flow is the reason I recommend it to other people.”

Enthusiasm is good. Enthusiasm without detail sounds like flattery. Put one fact behind every positive word.

What are good model answers for different situations?

Each answer is around 45 to 60 seconds spoken. Swap the details for real ones from your own research.

Data analyst applying to a retail company: “Two things stood out for me. First, you’re moving from store-level reporting to customer-level data, and that’s the exact transition I helped run at a grocery chain last year. I know how messy it gets, and I enjoyed that work. Second, I read that analysts here sit inside the commercial teams instead of in a separate data group. I like that, because the analysis I’m proudest of happened when I was in the room where the decision was made. So I’d like to bring that experience to your pricing team.”

Engineer applying to a startup: “I’ve been following your product since the beta. What interests me is that you’re solving document search for legal teams, where accuracy really matters and a wrong answer has a cost. In my current role I work on search for an e-commerce site, so I know the technical side, but I want to work on a problem where precision matters more than speed. I also like that the team is small. I’d have more ownership here than I’ve had anywhere before, and that’s what I’m looking for at this point.”

Career changer moving from hospitality into customer operations at a travel software company: “I’ve worked in hotels for eight years, the last three as a front office manager, and a big part of my job is dealing with the problems booking software creates. Your company builds that software. I’d like to move to the other side and help fix those problems before they reach a guest at the front desk. I also noticed in the job description that you want someone who understands hotel operations. That’s the part of this role where I can help from the first week.”

What should you avoid saying?

  • Pay, benefits, or remote work as your main reason. They matter, and you can discuss them later, but they do not answer this question.
  • Criticism of your current employer. “I want to leave my toxic company” turns the answer into a complaint.
  • Facts from the homepage only. “You’re a leader in innovative solutions” could be any company.
  • Something you cannot explain if they ask a follow-up. Only mention what you actually understand.
  • Getting the company’s product or market wrong. Check names and facts before the interview.

What mistakes do non-native speakers make with this question?

  • Translating formal compliments. Very formal praise can sound insincere in English. Plain and specific works better: “I like how you…”, “What stood out to me was…”.
  • Sounding memorised. If you recite a polished paragraph, the interviewer will hear it. Keep your two reasons as notes and build the sentences live.
  • Over-hedging enthusiasm. “I think maybe it could be interesting” sounds like you are not interested. Say “I’m interested because…” and give the reason.
  • Mispronouncing the company or product name. Check how it is said, for example in a video from the company, and practise it out loud.
  • Speaking too fast when you get to the research part, because you are worried about forgetting it. Slow down. That is the part that shows effort.
  • Filler words like “basically” and “you know” before every point. Replace them with a short pause.

How do you rehearse it out loud?

  1. Write two reasons about the company and one line about what you want to contribute.
  2. Say the answer out loud with a timer. Target 45 to 60 seconds.
  3. Record it and ask: would this make sense if I said it to their main competitor? If yes, it is too generic.
  4. Use the one-breath test on each reason. Each should fit in one or two breaths.
  5. Practise a second version with your backup reason, in case the interviewer has already talked about your first one.

You can rehearse this in Eloquent by setting up a custom roleplay with the company, the role, and the interviewer, then answering out loud. The debrief quotes your exact words and suggests a better line where your answer drifted into general praise.

Frequently asked questions

How long should my answer be?

Between 45 and 60 seconds. Two specific reasons, a link to your experience, and one sentence about what you want to contribute. If the interviewer wants more, they will ask about one of your reasons.

What if I don’t know much about the company?

Do at least thirty minutes of research before any interview: the product, recent news, the job description, and the careers page. If the company is small and has little public information, focus on the problem it is solving and why that problem interests you.

Is it OK to mention salary or remote work?

Not as your main reason. You can mention flexibility briefly at the end if it is important, but lead with the work. Compensation has its own conversation later in the process.

How is this different from “Why do you want this job?”

“Why this job” focuses on the role and its tasks. “Why work here” focuses on the company. In practice, a strong answer covers both: one reason about the company and one about the work itself.