Hiring managers ask "Why do you want this job?" to test whether you picked this role on purpose. They are not fishing for flattery.
Can you name the work, one true company detail, and a result you already own?
MIT's Career Development Office wants three pieces in one answer: why this company, why this position, and why you will succeed in it. That mix beats a speech about passion. It also beats "I need a job."
Open the posting on the job board or employer site where you applied, pull two duties you can actually speak to, and skip the fluffy values paragraph until those duties are in your notes. Your answer depends on those duties. Check the company LinkedIn page next. Skim Glassdoor interview notes if they exist.
Aim for 45 to 90 seconds. Sit down and time it.
A direct answer to why you want this job
Start with a fact only their team would recognize. Then connect a skill you have to a duty on the posting. Close with the contribution you want to make, not a five-year fantasy.
Use this shape, then rewrite it in your own words:
"I'm interested in [Company] because [specific product, customer, or team problem]. This job's focus on [duty from the posting] is the work I already do well. At my last role I [result], and I want to bring that same habit here."
Read it out loud. If it sounds like your cover letter, cut adjectives.
A filled-in version:
"I'm interested in this customer success opening because your team owns onboarding, not just inbox volume. The posting asks for someone who can build first-week playbooks. That's what I did in my last role, where I tightened the first-week checklist and new accounts got productive faster. I want that same hands-on work on a product I already know."
Company, role, proof. MIT says the strongest answers combine all three. Keep personal motivation short. The work should lead.
You'll hear close cousins of this question: why do you want to work here, why this role, why us. Same three parts. Swap the emphasis if they stress the company versus the seat.
What the interviewer is trying to learn
Harvard FAS Career Services boils the whole interview down to one worry: why should we hire you. This question is that worry in disguise.
They listen for research. They listen for whether the day-to-day matches what you say you want. They listen for a reason you might stay.
"Great culture" without an example is empty. So is "I've always admired you" if you cannot name a product.
Expect a follow-up. "What do you know about us?" is common. Keep one extra fact in your pocket. One product launch, one team ritual, one customer they serve. You don't need a dossier.
Skills-based hiring is real. If the posting lists tools, name the ones you have used. If you have not used them, name the closest stack and stop talking.
Lines that fail, and lines that hold up
Recruiters hear the same generic answers all week. You do not want to be that clip.
| Weak answer | What it signals | Stronger answer |
|---|---|---|
| It's a great opportunity. | Zero research. | Your implementation group runs 30-day cutovers, and I've led those. |
| I need a paycheck. | You'll leave for a slightly better one. | This analyst seat is the next step after two years of weekly SQL reporting. |
| I love the brand. | Fan, not coworker. | The role owns lifecycle email, which is the work I want more of. |
| The commute and benefits work. | Transactional. | I want the quota-carrying job, not a support seat that never talks to buyers. |
Thing is, compensation can wait for the offer conversation. Lead with the work itself.
If you only compliment the company, you sound like you would take any opening there. If you only talk about your growth path, you sound like the job is a stepping stool. Pair them in the same breath.
A candidate who cites the actual tech stack or the actual quota motion almost always beats the one who says "great company." You already have that material on the posting.
Research the posting like it is a brief
You cannot give a specific answer without a specific fact. Ten sharp minutes beat a vague evening of "prep."
- Highlight must-have skills on the job description in your job board, ATS portal, or saved PDF.
- Scan the company LinkedIn page for one product, customer, or team post you can mention honestly.
- Skim Glassdoor interview blurbs for that title if they exist, and treat them as hints, not gospel.
- Map two resume bullets to two duties. If your resume tool already tagged those bullets, use them.
- Draft a 60-second answer that names the company, the role, and one result.
- Record it in LinkedIn Interview Prep or a voice memo. Cut anything you would not say to a person.
Skip the corporate about-page poetry. Hiring managers wrote the requirements. Match those.
Transferable skills work when you name the transfer. "I have not sold SaaS, but I closed vendors for a campus org and kept a budget" is usable. "I'm a quick learner" is not.
Write the draft before you schedule the interview, not in the parking lot.
Sample answers to rewrite, not recite
Steal the structure. Change every noun.
Entry-level. "I want this operations coordinator job because the posting is about process documentation, and that's the work I already like. During my internship I built a shared tracker for campus events so rooms and vendors stopped colliding. I'm looking for a team that will let me own a system like that, not just send calendar holds."
Behind that is a small STAR story: events were slipping, I had to keep vendors straight, I built the tracker, fewer day-of surprises. MIT's STAR worksheet tells you to spend most of the story on your actions, not the setup.
Manager. "You asked for someone who can clean up the sales-to-delivery handoff. That's the job I want. On my last team both groups were dropping the same details in chat, so I sat them down, mapped the steps, and we stopped relitigating kickoff every week. I would start that work here in the first month, not after a long observation period."
Turns out managers get dinged for sounding like they need a tour first. Offer a first-month move.
Tech. "I applied because this role builds internal tools, not another consumer surface. I spent two years on a reporting service finance actually used, and I like that unglamorous reliability. The stack in your posting is what I work in now, including the parts nobody demos in a keynote."
Sales. "I want a full-cycle seat, which is what you posted. Last year I owned outbound through close and beat quota by working fewer, better-fit accounts instead of spraying the list. Your motion reads consultative. That's already how I sell."
Keep a real metric if you have one. Invent nothing. If you cannot defend a percentage in a follow-up, drop it.
If you're switching fields, say the switch out loud instead of hoping they won't notice, because they will notice, and a clean line like "I left classroom teaching because I want to do curriculum design inside a product team, and this role is that work" holds up so much better than a long claim about being passionate about learning, which is what half the room will say and which doesn't tell them why this job rather than any job with a laptop.
Remote or hybrid postings still need the same three parts. Mention the model only if it changes how you do the work: "I've shipped on distributed teams and your hybrid setup matches how I already run standups." Don't make location the headline.
Add STAR when they ask for a story
Sometimes "Why do you want this role?" is a behavioral trap. They want past behavior as a clue to future behavior. That's the point of behavioral interviews, per MIT CAPD.
Prep 3 to 5 stories. Outline them. Don't script every word.
Give the situation in one sentence so they have context. Name the task you owned. Spend most of your time on the actions you personally took. Close with a result you can stand behind.
MIT's worksheet even splits the airtime: about 20% situation, 60% action, 10% result. You do not need every detail of the old org chart.
Then snap back to this job: "That's why this role appeals to me. You need someone who already did that coordination."
A flat version sounds like "I like projects." A STAR version sounds like "A client had a hard deadline, I coordinated the handoffs, and we hit the date." Same energy, more proof.
Rehearse with the job search stack you already use
You found the role on a board. Keep using that stack.
The morning of the interview, reread the posting. Your resume or tracker should show which bullets you tailored. Those are the proof points. Say them without looking down.
LinkedIn Interview Prep lets you pick common questions, record an answer, and get automated notes. Use it for "Why do you want this job?" Then throw out any line that doesn't sound like you. Interviewers can hear a template.
Glassdoor write-ups can flag follow-ups. They can also be stale or petty. Don't quote them.
To be honest, the thank-you email is still an easy place to lose the thread. Harvard's interviewing notes say send it within 24 to 48 hours. Restate one specific reason you want the job. Skip the autobiography.
Show up 10 to 15 minutes early if it's in person. For video, one or two minutes is enough. Confirm the link the night before.
Write your three-part answer tonight. Time it to 90 seconds or less. Record it once, listen for the sentence that still could fit any company, and replace that sentence with a duty from the posting.