Hiring managers ask why you want this job because they need proof you want the work, not just any offer. Your resume already lists those skills. This question checks whether you understand the duties, care about this company, and can stay motivated after week one.
Have you read the job post twice, or only the salary range?
Career advisors at San Jose State University's School of Information say interviewers listen for sincere interest in the work itself. They also want a career plan that makes this role a logical next step. Generic praise of culture does not cover either point.
Keep the spoken answer near a minute. Specific beats clever.
What they want to hear
The question sounds casual. It isn't.
They screen for three signals. You know what the job does all day. You want those tasks, not a fuzzy title. You can name skills and results that transfer without stretching.
They also want proof you didn't fire the same application at every listing on the board. If you can't explain the work in your own words, they'll assume you applied everywhere.
Salary, remote policy, and brand prestige can be real reasons for you. Lead with them and you sound transactional. Save pay talk for the offer stage.
A strong answer spends most of its time on the role and the team. Your personal story can show up. It shouldn't eat the whole minute.
A formula you can actually say out loud
Thing is, you don't need a speech. You need four beats you can remember when your mind goes blank.
Open with the work you want to do. Tie in one company detail you didn't lift from a slogan. Add one result you've already produced. Close with how you'll help this team next, not how the job will complete you.
Say it in 45 to 60 seconds. If you run long, cut the biography.
Write it the way you'd talk to a person, not a portal. "I'm interested in this operations role because you run same-day fulfillment for mid-market retailers, and I just cut pick-path time 18% at a similar warehouse" beats "I'm passionate about excellence." Practice until that line feels ordinary.
Don't make it about the offer
Pay and benefits matter. They are the wrong headline for this question.
Weak answers versus answers that land
Most people miss here by staying vague, leading with money, or sounding bitter about their current employer.
| What people say | Why it fails | Stronger version |
|---|---|---|
| You have great culture and competitive pay. | Sounds like any job. | Your field team model matches the route planning I used to lift on-time delivery 12%. |
| I need a new challenge. | No research, no fit. | The posting's emphasis on SQL reporting is the work I already do. I rebuilt a weekly pipeline that cut close time two days. |
| I'm ready to leave my current company. | Badmouthing is a flag. | I want to keep doing B2B sales, and your partner program is the channel I grew last year. |
Don't memorize the right column. Swap in your numbers and their products. If you don't have a percentage, use a before-and-after you can defend in a follow-up.
Research the company before you invent a reason
Turns out most generic answers come from skipping 15 minutes of reading.
Use the same stack you already use to apply: the posting on the job board, the company site, Glassdoor reviews and interview notes, and LinkedIn. You're not writing a thesis. You're collecting two facts you can say without sounding like a brochure.
- Read the job description again. Highlight duties, tools, and outcomes. Circle two you can honestly claim.
- Open the company site. Product pages and recent news beat the About page. Only cite the mission if you can connect it to work you've done.
- Skim Glassdoor for repeated themes, then open the Interviews tab. Authentic reviews mention tools, processes, or managers. Skip one-line rants.
- Check the LinkedIn company page and a few people on the team. If you know who is interviewing you, glance at their path so you don't talk past them.
- Look at one competitor only if it helps you say why this shop, not the other one.
Our Glassdoor research walkthrough covers how to read reviews without treating a single complaint as the whole culture.
Read the posting. Read it again. The first pass is keywords. The second pass is the actual job.
If 10 minutes of this work produces nothing you respect, that's useful. You can still interview. You shouldn't fake a calling.
Stuffing every product name from the homepage into a one-minute answer is a common way to sound prepared while still missing the point, because the hiring manager mostly wants to know if you'd enjoy the daily work of the role you applied for, which is simpler to say if you've ignored the marketing adjectives and stuck to duties you can actually do.
Sample answers you can reshape
Don't treat these as scripts. Change the company facts. Change the metrics. Record yourself once and listen for filler.
For an entry-level coordinator role, try this shape. "I'm applying because this job is built around campaign tracking and vendor follow-up, which is the work I did as an intern. Your team ships weekly product emails, and I built a tracker that cut our send errors 20%. I want to do that work here and grow into the analyst seat you mentioned in the posting."
A backend role can be shorter. "I want this job because you're rebuilding the payments service, not babysitting a quiet app. I spent two years on Node services and cut API latency 15% on a similar checkout path. Your engineering notes on retries match how I already design jobs."
Sales works when you name the motion. "Your SDR seat is outbound into mid-market finance, which is the book I already run. I tightened list hygiene last year and kept more second meetings. I want this job because that motion is what I'm good at, and your partner overlay gives me a second door into the same accounts."
Managers should sound like they already see the problem. "I want to lead this team because the posting is about fixing a messy handoff between support and product, not collecting a title. I ran a similar overhaul and got two squads onto one weekly metric. Threads on Glassdoor about that handoff told me the pain is real, and that's the work I like."
Each version names the work first. Then a company detail. Then proof. Then a forward step. If your proof has no clean percentage, say what changed: two days faster, fewer errors, one tool retired.
Use STAR only for the proof
STAR (Situation, Task, Action, Result) backs one claim. It shouldn't swallow the whole answer.
Start with why this role is on your list. Drop one short STAR so the "why" has evidence. End by pointing that result at their team.
Here's a compact version. Situation: the sales pod missed renewals. Task: stabilize the book. Action: I rebuilt the follow-up sequence and sat with customer success on churn calls. Result: more closed-won deals and better retention. Last line: that motion is what your partner program needs.
Keep the story tight. If you don't have a number, say the change in plain English.
LinkedIn's Interview Prep tool gives you common questions, extra prompts by job title, and a written-answer cap that forces you to cut. Use it to hear whether you ramble. Don't paste those drafts as your live answer.
LinkedIn Learning's interview prep lesson walks through the company page and the people who may interview you. Fifteen to 20 minutes is enough if you actually use what you find.
If you don't have flashy numbers yet
Plenty of strong candidates don't have a 30% story. That's fine.
Use a concrete change. You documented a process that used to live in someone's head. You cut a report from Friday to Wednesday. You trained two people so tickets didn't sit.
Hiring managers can test those claims. They can't test "I'm a hard worker."
Students and career switchers can pull from internships, class projects, volunteer ops, or a freelance gig. Name the work in their posting. Then prove you've already touched something like it.
Career changes and internal moves
Career-change answers fail, to be honest, when they sound like an apology.
Don't trash the old field. Name the work that already transferred. "Customer conversations taught me to spot repeat defect patterns. I started logging them, and the fix rate went up. That's why I want this data role, not because I need a change."
Internal promotions should sound like continuation. "I've already automated the HR intake that ate the team's week, and this lead role is the same problem at a wider scope. I want it because I know the bottlenecks and people already trust me on them."
Switching industries costs you extra product homework. One accurate detail about how they sell or ship beats a paragraph about being a fast learner.
If they ask why this company instead
"Why us" tilts toward the employer. Don't recycle a pure role speech.
Name something this company actually does: a product, a market, a way they staff the team. Snap it back to the job in the next sentence. "I want to work here because you sell into clinics that still run paper intake, and this implementation role is how that software lands."
If you applied through a wide job-board blast, they can often tell. The fix is still research, not a confession that you clicked Apply on twelve tabs.
Remote or hybrid setups belong in the same logic. If they ask, talk about how you already deliver async work. Don't make the answer about your commute.
Prep this in 30 minutes
- [ ] Ten minutes: reread the JD, one news item, Glassdoor interview notes, and the LinkedIn team page.
- [ ] Ten minutes: pick two duties, one company fact, and one result with a number or a clear before-and-after.
- [ ] Ten minutes: say the answer out loud twice. Cut pay, "great culture," and any line about needing a job. Time it. If it runs past a minute, cut the origin story.
Practice once more the morning of. Don't rewrite it in the lobby.
Write four beats on a note: the work, one company fact, one result, one way you'll help next. Draft it in spoken English in your notes app. Read it against the posting one more time, then go in and say it like a person who actually wants the job.