Hiring managers ask why you want this job because a resume can't show whether you actually want these tasks, this team, and this company's current problems. They decide in about a minute.
Ever freeze and default to "it's a great company"? That sentence tells them nothing.
You need a specific answer you can say out loud. Name the work. Tie it to a result you already have. Pull details from the job posting, the career site, LinkedIn, and Glassdoor, then stop collecting tabs and start practicing.
What this question is really testing
Interviewers want proof you understand the role and want those responsibilities, not a random opening on a job board. They're also checking whether your skills map to a problem they already need solved.
A spoken formula that fits in two minutes
Keep four beats so you don't ramble.
- Name one specific detail from the company, product, team, or posting.
- Connect that detail to work you have already done.
- Give one result, with a number if you can defend it.
- Close on the contribution you want to make in this role.
Thing is, the part about your own growth should stay small. Lead with their work. Mention your path in a final clause if it helps, then stop.
Write a draft, then cut it. If a sentence would sound odd to a coworker, delete it. Interview-practice tools can flag pacing. They can't invent a reason you don't have.
Swap your details into this skeleton:
"I've been paying attention to [Company]'s [product, launch, or way of working] because it lines up with my work in [skill]. At [previous role] I [action], which led to [result]. I want this job because the posting's focus on [duty] is the problem I want to spend my week on, and I can start contributing there."
Time yourself. Aim for 60 to 90 seconds. Longer usually means you added autobiography.
Research the company without burning a weekend
Read the posting like a task list. Mark three duties you would do in week one. Skim the company site for customers and anything they announced recently. LinkedIn shows how employees describe the work. Glassdoor is better for patterns than for ammunition.
LinkedIn advice on researching a company before an interview points at a simple trio: people, product, and customers. That's plenty.
Make a one-page cheat sheet:
- Three duties copied in the employer's wording
- One recent public detail (launch, market, or team news)
- One value you can say without acting
- One resume bullet that matches a requirement
- One honest question about tools, team, or success in the role
Check the posting in the applicant tracking system if that's where you applied. Workday, Greenhouse, and Lever sometimes keep requirements that job boards shorten. When your spoken answer uses their phrases, the recruiter hears continuity, not copy-paste.
You don't need a war-room binder on the company, and you don't need to memorize five years of filings, because the person across the table can tell when you are reciting trivia and still can't say what you'd do on a normal Tuesday, so grab a few facts that connect to your real work and leave the rest closed.
Entry-level answers can lean on internships, class projects, or campus jobs. Manager answers need a leadership result. Don't invent a percentage you can't explain if they ask how you counted it.
Sample answers to copy the shape from
Steal the structure. Don't steal the sentences. Brand-name Mad Libs get spotted.
Marketing coordinator (entry-level)
"I've watched how you talk about product and community in your campaigns, especially the last seasonal launch. In my internship I ran social for a campus group and grew engagement by tracking comments and shares, not just likes. This coordinator role makes that work the job, and that's the work I want."
Tech support (entry-level)
"Your support model is about getting people unstuck, which is the part of tech I like. I staffed a student help desk, wrote down the fixes, and cut repeat questions with a short FAQ. I want this job because the posting is patient troubleshooting, not just closing tickets."
Sales manager
"I coached a small team through a rough quarter and we finished 25% above the prior year after we cleaned the pipeline and ran tighter weekly reviews. Your posting reads like process and coaching, not lone-wolf heroics. I want this job because those are the problems I already like managing."
Project manager
"The description calls out delivery when scope keeps moving. That's most of my week. I led 15 projects last year and we hit dates by dropping extra status meetings and putting risks on one page. I want to do that here, especially if vendors are in the mix the way the posting suggests."
Career change into operations
"I coordinated schedules and follow-up in a clinic, so I already know how small gaps turn into missed appointments. Your operations team is doing that work at scale. I want this job because the duties match what people already asked me to do, not because I'm running from my old field."
Turns out the same shape works if you change fields. A finance answer should name a real process on the posting, like close, risk, or audit support. A nonprofit answer should mix mission with the actual job, fundraising ops or program logistics, not a donation speech. Retail can talk conversion, staffing, or in-store execution if that's on the page.
Internal candidates should be blunt. You've done the adjacent work. You know the tools. This role is the next problem set.
If they want a story, tuck a short STAR beat inside the result: situation, what you owned, what you did, what changed. Then snap back to this job. Don't let the anecdote eat the answer.
You don't need a perfect story. You need a true one. A true one you can repeat when they ask it twice.
Weak answers versus answers that sound like research
| Weak line | Why it falls flat | Stronger line |
|---|---|---|
| "It's a great company." | No evidence you looked | "Your latest launch and the posting's focus on X match the work I did at Y." |
| "I need a job" or jumping straight to pay | Sounds like any offer would do | Start with the work; leave compensation for the offer stage |
| "I love the culture." | Empty without a detail | "Public posts and reviews keep mentioning [specific habit], which is how I like to work." |
| "I'm a hard worker." | Anyone can claim it | "I [action] and got [result], which maps to your [duty] requirement." |
Read your draft against the left column. If it could fit 50 other companies, rewrite it.
Mistakes that make you interchangeable
Recruiters hear these all week.
- Leading with salary, title, remote days, or "I just need something in this field"
- Paraphrasing the About page with no link to the role
- Using your current boss as the villain
- Reading an AI paragraph you have never said out loud
- Claiming culture fit without one example
Glassdoor dirt is not an interview strategy. If reviews mention change, stay curious: you saw they're adjusting how teams ship, and that's part of why the role interested you. Don't cross-examine them.
Use LinkedIn, Glassdoor, and job apps as a prep desk
The posting you clicked is the source of truth. Save it from LinkedIn Jobs, Indeed, or the company career site. Requirements move. You want the version attached to your application.
LinkedIn is for language and people. Scan the hiring manager's recent posts and a few people who already do the job. Borrow a verb or two. Do not recap their career at them. That feels like stalking, not interest.
Glassdoor is for themes. Repeated comments about mentorship, pace, or bureaucracy tell you what "fit" might mean. Pick a theme you actually share. Skip the one-star novel.
Resume tools and ATS views help you stay consistent. U.S. hiring teams often screen in software first, then meet you on video. If you applied through Workday, Greenhouse, or Lever, the recruiter already saw that phrasing. When your answer restates a requirement they ranked you on, you're aligned with the file.
Record one practice take on your phone. Some interview-practice features flag fillers and speed. Use that once. Then talk like a person. Over-smooth answers sound generated, especially on camera.
Most candidates over-research the brand story and under-research the Tuesday tasks. To be honest, I'd flip that ratio.
When they ask it again, and what you send later
They may rephrase: why this company, why this role, why now. Keep the same three beats. You don't need a childhood origin story. "The work matches what I'm already good at, and you're hiring for it now" is enough.
If they ask how you prepared, name the posting, one public update, and one employee or product detail. That's research. Reciting trivia isn't.
Send a short thank-you the same day. Restate one duty and one way you'd help. A LinkedIn connect is optional and should feel normal for that industry, not like a second pitch.
If one answer came out messy, tighten that point in the note. Don't recap the whole hour.
Open the posting you applied to. Write four lines: company detail, matching skill, one result, what you'd do here. Record 90 seconds. Cut anything you wouldn't say to a person. That's the answer you take into the room.