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

You applied to forty openings in a week, and on a call with one of them the recruiter asks why you want to work here specifically. The honest answer, "you were the first to call back", can't be said out loud. The Sobes question bank has this question in several forms: "Why did you choose our company? What matters to you when choosing an employer?", "What exactly attracted you to our vacancy and product?", "Why are you interested in our company and in banking?".

Nobody needs a declaration of love for the brand, and the interviewer isn't expecting one. It is enough for them to see that you read the job description, understand what the company does, and can name one or two reasons the work here would interest you. The reasons have to be true, otherwise the answer falls apart on the second follow-up question.

What they actually want to know

Whether you understand where you are. Candidates who confuse the company with a competitor are more common than you'd think.
Whether what matters to you matches what they have. The second half of the question from the bank, "what matters to you when choosing an employer", is about exactly that.
Whether you will leave in three months when someone more interesting calls back.

The question sits next to another frequent one: "What motivates you and what demotivates you at work?", recorded after interviews at 12 companies. The two answers should line up. If hard technical problems motivate you but you chose the company "for stability", the interviewer will notice.

What to find out in 15 minutes before the call

Four things, three or four minutes each:

The job description, once more and carefully. Write down two tasks that honestly interest you and one technology you want to work with.
The product. Open the site or the app and go through one scenario as a user. One specific observation is enough.
The engineering side. The tech blog, talks by employees, open repositories. Find one article or talk on your topic.
What they ask in interviews. For large companies you can see this on the company pages and in the interview leaks: the questions show what the team cares about.

Write your findings down in three lines. That covers the answer and a couple of questions of your own at the end.

Three honest footholds

Build the answer on one or two of the three. All three at once sound like a memorized text.

Product and problems. What the company does and why doing exactly that interests you: scale, domain, type of work.

Stack and engineering culture. Technologies, processes, the level of the team. Everything you can learn from the job description, the tech blog, and talks.

Company stage. A startup where everything is built from scratch, a growing product, a large corporation with established processes. The point is to explain why this stage suits you right now.

The formula is simple: what I learned about you, plus why it matters to me. The second part is required. "You have a great product" without "and here is why that's close to me" stays a compliment.

Examples

Product company

I've been using your app myself for about two years, and last week I took a deliberate look at how search works. The job description says the team works on search and ranking. I've spent the last year doing something similar at a smaller scale, and I'd like to work on it with your volume of data.

It works because there is an observation, a reference to the job description, and a link to your own experience.

Outsourcing or an integrator

I like that your projects change every year or year and a half. I've been on one product for four years and I feel I've stopped learning. Your portfolio has fintech and logistics, I've worked in both, and I'll get into a project quickly.

Praising a product that doesn't exist is odd at an outsourcing company. Talk about the variety of projects, the domains, and how fast you ramp up.

Bank or large corporation

I'm interested in systems where a mistake is expensive and reliability is taken seriously because of that. I watched your team's talk about moving to your own data bus and saw that the engineering problems are not trivial. Also, clear processes and grades matter to me right now: the startup I work at is missing that.

The word "stability" is better spelled out. On its own it sounds like "I want to be left alone".

Startup

I want a small team where a lot depends on one person. At a corporation I worked on one module for three years and saw the result once a quarter. You have twelve engineers and an early-stage product. I understand what that means for workload and uncertainty, and I'm fine with that right now.

The last sentence removes the founder's main fear: that someone from a big company will be scared off by the chaos within a month.

If nobody has heard of the company

There is barely a website, the name tells you nothing, the job description is three lines. Don't play the longtime fan. Lean on the job description and say plainly that you know little:

To be honest, most of what I know about the company comes from the job description. Two things caught my attention: you mention moving from a monolith to services, and I've been through exactly that migration, and you use Go, which I want to switch to fully. Could you tell me more about the product? I'm really curious.

Asking about the product is fair here: you show interest and get material for the next rounds.

If the recruiter reached out first

When you didn't apply and they found you, the question sounds a little different: "what interested you in the role?" Answer the same way, just start with the truth: "I wasn't actively looking, but here is what caught my eye in your message." There is no need to pretend you've dreamed of working here.

What not to say

"You're the market leader", "you have a friendly team". These fit any company and say nothing about you.
Only money, remote work, and health insurance. Terms matter, but they are discussed separately: how to name a number is covered in the article on salary expectations.
Only what you are leaving. That answers a different question, which has its own phrasing: Why are you leaving your job?
Invented facts about the company. The interviewer knows their company better than you do.

Keep a note for each company

With several processes running, details blur: which one had the data bus talk and which one had search. Save the three lines you wrote before the call in the vacancy card in the application tracker or in any file. Before the next round, rereading them and adding what the interviewer told you is enough: in the final round "why us" gets asked again, and an answer with details from earlier conversations lands better than the first one did.

Say the answer out loud once before the call. If it runs longer than thirty seconds, drop one foothold. And turn what you learned about the company into questions of your own: which ones are worth asking is covered in Questions to ask the interviewer as a developer.