How to Answer “Why Do You Want to Work Here?” the Right Way

The best way to answer “Why do you want to work here?” is to connect three specific things in about 60 to 90 seconds: something verifiable about the company, something concrete about the role, and the thread in your own experience that ties the two together. Interviewers are not fishing for flattery — they are checking whether you understand what the job actually is, and whether you will still want it in six months. A strong answer names a detail you could only know by doing your homework, then shows what you would do with it.

What They’re Really Asking (It Isn’t About Them)

Let me start by validating the eye-roll. “Why do you want to work here?” sounds like a question designed to make you perform enthusiasm on command. You’ve been applying for weeks, maybe months. You want to work there because it is a job, it pays, and you are a professional adult with a mortgage and a dog who has expensive opinions about food. Saying that out loud would be honest and would also end the interview.

So here’s the translation. When a hiring manager asks this, they are quietly running three checks at once:

• Did you do any homework? Roughly half the candidates they meet will answer with something that could apply to any company on earth. You clear a surprisingly low bar just by being specific.
• Do you understand what this job actually is? Plenty of people apply to a title without reading the description. Your answer tells them whether you read it.
• Will you still be here in a year? This is the real one. Hiring is expensive and slow, and the people who do it for a living — the recruiters and talent acquisition teams whose whole job is reducing bad hires — are listening for the difference between “this job solves my problem this month” and “this job is a step I actually want.”

RULE: Your answer is about the work, not about the company’s greatness.

This is the single most important reframe in this post, so I’m going to be obnoxious about it. Most people hear “why do you want to work here” and respond with compliments — the mission is inspiring, the growth is impressive, the culture seems wonderful. Compliments are pleasant and completely unmemorable. The interviewer has heard the mission praised eleven times this week. What they have not heard is somebody explain, concretely, what they want to do inside that mission.

What this question is not

It is not “tell me about yourself.” That one is a summary of your professional arc. It is not “why should we hire you,” which is about your qualifications. And it is not “what are your weaknesses,” which is its own special genre of discomfort that I’ve written about separately in this post on answering the weaknesses question.

“Why do you want to work here?” is a fit question. Fit means the overlap between what the organization needs done and what you want to be doing. Everything else in your answer is decoration.

When it shows up in the interview

Usually early — question two or three, right after the warm-up. Occasionally it arrives at the end, disguised as “so, any final thoughts on why this role?”, which is the same question wearing a hat. It also appears in phone screens, where recruiters use it as a fast filter, and in written application forms, where you get a text box and no body language to help you.

One more place it hides: internally. When your own employer asks a version of this to find out what’s keeping you around, it’s the same muscle in a different room.

The Three-Part Fit Formula

Here is the structure I teach every client. Company, role, you. Sixty to ninety seconds total, which is roughly 150 to 200 spoken words — shorter than you think, longer than a shrug.

Part 1: Why this company (about 20 seconds)

One specific, verifiable detail. That’s the whole assignment.

Verifiable means you could point to where you found it: a product launch, a published case study, a stated change in direction, a new market they entered, something a current employee said on a podcast. The test is simple — could a candidate who had never heard of this company say your sentence? If yes, it’s filler. Cut it and find something real.

Things that fail the test: “you’re a leader in the space,” “I love your culture,” “your mission really resonates with me,” “I’ve always admired your brand.” Things that pass: “you moved your onboarding entirely in-house last year, which is unusual for a company your size, and I’m curious what that changed.”

(Yes, that second one takes fifteen minutes of research. Fifteen minutes. You spent longer than that deciding what to wear, and I say that with love.)

Part 2: Why this role (about 30 seconds)

Now move from the company to the job. This is where most answers quietly fall apart, because people stay in compliment mode for the full ninety seconds and never mention the actual work.

Pull one or two responsibilities straight from the job description — the ones that are genuinely the point of the role, not the boilerplate at the bottom — and say what draws you to them. If the description lists “build and own the reporting cadence for a team of twelve,” that is the job. Talk about that.

The job description is the single most underused document in any job search. It is the hiring manager telling you, in writing, what they will be evaluating. I’ve made this point before in the context of résumés — why you have to tailor to the job description — and it applies even more directly here, because in an interview you get to say it out loud and watch their face.

Part 3: Why you (about 30 seconds)

Close the loop. One concrete piece of your experience that makes the previous two parts credible.

Not a list. Not your whole career. One example, told in a sentence or two, that proves you have already done a version of this work and liked it. The implicit message — which you never say explicitly, because saying it explicitly is weird — is I have done this, it went well, and I want more of it.

If you’re changing fields and you think you have nothing to connect, you almost certainly do; you’re just not seeing it, which is a separate and very common problem. I wrote about that in how to position yourself for a career change, and I watch people talk themselves out of perfectly good overlaps constantly — enough that I wrote a whole post about it.

The optional fourth beat: end on a question

If the conversation allows it, finish with a short, genuine question that grows out of your answer. “…which is actually what I wanted to ask about — how much of this role is building the process versus running it?”

This does two things. It turns a performance into a conversation, and it signals that you’re evaluating them too, which changes the temperature of the room more than almost anything else you can do. Use it when the rapport is there. Skip it if the interviewer is clearly working through a scripted list and watching the clock.

Research Without the Rabbit Hole

The advice “research the company” is useless on its own, because it has no stopping point. You open one tab, then forty, and two hours later you know the founder’s college roommate and still can’t answer the question.

So here is the stopping point: fifteen to twenty minutes, five sources, one usable detail from each. You will use one or two of them. The rest is ballast that makes you calmer.

For that last row, the Occupational Outlook Handbook from the U.S. Bureau of Labor Statistics is a reliable neutral read on what a given occupation involves and where it’s heading — useful when you’re moving into a field and need to sound like you understand its shape. The Indeed Career Guide is fine for a quick orientation on common role expectations, and Harvard Business Review’s career planning collection is where I send people who want the strategic view rather than the tactical one.

A note on transparency, since I believe in saying this out loud: I’m not affiliated with any of these sources, I’m not paid to point you at them, and I’d tell you if I were.

What to do when you genuinely can’t find anything

Small companies, stealth startups, and private firms with a four-page website are real. You will sometimes do your twenty minutes and come up with very little.

When that happens, pivot from the company to the problem. You can almost always infer what problem the role exists to solve, because they wrote a job description about it. “From the description, it looks like this role exists because support volume has outgrown the current process — is that right?” is a superb answer, because it demonstrates reasoning rather than retrieval. And if you’re wrong, you’ve just invited them to correct you, which is a conversation, which is the goal.

This is also, incidentally, the same muscle you use to get into companies that never post publicly — something I covered in accessing the hidden job market.

Bland vs. Bullseye: What It Sounds Like Out Loud

Formulas are easy to nod at and hard to execute. So let’s look at the same sentiment, said two ways.

Notice what the right column has in common: it’s falsifiable. Someone could check. That’s the quality you’re after.

Full sample answer: you’re in the same field

“Two things, honestly. The first is that you moved fulfillment back in-house last spring — I read the write-up — and I’ve only ever worked on the other side of that decision, cleaning up after third-party logistics. I’d like to see it done the hard way for once.

The second is the role itself. The description says this person owns vendor relationships end to end, and that’s the part I’ve been doing informally for about three years without the title. At Northgate I took over two vendor contracts nobody wanted, renegotiated both, and cut our fulfillment errors noticeably over two quarters. It’s genuinely the part of the job I like most — which I realize is an odd thing to enjoy.”

About eighty seconds. Specific, connected, ends on a human note.

Full sample answer: you’re changing fields

“I’ll be upfront that I’m coming from teaching, so let me connect it. What drew me here is the training side — you’ve built the onboarding program in-house rather than buying it, and that’s unusual.

For six years my actual job was taking something complicated and finding the version of it that a room of thirty people could absorb in forty minutes, then noticing in real time which four of them hadn’t. That’s instructional design with a different job title. I built our department’s curriculum from nothing, and the thing I’m chasing now is doing that work for adults who chose to be there. Which, if I’m honest, is a significant upgrade.”

The transition is named in the first sentence rather than hidden. That’s deliberate — the elephant in the room gets smaller the moment you point at it, which is the whole argument of this post on riding the elephants.

Full sample answer: you’re early in your career

“I want to work somewhere I’ll be taught properly, and the description is unusually specific about mentorship — it names a structured review cycle, which most postings at this level don’t.

On the role: it’s half analysis and half communicating the analysis, and the communicating half is the part I’m actually good at. My capstone was a six-month data project, and the piece I enjoyed was the twenty minutes at the end explaining it to people who didn’t want a spreadsheet. I’d like to do that in a place where the stakes are real.”

No invented experience, no apologizing for being new. If “I don’t have the experience to answer this” is your instinct, read “I don’t know how to” — yes, you do and then come back.

How to practice this without memorizing it

Do not write it out and learn it word for word. Memorized answers sound memorized, and the moment you lose a line you’ll freeze, which is far worse than being a bit rough.

Instead, learn three bullet points: your company detail, your role detail, your proof. Say the answer out loud six or seven times, differently each time. By the fifth attempt the wording stops mattering and the structure holds on its own — which is also what keeps you steady when the video call freezes for ten seconds mid-sentence and you have to find the thread again.

Common Mistakes People Make With This Answer

I have sat through a lot of mock interviews. These are the ones I see weekly.

• Reciting the About page. If your answer could be lifted verbatim from their website, you’ve proven you can read, which was not in question. Use the research to reach a thought, not to quote one.
• Making it entirely about you. “I need a role with more flexibility and better growth.” Reasonable needs. But an answer composed only of your needs tells the interviewer what you want from them, not what you’d bring. Flip at least half of it outward.
• Leading with money, location, or benefits. Compensation is a real and legitimate part of the decision — it is simply not the answer to this question, and there’s a proper moment for the pay conversation that comes later.
• Going on for four minutes. The most common failure of all, and it is almost always nerves. Ninety seconds. If you’re past two minutes, you’ve stopped answering and started filling silence.
• Faking passion you don’t have. Interviewers can hear it. If the honest answer is “this is a solid company doing work I’m good at and I’d like to do it well,” say a polished version of that. Measured sincerity beats performed enthusiasm every time.
• Praising a competitor’s product by accident. It happens more than you’d think, usually when someone researched the wrong company at 11 p.m. Check the name on the calendar invite before you speak.
• Giving the same answer to every company. If you’re running a high-volume search, this is a tempting efficiency. It is also the single fastest way to sound like you’re applying everywhere, because you are.
• Answering a job you don’t actually want. Sometimes the reason the answer won’t come is that there isn’t one. That’s worth noticing before you accept, not after — see should I apply for this job?

RULE: If you can’t name one specific thing, you’re not ready for that interview yet.

That’s not a scolding. It’s a diagnostic. When a client can’t produce a specific detail after genuine effort, roughly half the time the real issue isn’t research — it’s that they’re applying out of exhaustion rather than interest. Which is extremely human, and worth addressing directly instead of papering over with a better script.

How I Coach This Question Differently

Most interview advice hands you a script. I don’t, for one unglamorous reason: a script fails the moment the interview stops following it, and interviews always stop following it.

What I do instead, in a coaching session or over a mock interview, is work backwards from your decision rather than theirs.

Before we build an answer, I ask why you want this job — not the interview-safe version, the real one. Sometimes it’s the work. Sometimes it’s the commute, or the money, or the fact that your current manager is making you ill. All of that is allowed. But knowing which it is changes what we build, because an answer with a true thing buried inside it sounds different from an answer made entirely of professional-sounding noise. The small adjustments — pacing, where you put the pause, whether you end on a question — only matter once there’s something real underneath.

The other thing I do is treat the answer as an asset you reuse, not a one-off. Your “why this company” is the same raw material as your cover letter opening, your LinkedIn About section, your networking message, and your follow-up email. Most people build each of these from scratch, badly, five times. Build it once properly and it travels.

What this means for your job search

Three practical consequences, and then I’ll stop.

It caps how many applications you should send. You cannot do twenty minutes of real research for sixty applications a week. You can for eight. The people I see land roles are, almost without exception, running fewer and deeper searches — which is a strategic choice, not a lack of effort, and one I’ve argued for in a framework for strategic job hunting.

It makes the follow-up write itself. The thank-you note after the interview should extend the specific thing you raised, not thank them generically for their time. If you’ve got a real detail, you’ve got a real follow-up — and there’s a follow-up strategy most people haven’t thought of that works far better when you’ve laid this groundwork.

It tells you something before you accept. If you cannot construct an honest answer to “why do you want to work here” after doing the research, you have learned something useful for free. Possibly the role isn’t right. Possibly you’re more burned out than you’ve admitted. Either way, better to find out in the preparation than in month three.

If you want the broader view of how recruiters and hiring managers evaluate all of this — and they are not evaluating the same things — I broke that down in how to impress recruiters and hiring managers.

Frequently Asked Questions

How long should my answer to “why do you want to work here?” be?

Sixty to ninety seconds, which is roughly 150 to 200 spoken words. Shorter than thirty seconds reads as indifference; longer than two minutes reads as nerves. If you’re unsure, err short — a crisp answer invites a follow-up question, which is exactly what you want.

What if I just need the money?

That’s true for most people interviewing right now and it is not disqualifying. Find the true-but-sayable version: something about the work you’d genuinely rather be doing than not doing. “I’m good at this and I’d like to do it somewhere the systems actually work” is honest, specific, and completely acceptable. You’re editing for relevance, not inventing a feeling.

Is “why do you want to work here” the same as “why should we hire you”?

No, and mixing them up is one of the most common errors. “Why do you want to work here” is about fit — the overlap between what you want and what they need. “Why should we hire you” is about qualifications — the evidence you can do the job. Your answer to the first one should include a little evidence, but if it turns into a résumé recital, you’ve answered the wrong question.

How do I answer when I’m changing careers?

Name the transition in your first sentence instead of hoping nobody notices. Then build the bridge explicitly: the thing you did before, the skill it actually trained, and why this role is where you want to use it. Hiding a career change makes interviewers suspicious; explaining it in one calm sentence makes you sound deliberate.

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

Spend fifteen minutes before the interview and you will. If it’s a small or private company with almost no public footprint, pivot from the company to the problem the role exists to solve — you can infer that from the job description. Reasoning out loud about why the role exists is a stronger answer than reciting facts anyway.

Should I mention salary, benefits, or remote work?

Not in this answer. They’re legitimate factors and there’s a right moment for them, usually once mutual interest is established or when the recruiter raises it. Leading with them in an early interview signals that the conditions matter more to you than the work, which may be true but isn’t the impression you’re building here.

How is this different in a phone screen versus a final interview?

In a phone screen, recruiters are filtering for basic fit and genuine interest — keep it to about forty-five seconds and lead with the role. In a final-round interview with a hiring manager or executive, go deeper: tie your answer to the team’s actual priorities and what you’d want to do in the first ninety days. Same three parts, different altitude.

Can I use the same answer for every company?

The structure, yes — that’s the point of having one. The content, no. The company detail must change every single time, and the role detail usually does too. If you catch yourself reusing a specific sentence across four employers, that sentence is too generic to be doing any work for you.

Let’s Practice It Out Loud

Here’s the thing nobody tells you: reading this post will not fix the problem. You already knew most of it. What trips people up is the gap between knowing the structure and delivering it while a stranger looks at you over a video call and types something you can’t see.

That gap closes with practice and feedback, not with more reading.

That’s what interview coaching is for. We run the real interview — this question and the twelve others you’re dreading — and I tell you precisely where you lost the room, which is usually somewhere you’d never have guessed. Clients come in with an answer that’s technically fine and leave with one that sounds like a person. Sessions are available individually or as a full course, and the rates are listed openly because I don’t think pricing should be a mystery.

If you’re not sure that’s what you need yet, that’s fine too — read around the rest of what I’ve written and steal whatever’s useful. I’d rather you got the job with free advice than didn’t get it with none.

But if you’ve got an interview on the calendar and a pit in your stomach about it: that’s the moment to book. Not after.