Why do you want to work here? How to answer (with an example)

The answer, in 4 blocks

1. 1. One specific, checkable detail

   A product, a technical decision, a public post, an open-source repo. Even better if it's a detail nobody else would pick.

   Example: You publish write-ups when something breaks — I read the one about the payout queue.

2. 2. The bridge to your experience

   Why that detail matters to you, based on something you already did.

   Example: I ran a queue migration that broke in production once, and I liked how your team handled that.

3. 3. The work, not the perks

   What you want to learn or do that you can't do where you are now.

   Example: I want to work at a bigger scale and on a team that owns services end to end.

4. 4. The honest limit

   Optional, but it makes the answer sound like a person: something you don't know yet, or a question you have.

   Example: What I don't know yet is how the team decides between fixing that queue and shipping something new.

The full example answer

Read it out loud, swapping in your own details. An answer you've never spoken isn't yours yet.

Because of your incident write-ups. I read the one about the payout queue — you published what broke, with the timeline, and that's rare. I ran a queue migration that broke in production once, and it changed how I work: now I measure before and after. What I'm looking for is a team that owns services end to end, because that's where I learn the most. One thing I'm curious about is how you decide between fixing that queue and shipping a new feature.

What to avoid

• ×"You're a market leader" or "great culture". It's what everyone says, and it fits any company.
• ×Talking about salary or benefits here. This question is about the work.
• ×Praising the office or the snacks. It shows what you noticed, not what you want.
• ×Not knowing what the company does. Two minutes on the site is enough to avoid that.

Phrases that help

“What caught my attention was ...”

Opens with the specific detail instead of with praise.

“I did something similar when ...”

Builds the bridge, without turning the answer into a story about you.

“What I'm looking for is a team that ...”

Says what you want to do, not what you want to receive.

If the question comes like this

Why us?

Same answer, shorter: one detail and one sentence about your experience.

Why do you want to leave your current job?

Don't criticize the current company: "I'm looking for X, which I can't do where I am" — with X being something the new role has.

What do you know about our company?

The product, who uses it and one recent piece of news. Two sentences are enough; inventing is worse than saying you read the product page.

FAQ

What if I don't know the company well?

Spend ten minutes: product page, engineering blog, recent news. One real detail beats four adjectives.

Can I say I need the job?

You can be honest about wanting to change jobs, but answer with what draws you to the work. "I need a job" ends the conversation.

Should I mention the salary here?

Not here. If the salary is why you're applying, that's fine — but this question is about the work, and mixing the two weakens both answers.