Why do you want to work here?

Three questions hiding in one

“Why do you want to work here?” bundles three separate questions, and a complete answer touches all of them.

Why this organisation, out of the dozens doing similar work. Why this role, rather than the adjacent jobs you could apply for with the same skills. And why now, which matters when you are leaving a job, returning after a break or switching field.

Most weak answers cover only the first, and cover it with praise. Interviewers hear flattery all day, and praise is cheap to produce without reading anything. What they are checking is simpler: did you understand what we do before you applied, and does this job make sense for you? If the answer is yes, you are less likely to withdraw at offer stage or leave inside a year.

Harvard’s career services puts the preparation plainly, advising candidates to read through the employer’s website and review online content relevant to the role before the interview. That reading is where the specifics come from. There is no way to improvise them convincingly in the room.

How to research an employer in an hour

You do not need a dossier. You need four or five facts you could not have guessed, and a view on which part of their work you would be joining.

Start with what they sell or deliver, in their own words. Product and service pages are more useful than the about us page for understanding the actual job, though the National Careers Service is right that the about us section is where products, services and values are usually spelled out together. Write down the thing they do that is closest to the team you are interviewing with.

Then look for what changed recently. MIT’s primer suggests checking what an employer has been in the news for; press releases, a funding round, a new product line, a regulatory change, a merger, a new branch. Recent change is the best material for this answer, because it shows you looked at them as they are now rather than as they were when the website was written. For public bodies, charities and universities, the equivalent documents are the published strategy, annual report or inspection results.

Next, the people. The same primer suggests talking with current or former employees. One short conversation gives you something no page will: how the team is organised, what they are proud of, what frustrates them. Harvard also recommends keeping current on industry news through daily news sources, which is what lets you say something sensible about their market rather than only about them.

Finally, reread the job advert as a document about them. The responsibilities tell you what is not getting done right now, and the order they are listed in tells you what hurts most. That is usually the honest answer to why this role exists at all.

Turning the research into an answer

Use three beats, about twenty seconds each.

The hook. One specific thing about the organisation that genuinely interests you, said in a sentence that could not be transferred to another employer. A product decision, the market they serve, a technical constraint they work under, the scale of their caseload, the fact that they do in-house what most competitors outsource.

The fit. Why this role, connected to the hook. Here you name the part of the work you want to be doing and why it suits what you are good at. If your route to this job is unusual, this is the beat where it stops looking random.

The forward line. One sentence on what you would contribute or want to learn in the role. It keeps the answer from being purely admiring, and it gives the interviewer something to ask about.

Said out loud, that is 45 to 60 seconds. Resist the urge to list three reasons for each beat; one strong specific is more persuasive than three vague ones, and a long answer buries the detail you worked hardest to find.

Sample answers

A company whose product you use

I have been using your scheduling tool at work for two years, and the thing I noticed is that it is one of the few that treats shift swaps as a first-class feature rather than an afterthought. That is a decision made by people who have talked to shift workers.

The role interests me because it sits on the support side of exactly that feature set. I have spent four years supporting workforce software, so I already know the arguments managers have about rota changes, which is usually the hard part of the conversation rather than the software.

What I would want to do early on is go through the recurring swap-related tickets and see which ones are really documentation problems, because that is where I have made the biggest difference before.

A public body or charity

I read your last annual report before applying, and the part that stayed with me was the shift to delivering advice in community venues rather than by appointment at the office. I have worked with the same client group, and reach is the whole problem.

This role is the delivery end of that change, which is where I want to be. I have five years of frontline advice work and I am used to running a session in a borrowed room with no system access.

In the first months I would expect to spend a lot of time learning your referral pathways, because getting those wrong is what wastes a client’s day.

An employer that is not glamorous

Honestly, what attracted me is the nature of the work rather than the brand. Pipeline inspection is unfashionable and highly regulated, and I like regulated work because the standard is written down and arguments end with a document.

The role is a step up in scope from my current job, with responsibility for a region rather than a single site, and your region covers the older network, which is where the interesting failures are.

I would bring the reporting habits I built at my last employer, where I rewrote our inspection write-ups so they could be read by a planner who was not an engineer.

The “why this job” version

I want this job because it is the first one I have seen that combines the analysis with the client conversation. In my current role those are two different people, and I keep ending up in the second half unofficially.

Your team is small enough that the person doing the modelling presents it, which is what I am trying to move towards.

The learning curve for me would be your sector rather than the method, and I would plan to spend my first weeks with the account managers to close that gap.

What makes this answer fail

Flattery with nothing behind it. “You are the market leader and have an amazing culture” tells the interviewer you read a headline. If a sentence works for any employer in the sector, it is filler.

Reciting the about us page. Repeating their own mission statement back to them is worse than saying nothing, because it proves you read one page and stopped. Quote a fact and say what it means to you instead.

Making it only about yourself. “This would be a great step for my career” and “the commute is easy” may both be true, and neither gives a reason to hire you. Convenience is a tiebreaker, not an argument.

Talking about pay. Compensation questions get their own stage in the process, and raising money here reads as though nothing else drew you.

Getting a fact wrong. Naming the wrong product, the wrong country or last year’s chief executive undoes the work. If you are unsure of a detail, describe it rather than name it.

And leaving out the role. Plenty of candidates explain the company beautifully and never say why they want this particular job. That omission is what sinks otherwise good answers.

When your real reason is pay, location or stability

Sometimes the honest driver is that you need a steadier contract, a shorter commute, hours that work with childcare, or more money. None of those make you a bad candidate. They are just not an answer to this question, because they say nothing about the work.

The fix is to find the smallest true thing you can say about the job itself and lead with that. If stability is the driver, you can say that you are looking for a permanent role where you can stay and build something, then move to what attracted you about their work. If the location is the driver, you can mention wanting to work for an employer rooted in the area, and then talk about what their service actually does.

Do not manufacture a passion you do not have. Interviewers who hire often can hear it, and a measured, specific answer is more convincing than an enthusiastic vague one. A candidate who says that the work looks interesting, the team looks well run, and the commute means they could do it for years is believable.

If you genuinely cannot find anything that interests you about the employer after an hour of research, that is useful information about whether to take the interview at all.

Related wordings you should prepare for

“Why are you interested in this position?” narrows the question to the role, so put the fit beat first and keep the company hook to one line. MIT lists the compressed version as “Why are you interested in position, company or industry?”, and the industry variant is worth a separate sentence if you are changing sector.

“What do you know about us?” is the research question with the politeness removed. Answer with two or three concrete facts and then connect one of them to the role, rather than listing everything you read.

“What about this organisation impresses you compared with others in the field?”, a wording used in Harvard’s question list, is explicitly comparative. Prepare one real contrast: something they do differently from the obvious competitor. This is the version that punishes thin research hardest.

On a recruiter screening call, the same question is usually a filter for whether you applied deliberately. Thirty seconds is enough: one fact, one reason, one line about the role.

For an internal move, drop the company research entirely and talk about the team, the problem and what you have seen of their work from the inside. And if the question arrives as “why should we hire you”, that is the mirror image: the focus moves from their organisation to your evidence.