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

They want to know whether you picked this company for a reason, or whether it's one of fifty applications you sent the same afternoon. A clear, specific answer tells them you're likely to accept an offer, settle in and stay.

Hiring someone takes time and money, and a candidate who leaves after six months costs the team all of it again. So the interviewer is listening for three things: that you know what the company actually does, that something about it matches what you want from your career, and that you've thought about where you'd fit. Enthusiasm matters, but only when it's attached to a fact.

The same question comes in several disguises: “Why this company?”, “Why do you want to join us?”, “What attracted you to this role?” and “Why should we be your first choice?”. All of them want the same answer, so one prepared structure covers every version.

Spend twenty minutes reading four sources, in this order, and write down one line from each. You're not trying to become an expert; you're looking for one or two facts you can honestly connect to yourself.

Take notes by hand or in a single document, and finish by writing one sentence that starts “I want to work here because…”. If you can't finish that sentence with something specific, keep reading for another ten minutes.

Use three parts: what draws you to the company, why that fits your own skills or goals, and what you'd bring to the role. Say one or two sentences for each, and the whole answer lands in forty to sixty seconds.

The order matters. Starting with the company shows you did your homework. The middle part turns a compliment into a reason, because it links their fact to your story. And ending on what you'd contribute shifts the answer from “what I want” to “what you get”, which is what the interviewer is really weighing.

For a large IT services company, talk about the range of clients and technologies, the structured training, and the chance to learn how large systems are delivered. Those are the real strengths of services work, and interviewers there like hearing that you understand them.

A fresher from an engineering college might say: “What stood out to me is the range of work here. Reading about your recent projects, you're building systems for banks, retailers and hospitals at the same time, and your graduate programme trains new joiners before placing them on a project. I've enjoyed my coursework in databases and my final-year project, a small inventory app for a local shop, but I haven't yet seen how software is built for a large client with real deadlines. Starting here would give me that. In return I'd bring a habit I built in that project: I test my own work properly before handing it over, which I think matters a lot when a client is depending on it.”

Notice that the answer doesn't say “because you're a big, stable company”. Stability may be true and may matter to you, but on its own it's a reason to want any big company. The range of clients and the training programme are reasons to want this one, and they connect naturally to a fresher's honest wish to learn.

For a startup, talk about the problem they're solving, the stage they're at, and your appetite for ownership. Startups worry that candidates want a big-company job with a startup's excitement, so show that you understand small teams mean wide responsibilities.

An engineer with three years at a mid-sized company might say: “I've been following your product since your launch post last year, and I noticed you've just started selling to small clinics as well as pharmacies. I spent the last three years building billing features for a healthcare software company, so I know how messy pharmacy and clinic data can be. What draws me here is the size of the team. At my current job, a feature passes through four teams before it ships, and I want to own something from the first conversation with a customer to the release. I'd bring that healthcare billing knowledge from day one, and I'm comfortable picking up whatever needs doing, including the parts that aren't strictly my job.”

This answer works because it names something recent and specific, links it to real experience, and addresses the startup's quiet worry — will this person cope with the chaos? — without being asked.

For a product company, talk about the product itself: how you've used it, what you noticed, and what you'd want to work on. Product companies want people who care about the thing they build, and actually using it is the easiest way to prove you do.

A career switcher moving from customer support into a junior developer role might say: “I've used your expense app at my current job for two years, and I've also been on the other side of it — I handle support tickets, and a lot of them come from people confused by expense approvals. That's partly why I started learning to code eighteen months ago. I built a small side project that sorts receipts automatically, and working on it made me want to build tools people rely on every day, not just answer questions about them. I'd bring a support person's instinct for where users get stuck, which I think is useful on a team that ships features straight to customers.”

The switcher turns what might look like a weakness — no developer job yet — into the centre of the reason. That's the trick for any career change: make your old role the reason you understand their users better than a typical candidate would.

Give a short, accurate summary in your own words — what they do, who for, and one recent or distinctive fact — then connect it to the role in one sentence. It's a knowledge check first and a “why us” question second, so keep it factual and brief.

A good shape is three sentences. First, what the company does and for whom: “You build payroll software for small and medium businesses.” Second, one thing you found in your research that shows you looked past the homepage: “I read that you've recently added support for contract workers, which seems to be a big push this year.” Third, the link to you: “That's part of why this backend role interested me, because it sounds like the payments side is growing fast.”

Don't recite the founding year, the number of offices or the revenue figure. Numbers you've memorised sound like a copied fact sheet, and if you get one wrong it's worse than leaving it out. If you genuinely aren't sure about something, say what you do know and ask a question about the rest: “I understand the main product well, but I'd love to hear how this team fits into it.”

The biggest mistake is giving an answer that would work for any company. If you could swap in a competitor's name and nothing else would change, the answer isn't doing its job.

Write your three parts as bullet points, not full sentences, and say the answer out loud five or six times, a little differently each time. You want to remember the facts and the order, not a script.

Record yourself on your phone and listen back. Check that you mention one specific fact within the first two sentences, and that you finish on what you'd bring rather than trailing off. Then ask a friend to play interviewer and follow up with “Why not our competitor, though?” — that's the question that shows whether your reason is really specific.

Keep a short note for every company you apply to, with your research lines and your three parts. Before each interview, reread it for five minutes. If you want to rehearse under realistic pressure, a RoundAlpha mock interview lets you name your target company and add the job description, then asks questions and follow-ups built from your CV, so you can hear how your reasons land before the real thing.

The same research also powers “why should we hire you?” and your questions to ask the interviewer at the end, so you prepare three answers for the price of one.