How to Answer Why Do You Want This Job Without Sounding Fake

9 min read

You practiced in the car. You said you're passionate about innovation. The recruiter smiled and asked about something else. You're not dishonest. You're answering a fit check with a commercial, while your resume in Greenhouse already lists the proof you never said out loud.

Before you rewrite your whole story, check your resume for free against the posting and read bullet one under your current title. That line is the spine of a believable motivation answer.

Job searching is exhausting, and this question feels like a personality test. It's not. It's a short check that you know what this req actually is and that you'll still want the work after week three.

Below you'll see what interviewers grade, three frames that stay specific, lines that sound fake, a copy-paste script, and how to line up your file before the screen.

What they hear when they ask why do you want this job

The question sounds soft. The grading is not. Panels want to know you read the req, you understand the messy part of the role, and you will not quit when the messy part shows up in month two.

Mission lines are cheap. Team problems are expensive.

When someone says they love our culture of innovation, the room hears nothing verifiable. When they name your posting line about billing exceptions in NetSuite and back it with month-end close moving from nine days to six, that lands on the scorecard.

US screens often run back-to-back in Workday scheduling blocks. You get one clean minute before attention drifts. Generic warmth feels safe to you and forgettable to them.

Another fail mode is resume whiplash. You gush about customer empathy while bullet one is all SQL and pipeline metrics. The mouth and the file need to tell the same story.

Career changers get stuck here too. You know you can do the work, but your answer still sounds like the old industry label. Translate the duty first, then add desire second.

For how this question differs from the proof-heavy hire-you variant, see how to answer why should we hire you with US examples after you nail motivation beats.

Three frames that stay specific (with paste scripts)

Pick one frame per interview. Stack all three and you sound like a brochure. Each frame follows hook, proof, forward line.

Frame 1: Team problem you want to help solve

Best when the posting names a backlog, a launch, or a broken handoff. Pull the noun from the job description, not from the About page.

Before: "I love your mission and I think I'd be a great culture add."
After: "You're hiring to reduce churn on the self-serve tier. I owned renewal saves for SMB accounts in Salesforce, lifted save rate from 62% to 71% in two quarters, and I'd start by mapping your current save playbook in week one."

Frame 2: Craft or stack you want to deepen

Use this when the role is a clear step up in tool depth. Tie enthusiasm to work you already shipped, not tools you watched on YouTube.

Before: "I'm excited to learn from your amazing engineers."
After: "This role sits on your payments service in Go and Kafka. I built the idempotency layer for card retries that dropped duplicate charges 18% in Q2, and I'd pair on the rate-limit work you listed for this squad."

Frame 3: Customer or user segment you already serve

Strong for support, success, clinical, or education roles where empathy only counts with context.

Before: "I care deeply about helping people."
After: "Your req focuses on Medicaid enrollment calls in Spanish. I handled 40+ eligibility screens a week in Epic, cut average handle time twelve minutes while holding accuracy, and I'd shadow your escalation queue in the first two weeks."

Copy-paste scaffold (edit brackets only):

{`Hook: You're hiring to [duty from posting line 3].
Proof: I already [verb] [tool] for [user segment], [metric] in [time window].
Forward: In month one I'd [task from posting] with [team name or product].`}
            

I've screened motivation answers right after the resume pass in Greenhouse, and the believable ones sound boring: duty, metric, next task. Flourish does not beat a line the hiring manager can trace to bullet one.

Need pacing so it does not sound memorized? Read behavioral interview answers that do not sound rehearsed once the facts are right.

Lines that make motivation answers sound fake

• Opening with I've always dreamed of working here without naming a duty.
• Quoting the careers page mission while your resume shows unrelated tools.
• Listing five adjectives before any noun from the posting.
• Bad-mouthing your current employer instead of naming forward work.
• Reciting the answer word-for-word without pauses or breath.

If you would not email that sentence to the hiring manager, do not say it in the room.

Before: You stack compliments about leadership and values.
After: You name one backlog item and one metric you already moved on similar work.

Before: You claim you're a fast learner with no example attached.
After: You cite a tool you adopted in ninety days with a shipped outcome.

Line up resume and mouth before the screen

Motivation answers fail when the proof lives only in your head. Put it on the page first so the spoken line has somewhere to point.

Run the free ATS check on the PDF you uploaded to Workday or Greenhouse. If bullet one does not mention the duty you'll praise in the interview, fix the bullet before you fix the script.

When the posting asks for a short note before the loop, draft hook and forward lines with the cover letter generator , then lift the proof sentence straight into your spoken answer.

Optional: score your job match on the same posting if you're unsure which duty belongs in beat one. Low match usually means you're forcing a frame that will sound hollow live.

Rehearse once, then stop polishing

You do not need a new personality to sound real. You need a team problem, proof from bullet one, and one honest forward line about month one.

Open the req. Pick a frame. Paste the scaffold. Say it twice out loud with the resume on screen. If the metric matches, you're ready enough for tonight's slot.

Perfect loops steal sleep. Panels rarely reward the fifth rewrite. They reward answers they can connect to work already on their roadmap.