Hiring managers ask "Why do you want this job?" to hear whether you picked this role on purpose. Can you name the work, not just the logo?
A usable answer runs about 45 to 60 seconds. It shows you read the posting, you can handle the core tasks, and this job fits a direction you already started. Empty praise falls flat. A speech about benefits does too.
What they're screening for
They're checking research and intent, not how warmly you describe the brand. The job is the subject.
Build a three-part answer
Keep the center of gravity on the work. Recruiters at Michael Page treat this as a cluster of questions: what you know about the company, how the role sits in your plan, and why this employer appeals. Harvard FAS Career Services is blunter. Employers want to know why they should hire you.
Talk through this sequence once, then trim:
- The role. Name one duty or problem from the job description.
- Your proof. Connect a skill or a result you already have.
- This employer. Say why this team, product, or customer, not a clone role at another firm.
Time it on your phone. If you wander into childhood stories, cut them. A short personal reason is fine. It should not eat the whole answer.
Do the research on the posting, not in your head
Thing is, you can't fake specifics if you never left the job board. Open the listing on LinkedIn, Indeed, or the company's own careers page. Underline two responsibilities you can defend in a room. Then jump to the About, product, or news page and grab one fact you did not invent: a customer group, a product line, a hiring push in the same function.
Ten focused minutes beat an all-night rabbit hole.
If you spent last night reading every review thread and still plan to say "I love your culture," you didn't research, you grazed, and interviewers hear that thinness in the first sentence while you're still smiling at the camera.
Match the same themes you already put on your resume. If an applicant tracking system parsed your file for Python, stakeholder updates, or outbound outreach, those words should show up naturally when you talk. Consistency beats clever phrasing.
Work this in order:
- Copy two must-have duties from the job-board posting.
- Pull one company detail from the careers site.
- Match one resume bullet to those duties.
- Draft 45 seconds and read it aloud.
Generic vs tailored: what changes in the room
| Piece of the answer | Generic (they tune out) | Tailored (they lean in) |
|---|---|---|
| Opening | "I've always admired your company." | "Your claims team is rebuilding the provider portal, and that's the work I want." |
| Role fit | "This is a great opportunity." | "The posting's mix of SQL and weekly stakeholder recaps is the work I already do." |
| Motivation | "I'm looking for growth." | "I want a seat closer to the product decisions, which this IC role actually has." |
| Company reason | "You're a leader in the space." | "You're hiring two more ops analysts after the Midwest launch. I want on that ramp." |
The tailored column is longer on purpose. Specifics take a few extra words. They also sound like a person who applied on purpose.
Sample answers (steal the shape, not the facts)
Swap the brackets for your posting. Don't recite someone else's metrics.
Software engineer. "I applied because this role owns the payments API, not a ticket pile with no owner. At my last job I spent two years reducing checkout failures on a similar stack, and I want that same problem with your volume. Your careers page also shows you're hiring platform and fraud in the same quarter. That's the kind of team I want to sit on."
Digital marketing. Short version: name the channel they actually use. "Your job post is not a generic 'do social' brief. You want someone who can take paid search and the email lifecycle together. I ran that pairing for a DTC brand and I want to do it where the catalog is bigger. That's why I clicked apply on this listing, not the five lookalikes."
Entry-level answers should sound hungry without sounding lost. "I don't have five years in the title. I do have a semester of the same CRM you named, plus a campus project that used it for real outreach. Your rotational program is the reason I applied here instead of a random coordinator posting. I want the structured reps."
Career switchers need the transfer, said once. "I'm leaving banking ops because the work I liked was the data cleanup, not the product. Your operations analyst role is that work with a clearer path. I already rebuilt a reporting cadence my old team still uses. I want to point that habit at your onboarding funnel."
Managers can skip the origin story. Talk about the problem on the posting. "You need someone who can stand up a five-person support pod without blowing up quality. I did that split last year when we doubled ticket volume. I want this job because the scope is the pod plus the vendor relationship, which is the next seat I'm trying to take."
Internal candidates should not pretend they're outsiders. "I've sat next to this team for 18 months. I know the backlog and I know who gets stuck. The lead role is the natural next step because I've already covered the queue and the client call. I want the title that matches the work."
None of these mention salary. Save that for the offer conversation.
Use STAR when they ask for a story, not as a speech
You don't need a full STAR recitation for "why this job." Use it when they follow up with "tell me about a time." Harvard's interviewing notes tell you to pick the situation first, then talk. Keep the result visible.
Here's one pass, said like a person, not a worksheet. Situation: my last team missed a client deadline after a tool migration. Task: I had to rebuild the weekly status without extra headcount. Action: I cut the report to five metrics and ran a 15-minute standup. Result: we stopped missing the Friday send. Reflection, one line: that's the kind of messy process work your operations posting describes, which is why I want it.
MIT's interview primer treats the meeting as two-way. You're also deciding whether you can see yourself with these people. If their answers about the team feel off, that belongs in your notes. It does not belong in this particular answer.
Answers that quietly sink you
Turns out the failures are boringly similar.
Leading with money makes you sound transactional. So does "I just need a job," even when that's true at home. Complaining about your current boss hands them a preview of how you'll talk about them later. Reciting a mission statement you could have pasted onto any competitor tells them you did not open the posting. A perfectly smooth paragraph that sounds like a chatbot is another tell. They'd rather hear you pause than hear a script.
Arrogance without an example is almost as bad. "I'd be a great fit" is not proof. One duty plus one result is.
Practice on camera, then close the loop
To be honest, most people write a decent draft and never hear it out loud. Your first recording will be too long. That's normal. Cut until it fits in a minute without sprinting.
Use this checklist before the call:
- [ ] Two duties from the job-board posting, said in your own words
- [ ] One company fact that is not "great culture"
- [ ] One proof point that already lives on your resume
- [ ] One phone recording, watched once for filler words
- [ ] Virtual: join 1-2 minutes early; in person: arrive 10-15 minutes early
- [ ] Thank-you email within 24-48 hours, with one detail from the conversation
Those timing and follow-up habits come from Harvard's interviewing resource. They won't rescue a vague answer. They do keep a good one from looking sloppy.
If you use a job-search app or LinkedIn Easy Apply, don't stop at the tap. The same posting you applied through is the script for this question. Pull it up again the night before. Read the requirements out loud. Then answer as if the hiring manager has that tab open, because they might.
Questions people still have
Why do they ask this so early? It sets whether you did homework. It also confirms you want this seat, not a random offer.
Can I talk about growth? Yes, if you tie it to the work they need done. "I want to learn" with no job detail sounds like they would be funding your education.
What if I'm changing careers? Name the transferable task once. Then stop narrating your whole pivot.
Should I mention the job board or the app I used? Only if it matters. "I saw the role on your careers page after following the product launch" is useful. "I mass-applied on my phone" is not.
Open the posting you already submitted. Write three sentences that follow role, proof, employer. Record them once before the next round. If you can't say it without looking down, it isn't ready.