How do you convince an interviewer that their job is the one you actually want, not just any open seat?
Hiring managers ask this for two reasons, and neither is small talk. They're checking whether you understand what the work really involves. They also want proof you're running toward this opening instead of fleeing a bad manager.
The strongest answers stitch three things together: a specific detail from the job listing that caught your eye, a real past achievement that solves their current problem, and a line connecting this role to where your career is headed. Say all of that out loud in 45 to 75 seconds. Go longer and you're rambling through your biography. Go shorter and you sound like you skimmed the post on your phone.
What Recruiters Are Actually Checking
This prompt usually lands early in a phone screen, and its real job is catching autopilot applicants. If you blasted fifty resumes through a one-click board without reading a single team description, it shows up here fast.
Weak answers run on push factors. You complain about your salary, a toxic boss, or the remote flexibility that vanished last year. Every word of it might be true. Dumping those complaints on an interviewer still reads as flight risk.
Strong candidates build a pull narrative instead. That means company momentum, a specific product initiative, or an internal workflow that makes this team the logical next step for your talent. Thing is, hiring managers want someone who picked them on purpose, not someone collecting offers.
Gathering Clues from Job Boards and Review Sites
Twenty minutes of research before you write a word. That's the whole assignment, and generic praise about an innovative culture won't survive it.
Open the original posting on Indeed or LinkedIn and read the verbs first. When a listing says cross-functional collaboration four separate times, your answer should find room for team alignment. Next, check employer review apps for company sentiment. A structured Glassdoor company research workflow helps you spot recurring operational themes, organizational shifts, and the interview questions that keep coming up, all before you ever hop on a phone screen. Patterns across multiple reviews matter more than one bitter rant. Last, search press releases or leadership posts on LinkedIn, because citing an expansion into a new market shows initiative that ninety percent of candidates never bother with.
The 3-Step Answer Framework
No script required. You need a frame sturdy enough to rebuild under pressure.
- Name a specific hook from the company or the post itself. A recent project, a product line, an operational standard you dug up during research.
- Attach one past win that proves you can do the work. A single metric or milestone that mirrors what this job does every day.
- Close on timing. Tie the responsibilities back to your trajectory without making the whole answer about what you personally get out of it.
Applying the STAR Method to Role Motivation
Most job seekers save behavioral stories for conflict and failure questions. That's a missed opportunity, because anchoring your motivation in the STAR interview method swaps vague promises for proof.
Situation: "At my last SaaS company, our sales engineering team had to shorten onboarding times for enterprise clients."
Task: "I was assigned to overhaul the technical demo workflow to reduce client drop-off during trial phases."
Action: "I built standardized sandbox environments and ran targeted training sessions for our enterprise account executives."
Result: "Our trial conversion rate jumped 24 percent within four months. When I saw your team expanding its enterprise onboarding tools on LinkedIn, I recognized the exact challenge I just solved."
Told this way, the story does the persuading for you. You're not just drawn to the company brand. You already understand the work sitting on that desk.
Scripted Examples Across Common Job Scenarios
Tech Sales or Account Management
"Your posting says the team is actively scaling enterprise accounts in healthcare tech, and that's where I've spent the past two years. At my current firm I closed twelve enterprise accounts by mapping custom workflow demos to specific clinical bottlenecks, which grew our pipeline value by 35 percent. The catch is that my company has pivoted toward small business subscriptions, so the big deals I'm best at rarely cross my desk anymore. This opening puts my healthcare sales background on a high-growth pipeline where enterprise accounts are the entire focus."
Entry-Level Applicant
"During my final semester I coordinated digital outreach for our university business network, managing email sequences that raised event attendance by 20 percent. While going through your job posting and recent company updates, I noticed your client services team needs someone who can handle customer communication across multiple channels right away, not eventually. I'm eager to build on those coordination skills somewhere with established training tracks, and your reputation for promoting entry-level hires from within makes this role the right first step for my career."
Remote or Hybrid Role
"I've spent the past three years on distributed engineering teams, where clear written documentation carries everything. Turns out, proactive communication kept my last team ahead on quarterly sprints without a single daily status meeting. Your job description emphasizes asynchronous execution and self-directed sprint planning, and that's rare. I'm looking for an organization that deliberately built remote infrastructure instead of treating remote work as an afterthought."
Layoff or Company Restructuring
"My previous employer restructured operations in the fourth quarter, and my entire product division was phased out alongside twenty other roles. I refused to grab the first opening I saw. Instead I targeted teams working on logistics software, because your recent release on supply chain transparency matches the inventory tracking projects I spent three years refining. I want to bring my background in supply chain architecture to an engineering team with stable footing and strong market momentum."
Experienced Manager or Team Lead
"Over the last four years I grew our internal support team from four representatives to twelve while keeping customer satisfaction at 94 percent. Then I hit a ceiling. Our leadership layer is small, and there's no near-term path to broader operational oversight. Your job post calls for an operations lead to build regional support teams from the ground up, and an aggressive scaling phase is exactly where my hiring and workflow design experience pays off."
Push vs Pull: Good and Bad Responses Compared
| Interview Topic | Push Response (Avoid) | Pull Response (Recommended) |
|---|---|---|
| Reason for Leaving | "My manager micromanages every task and our culture has turned toxic." | "I am ready for a role with greater project ownership, which is unavailable in my current group." |
| Salary Motivation | "I need a higher salary because the cost of living went up." | "This role expands my scope to enterprise clients, which matches my target compensation and responsibility level." |
| Company Interest | "I saw your job ad on a search app and liked the benefits." | "Your push into automated customer analytics matches my background building retention dashboards." |
| Remote Flexibility | "I refuse to commute forty minutes each way anymore." | "I have delivered my best project work in structured remote teams, and your async workflow fits how I produce." |
Rehearsing Your Response Before the Interview
Bullet points on a notepad get you halfway there. Delivery takes rehearsal, and there's no shortcut around it.
To be honest, reading notes off a secondary monitor during a video call looks unnatural. Your eyes drift toward the corner of the screen instead of the camera lens, and interviewers notice.
Set a timer and run the pitch out loud. Sixty seconds is the target. If you want objective feedback on your pacing, vocabulary, and filler words, try mock sessions with LinkedIn interview prep tools. Keep practicing until the three points roll off your tongue without checking a script. When the hiring manager opens the conversation with this question, a crisp delivery sets the tone for everything that follows.
Frequently Asked Questions
Is it bad to mention salary when answering why you want the job?
Leave compensation out of your first answer. Hiring managers know money matters, but leading with salary makes your interest look transactional. Talk about the responsibilities, the team challenges, and where the company is headed. Handle the numbers when the recruiter brings up pay bands later in the process.
How long should my answer be?
Aim for 45 to 90 seconds, which works out to roughly four to six spoken sentences. Two minutes is too much. By that point the interviewer has lost your main point.
What if I am unemployed and just need a job?
Never tell an employer you just need a paycheck. You can need work badly and still find one honest detail about their software, business model, or team mission, and one honest detail is all you need to frame your answer around why their specific opening makes sense for your background. Pick that detail tonight, build your three parts around it, and say it out loud a few times before the call.
