Why do you want to join our company, and what your answer is really being scored on

On 6 September 2026 I re-read Gallup’s page on why the manager-employee relationship matters, still live at gallup.com/workplace. It’s dated 2019, but the number hasn’t aged: 52% of employees who quit voluntarily say their manager or the company could have done something to prevent it. Nobody asked, or nobody listened. That’s the fact sitting behind “why do you want to join our company” every time it gets asked, and it’s why the question isn’t really about enthusiasm.

It’s a retention-risk screen wearing an enthusiasm costume. The interviewer isn’t measuring how much you want the job. They’re measuring how likely you are to quit in eleven months, because replacing you costs real money and their name is on the requisition.

Why do you want to join our company? What it’s actually screening for

Recruiters and hiring managers have both been burned by a candidate who said all the right things and left before the first year mark. So the question does three jobs at once: it checks whether you understand what the role actually involves, whether your reasons for leaving your last job will show up again here, and whether you sound like you researched this company specifically or copy-pasted the same answer into four tabs.

Generic answers fail on all three counts simultaneously. “I love the mission and the growth opportunities” could be said to any company in any industry, and interviewers have heard it enough times to tune it out mid-sentence.

There’s a real base rate behind the caution. The 2025 Stack Overflow Developer Survey found 45.6% of developers globally are not actively seeking a new role, and only 24.5% describe themselves as happy at work. Read those two together and most hires are, at best, mildly restless rather than genuinely pulled toward a specific employer, which is exactly why a convincingly specific answer stands out. Most candidates aren’t giving one.

A structure that survives follow-up questions

The answers that hold up in the room share a shape, and it’s three parts, not five, because five-part frameworks are what get memorized badly. I think most of the five- and six-step interview frameworks floating around LinkedIn are coach theater more than usable advice. Nobody actually holds four transitions in working memory under pressure, and the ones who try sound like they’re reciting a menu.

Part one: a specific, verifiable reason tied to this company. Not “your mission,” which is what every applicant says. Something you could only know by actually looking, a product decision, a technical choice, a market they entered that a competitor didn’t.

Part two: why now, connected to your own trajectory. This is where you explain what you’re leaving behind or moving toward, briefly, without trashing anyone.

Part three: what you bring that closes a gap they likely have. Not a list of your skills. One thing, tied to something in the job description or the conversation so far.

Three parts, thirty to forty-five seconds. Longer than that and you’re performing rather than answering, and performing is the thing interviewers are trained to notice.

Practice the transitions more than the content. Most rehearsed answers fail not because the facts are wrong but because the seams show, a long pause before part two, a memorized phrase that doesn’t match how the candidate talks in the rest of the interview. Say it out loud a few times, changing a word or two each pass, so the shape sticks without the exact sentence getting frozen in place.

Four worked answers for different situations

The fresher. “I looked at three companies building in this space, and yours was the only one where the engineering blog actually explained a tradeoff instead of just announcing a feature. That told me the team writes things down, which matters more to me as a new grad than the brand name. I don’t have production experience yet, but I shipped two projects this year that needed the same debugging discipline your postings ask for, and I want to build that habit somewhere that already has it.”

The service-to-product switcher. “I’ve spent four years maintaining client systems where the requirements came from someone else’s contract, not from user data. I want to work somewhere the roadmap is driven by what people actually do with the product, and your last two releases both cite usage numbers in the changelog, which is rare. I bring four years of production discipline that a lot of product-side candidates skip straight past.”

Two answers for candidates explaining a gap or an exit

The laid-off candidate. “I was part of a reduction in March when the team’s budget was cut by forty percent, not a performance issue, and I can put you in touch with my manager there if that’s useful. Since then I’ve been narrowing my search to companies that are still hiring for this role specifically, rather than applying broadly, and yours came up because of how the JD described the on-call rotation. It’s the same shape of problem I was solving before, at a company that’s apparently still funding the team.”

Leaving after eleven months. “I took the last role expecting more ownership over the data pipeline, and the reorg six months in moved that work to a different team before I got to touch it. I’m not leaving because I dislike the company. I’m leaving because the actual job stopped matching what I was hired to do, and yours is scoped closer to what I was looking for the first time around.”

What makes an answer sound rehearsed

Timing matters here too. Answer this question too early, before you’ve asked anything about the role yourself, and it reads as scripted regardless of content, because you haven’t earned the specifics yet. Answer it too late, after four other questions, and it can read as an afterthought. Somewhere in the first third of the conversation is usually right, right after the interviewer has described the role but before you’ve asked your own questions.

Three tells, and interviewers spot all of them fast. A superlative with no evidence (“this is my dream company”) reads as filler because it can’t be checked. A reason that applies to literally any employer in the sector reads as generic even if it’s true. And a delivery that’s too smooth, no pause, no hedge, no specific noun, reads as memorized even when the content underneath is genuinely honest.

The fix for all three is the same: cite something you can only know by having actually looked, a specific product, a specific person, a specific number from their own site. I don’t know if this generalizes to every industry. In fast-moving fields where public information is thin, like early-stage hardware or defense contracting, a generic answer might be all you have, and that’s a fair gap in this advice.

The limits of this advice

If the eleven-month version of this answer is closer to your situation, our why are you leaving your current job post goes deeper into that framing without sounding defensive. And if you’re still building the rest of the pitch, tell me about yourself covers the opener this question usually follows, while why should we hire you covers the close.

One honest caveat: none of this fully works if the role itself is a bad fit. A well-built answer gets you past this question, but it doesn’t fix a mismatch between what you want and what the job actually is, and I’d rather you catch that in the interview than six months into the job.

The interviewer isn’t asking because they doubt you want the job. They’re asking because the last three people who said yes enthusiastically left within a year, and somebody above them wants a better filter than a vibe.