Why Do You Want to Work Here? The Answer Structure, and 8 Worked Examples

A strong why do you want to work here answer has three parts: something specific about the company that you could not have said about a competitor, something specific about the role itself, and an honest line about where your career is headed. Sixty to ninety seconds, spoken plainly, beats any memorized mission statement.

What the question is actually testing

Interviewers rarely ask this to collect compliments. Three separate hiring risks sit behind the question, and one answer can probe all of them: whether you prepared, whether your motivation is the kind that survives a bad quarter, and whether what this job actually contains lines up with what you say you want next.

Those three things are worth separating, because most weak answers are strong on one and silent on the other two. A candidate who has clearly read the annual report but can't say why this role appeals has answered a third of the question. A candidate who is obviously excited but names nothing specific has answered none of it.

• Did you prepare? This is the cheapest signal to check and the one interviewers weight first, because preparation is a proxy for how you'll treat the work. A single verifiable detail — a product change, a number from an earnings call, a line from the job description — does more than a paragraph of admiration.
• Will the motivation hold? Hiring managers have watched enthusiastic hires quit in month four. They're listening for a reason that is attached to the work rather than to the idea of the company, because the work is what will still be there when the honeymoon ends.
• Does the fit run both ways? A good manager is also checking whether the job can give you what you said you want. If you describe wanting to build and the role is 80% maintenance, a careful interviewer will tell you — and that is a favor, not a rejection.

The retention worry is not imagined. Onboarding-industry surveys put early attrition at levels that would be alarming anywhere else in the business: in one survey of HR leaders, roughly a fifth said that up to half of their new hires leave inside the first 90 days. The magnitude is worth holding loosely — these are vendor-collected surveys, not peer-reviewed research, and the numbers swing hard between sources. The ranking of causes is the durable part, and the reason cited most often is a mismatch between how the job was described and what it turned out to be, ahead of culture, onboarding quality and pay. Your answer is the first place that mismatch can surface, which is a reason to be accurate rather than merely appealing.

The three-part structure that holds up under follow-up questions

Structure matters less for the interviewer's benefit than for yours: it stops you rambling and it guarantees you say the one specific thing that makes the answer memorable. Three beats, roughly twenty to thirty seconds each. Company, role, trajectory. In that order, because the order controls what the follow-up question will be.

Part one: something only this company could claim

Open with a fact, not a feeling. The test is simple — if you could swap in a competitor's name and the sentence still works, the sentence is worthless. "You're an industry leader with a great culture" passes for nobody. "You shipped usage-based pricing in March and it changed how deals in my segment get won" can only be said about one company.

The fact doesn't have to be flattering, and it doesn't have to be big. A pricing change, a documentation rewrite, an acquisition, a published metric that most competitors don't publish, a product decision you disagree with slightly and find interesting. Specificity is the signal; praise is not.

Part two: something specific about the role

This is the part most candidates skip, and it's the part that separates "I want to work at your company" from "I want this job." Quote the job description back, lightly. Which bullet made you apply? Which responsibility have you done before, and which one is new to you in a way you're deliberately choosing?

Naming the responsibility you have not done is unexpectedly strong. It shows you read past the title, and it signals that you're moving toward something rather than away from something — which is exactly the distinction the interviewer is trying to draw.

Part three: the honest trajectory line

Close by connecting the role to where your work is going. One sentence. "I've run the mid-market version of this and I want the enterprise version" is a trajectory. "I'm looking for growth opportunities" is not. The trajectory line is what makes the whole answer sound like a decision instead of an application.

If the honest trajectory is modest — you want stability, you want to stop travelling, you want to go deeper in one craft rather than manage people — say that. Interviewers hear ambition-shaped answers all day and most of them are performances. A plain one lands harder.

1. 1Name one verifiable, company-specific fact and what it told you.
2. 2Name the responsibility in the posting that made you apply, and one you've already done well.
3. 3Say where this sits in your next three to five years, in one sentence.
4. 4Stop. Do not add a fourth reason, and do not summarize the three you just gave.

Where the specifics come from (the About page is the worst source)

Everyone reads the About page, which is exactly why nothing from it can distinguish you. The useful material sits in documents written for other audiences — investors, customers, regulators, and the company's own employees — because those are written to be accurate rather than appealing. An hour in the right places is enough.

• The job description, read twice. Anything repeated across the summary, the responsibilities and the qualifications is the thing they're actually hiring for. Note the verbs: "maintain" and "scale" and "build" describe three different jobs that can share a title.
• The product itself. Sign up, use the free tier, walk into the store, read the changelog or release notes. Ten minutes of real usage produces the kind of detail nobody can fake, and it's available for almost any consumer-facing company.
• Investor material, if they're public. The investor relations page carries earnings call transcripts and the annual 10-K. The Q&A section of a call is the most candid public document a company produces — it's analysts pressing executives on the things that aren't going well. The 10-K's risk factors section, which the SEC requires public companies to file, tells you what management is worried about in writing.
• Press and trade coverage from the last six months. Not the press releases — the trade publications that cover the industry, which will frame the same news with context the company omitted.
• Employee posts. People who work there write about launches, conference talks and internal tooling on LinkedIn. It's the closest thing to a window into daily work, and referencing a specific post ("your staff engineer wrote about moving the pipeline off cron jobs") is unusually precise.
• Review sites, with a discount applied. Glassdoor and similar sites skew toward the delighted and the furious; the contented middle rarely writes anything. Glassdoor's own employer-branding research is the source of the widely repeated figure that around 86% of job seekers read reviews and ratings before applying — a self-reported survey of people already on Glassdoor, so treat it as directional. Either way, assume the interviewer knows what's on there. Use reviews to generate questions, not conclusions.
• The recruiter. Ask the screening call what the team is under pressure to deliver this year. You'll get material for the final round that no other candidate has.

One discipline: check the date on everything. Citing a product that was sunset last spring, a CEO who left in January or a rebrand that happened two years ago converts preparation into its opposite. If you're not sure a fact is current, phrase it as a question instead of a claim.

Eight worked answers, by situation

Company names and details below are invented; the shapes are not. Read these for the moves rather than the words — where the specific fact lands, how the role gets named, how the trajectory sentence closes it. Each one runs roughly sixty to ninety seconds spoken aloud, which is the right length in almost every round.

1. The career changer

The fear you're managing: that you're fleeing a field rather than choosing one. The fix is to show that the new job contains work you were already doing voluntarily in the old one.

I taught ninth-grade biology for six years, and the part I kept volunteering for was rebuilding the unit our department's curriculum kept failing on. When I worked through your Foundations product, the sequencing is doing by design what I was doing by hand on Sunday nights. The posting asks for someone who can write assessment items and then defend them to a subject-matter expert — that's most of what a department meeting is. I want to do that work at the scale software gets you, and I'd rather learn the product side somewhere the content standard is already high.

The move: the transferable skill is demonstrated, not asserted, and the product detail proves the application wasn't mass-produced.

2. The new grad

With little work history, the specific fact carries more weight than usual — it's the main evidence that you'll do homework nobody assigned you.

I got into supply chain through a class project where we modeled a regional distributor's stockouts, and what I liked was that the answer was boring and specific: the reorder point was wrong. Your last earnings call spent most of the analyst Q&A on inventory turns in the Southeast distribution centers, so it sounds like that problem is live here rather than theoretical. The rotational program means I'd see forecasting and transportation before I specialize — and I'd rather not specialize before I've seen both.

The move: a detail pulled from an earnings call transcript is roughly the highest-effort signal a new grad can send, and it costs an hour. Transcripts are free on most investor relations pages and on the financial news sites that syndicate them.

3. Applying to a direct competitor

Three unspoken questions are in the room: are you bringing confidential information, are you just leveraging an offer, and are you going to badmouth your current employer. Address the obvious thing early, keep everything you cite public, and never disparage.

I've been selling against you for two years, so I won't pretend I don't know the product. What made me take the call is the usage-based tier you launched in March — we didn't have an answer for it and I lost two deals on that alone. I'd rather be on the side setting the terms of that conversation. And this is a step up in segment: I've run mid-market, the posting is enterprise with a named-account list, and that's where I want the next five years to go.

The move: the awkwardness is named in the first sentence, which defuses it, and the reason to leave is framed as attraction rather than escape. Note what the answer never does — it cites a public product launch, not anything the candidate learned inside a deal room.

4. The nonprofit or mission-driven role

Mission roles attract more mission-statement recitation than any other category, so hiring managers there are unusually allergic to it. Demonstrate that you understand the operational reality, not just the cause.

I've donated to reentry programs for years, which qualifies me for nothing. What made me apply is that your annual report breaks out housing placement separately from job placement and shows the gap — most organizations in this space don't publish the number that makes them look worse. The role is half data, half sitting with case managers, and I've done the data half at a county agency where the case managers hated the reporting tool I built until I spent a week shadowing them. I'd like to do that again somewhere the reporting is already honest.

The move: the candidate credits the organization for something uncomfortable and true, which is impossible to fake and difficult to say about a competitor.

5. The large enterprise

At 40,000 people, any answer risks being about the brand. The counter is to talk about what scale does to the work, which is a reason only a serious candidate thinks to give.

Honestly, the brand isn't the reason. I've worked at two companies that outgrew their internal tools, and both times the fix stalled because nobody owned the platform. Yours is the first job description I've read that puts platform ownership in the first bullet instead of the last. And at your size there's a version of this job where I see the same problem across six business units instead of one — I've done the one-unit version, and the pattern-matching is what I'm missing.

The move: "the brand isn't the reason" buys credibility for everything after it, and the job-description detail proves the claim.

6. The startup

Founders screen for whether you've priced the risk and whether you understand that the scope is wide and the support is thin. Saying the quiet part out loud is a feature here.

I've read enough of the category to know the Series A was mostly about the compliance layer, and that's the part I find interesting — everyone else ships the demo and hand-waves the audit trail. On the role: twelve people means the first design hire owns research, the system and the marketing site for a while, and I'd rather have that than a narrower job with more scaffolding. I've been at a 400-person company for three years and what I miss is deciding something on Tuesday and seeing it Thursday. I know the tradeoff includes the company not existing in two years. I'd take it.

The move: naming the failure risk without flinching reads as adult, and it pre-empts the founder's own version of the question.

7. The role you mainly want for the money

Compensation is a legitimate reason and a bad complete answer — mostly because it answers a different question. "I need more money" explains why you're leaving, not why you're here rather than at the four other places paying the same. Find the true second reason, and lead with honesty rather than invention.

Two reasons, and I'll be straight about both. One is compensation — I'm at the top of my current band and this range reflects the scope I'm already carrying, so the move is a correction. The other is that the work is closer to what I want: my job now is 80% incident response and 20% building, and this posting is the reverse. I'm not going to claim a lifelong connection to fleet logistics. I will say I've done the on-call version of this job at scale, and I'd like to do the building version.

• Only name compensation out loud if the range is published or it has already come up with the recruiter; otherwise let it stay implied.
• Pair it with a content reason. The interviewer's real fear is that you'll leave for the next raise, and the scope reason is what answers that fear.
• Don't manufacture passion you don't have. Interviewers who hire for a living can hear it, and a false note contaminates the credible parts of the answer.

8. After a layoff, or re-entering the workforce

Urgency can read as indiscriminate — as though any employer would do. The fix isn't to hide the constraint, it's to show you were selective inside it.

I was part of the October reduction, so I've been looking since — which means I've applied to a lot of places, and I should tell you why this one got a real letter instead of a form submission. You're the only lab in the region running the assay in-house rather than outsourcing it, and instrument validation and maintenance is the part of my last job I was best at. I need a job. I'd also like this one specifically, and those two things aren't in conflict.

The move: the last sentence does the work. It concedes the obvious and then refuses to let it be the whole story.

The failure modes, and what to say instead

Most bad answers fail in one of six predictable ways, and each has a clean fix. Recruiters writing about interview red flags describe the same thing from the other side of the table: when a candidate can't give a specific reason for wanting this job, the read is that they're applying indiscriminately. Generic praise, recited mission copy and a focus on what the candidate gets are the three most common versions of that failure.

• Generic praise. "You're a leader in the space with a great culture." Replace the adjective with a fact. If you can't name one, you haven't done the research yet — do it before the call rather than improvising in it.
• Making it entirely about what you get. Growth, mentorship, a better commute, learning opportunities. All real, none of them reasons the company should hire you. Give them a sentence at most, and only after you've said something about the work.
• Reciting the mission statement. Quoting a company's own copy back to it proves you can read a homepage. If the mission genuinely matters to you, cite the evidence that it's real — a published outcome, a decision that cost them money — not the sentence on the wall.
• Over-flattery. Sustained admiration makes interviewers uncomfortable and reads as a negotiating position rather than an assessment. A single critical or curious note ("I'd want to understand how you're handling X") is worth more than three compliments.
• The unverifiable passion claim. "I've always been passionate about payments." Nobody has. Swap it for the moment you actually got interested, which is both true and more interesting.
• Going three minutes long. This is a warm-up question, not the centerpiece. Ninety seconds, then stop and let them ask. The follow-up question is where the real conversation is.

It is not the same question as "why should we hire you"

These two get merged constantly and shouldn't be. "Why do you want to work here" runs from you toward them: your motivation, your fit, your reasons. "Why should we hire you" runs the other way: their problem, your evidence, the case for choosing you over the other finalist. Same interview, opposite direction — Harvard Business Review makes the same distinction, framing the second question as leading with the employer's hopes rather than your own.

Practically, that means the material is different. The motivation question is built from research and self-knowledge. The hiring-case question is built from outcomes — a number you moved, a thing you shipped, a problem that looked like theirs. Prepare both, and don't let the second one colonize the first; an answer to "why us" that turns into a résumé recital sounds evasive.

• "Tell me about yourself." A ninety-second narrative arc, not a motivation statement. We break the opening minutes down in our guide to introducing yourself in an interview, which covers the sequencing this question shares with a pitch.
• "Walk me through a time when…" Structured behavioral evidence. Build a story bank instead of memorizing answers — the method is in our STAR method guide.
• The thirty-second version, outside the interview. A networking event or a recruiter's cold call needs compression, not structure. Our elevator pitch examples cover that format, which is a different instrument from the one on this page.
• "Do you have questions for us?" The mirror image of "why do you want to work here," and the place where your research pays a second time. Our guide to end-of-interview questions organizes them by who's actually in the room.

When it comes up, and how the delivery changes

The same question means slightly different things depending on who is asking and how far along you are. The three-part structure holds throughout; the emphasis shifts. Calibrate by asking yourself what that particular person is still uncertain about, and weight the part of your answer that resolves it.

On a recruiter screen, this question is mostly a filter for effort and a check that you know what the company does. Keep it to forty-five seconds, keep it concrete, and don't spend your best material — the recruiter usually isn't the decision-maker. Our phone interview guide covers the rest of that call, where the real risks are pacing and audio rather than content.

With the hiring manager, part two carries the weight: they want to know you understand the job. In a second interview, the question is often re-asked deliberately to see whether your reasons have changed now that you know more — so update the answer with something you learned in round one. "Last time I said X; after talking to the team I'd add Y" is the strongest possible version, because it proves you were listening.

With an executive in a final round, lead with trajectory. They are underwriting a multi-year bet and want to hear that the role makes sense as a chapter in a coherent career rather than as a lateral move of convenience. Expect a shorter attention span and a sharper follow-up: executives tend to test one claim rather than hear all three.

One thing that sits outside the answer but shapes the first impression: interviewers routinely open your LinkedIn profile before the call, sometimes on a phone, minutes before walking into the room. A current, well-lit photo won't get you hired, but a dark selfie cropped out of a wedding photo creates a small, unnecessary contradiction with a candidate who claims to have prepared. Our LinkedIn profile picture guide covers what actually reads as competent in a small circular crop, and if you'd rather understand the craft than the rules, our plain-English guide to headshot lighting explains why one window beats a ceiling light.

A twenty-minute prep routine the night before

You don't need a script, and a memorized one will hurt you — the delivery goes flat and the follow-up question catches you off balance. What you need is three bullet points you could reconstruct from memory in any order. Twenty minutes, done the evening before rather than in the parking lot.

1. 1Re-read the job description and highlight every phrase that appears more than once. That's the job.
2. 2Find one fact from the last six months — a launch, a filing, a trade story, an employee post — and write one sentence about what it tells you.
3. 3Write the role sentence: the bullet that made you apply, plus one responsibility you've already done well.
4. 4Write the trajectory sentence: where this sits in your next three to five years, in plain language.
5. 5Say all three out loud once, timed. If you're past ninety seconds, cut the adjectives first.
6. 6Write down the one thing you'd genuinely want to ask about the company — it usually falls out of step two, and it's your end-of-interview question.
7. 7Close the notes. Do not rehearse it again; you want the shape, not the wording.

The reason this works isn't that the structure is clever. It's that three specific, true sentences are rarer than they should be. Most candidates arrive with warm feelings and no evidence, so the bar for standing out is one verifiable detail and the honesty to say what you actually want next.