Hiring managers ask "Why do you like this job?" because they need a signal you want the work itself. Your resume already listed skills. This question tests motivation, fit, and whether you'd still care after the offer.
You'll hear close cousins too. "What do you enjoy most about your job?" "Why this role?" "Why do you want this job?" Same intent. Different wrapper.
You found the posting on a job board and got through the ATS screen. Now a person wants to know if you'd pick these duties again on a hard Tuesday.
Can you point to a task you'd miss if it vanished?
That's the answer they can trust. Not "great culture." Not "growth opportunities." A specific kind of work, tied to this team, said in under a minute.
What they're actually listening for
They want to know you understand the duties. They want a reason this work fits you. They want a hint you'd stay.
Penn Career Services treats "Why are you interested in this role?" as the same test: grasp the responsibilities, show you align with the company, and show you want the challenge with proof you can handle it.
Closed answers die fast. "Yes, I like it" gives them nothing.
Turns out past enjoyment is the cleanest evidence. MIT CAPD treats behavioral interviews as a way to use what you already did as a predictor of what you'll do next. If you liked debugging production issues, say that. Then show a time you did it well.
They're also watching retention risk. Enthusiasm about the duties beats enthusiasm about the logo.
Build it in four parts
Keep it to a few sentences. You're not giving a keynote.
- Name the work you like, using language from the posting.
- Give one short STAR story that proves you liked it enough to do it well.
- Tie that work to this company or team with something you actually found, a product, a customer type, or a workflow.
- Close on what you'd do here, not on pay, remote days, or "I just need a job."
Write it, then cut it. If a sentence could sit on any listing on Indeed or LinkedIn, delete it.
Most of the talking time should sit on what you personally did. University of Cincinnati career staff tell candidates to use "I," not "we," and to walk through the steps they took. That's the Action in STAR. It's the part people remember.
Don't burn the minute on your origin story. A little personal context is fine. The role still has to sit in the center.
Sample answers to rewrite in your own words
Don't memorize these. Swap in your tools, your numbers, and the details you pulled from the posting.
I keep seeing people try to sound passionate and then they list values that came off the careers page, values, mission, innovation, all of it true for fifty other employers, and the interviewer has heard that tape before. Use a story instead.
Marketing version: "I like this job because I get to turn messy audience data into campaigns people actually open. Last year our list had gone flat. I owned the spring target, rebuilt the segments, and ran two interactive email series. Engagement jumped about 30 percent in a month, and I still get a kick out of that puzzle. Your posting's focus on lifecycle programs is the same work I already protect on my calendar."
See the shape. Skill, story, their listing. No speech about a passion for marketing.
QA or software version: "I like hunting the bugs other people skip. Crash reports spiked after a release. I had to stabilize the build before the next ship date. I wrote a repro script, isolated a race in the session handler, and I got a build out that stopped the crashes. Your notes about edge-case coverage are why I applied here instead of a generic tester listing."
People-manager version: "I like this job when the work is leading a team through an ugly constraint, not just writing the plan. I didn't set out to manage. A weekend prototype turned into a years-long product and I ended up owning the people side. I want that mix here, especially the cross-functional build cycle in your listing."
Sales or support version: "I like work where I can see a customer get unstuck. I built a simple follow-up cadence after onboarding, and more accounts stayed through the first 90 days. Your role is heavy on that post-sale stretch, which is the part I don't get bored with."
If they mean your current job, talk about the tasks you still volunteer for. Then connect those tasks to the new posting so it doesn't sound like you'd rather stay.
A career-change answer has to work harder. Name the transferable task, not the old title. "I like diagnosing process failures" travels. "I like being a teacher" only travels if you map it to training, enablement, or customer education in this role.
Use STAR without saying the word
You don't need to announce the framework. You do need the bones.
MIT's CAPD worksheet asks you to prep 3 to 5 stories. Situation gets a little context. Task is the goal you owned. Action is most of the telling. Result is the outcome, with a number if you honestly have one.
Situation: enough for a stranger. Skip the org chart. Task: what you were on the hook for. Action: the steps you took. Result: what changed.
Thing is, people treat "why do you like this job" like a vibe check and ramble. Anchor it with one story anyway. That's how you prove the liking is real.
A compact version sounds like this. "As the email lead, I had a 50 percent list-growth target. I added interactive modules and hit a 30 percent engagement lift in a month. That loop, brief, test, ship, is what I like, and it's all over your description."
If you don't have a clean percentage, use a before-and-after you can defend. Time saved. Tickets closed. A launch that shipped. Fake precision is worse than a plain result.
Prep those 3 to 5 outlines on paper. Interview day is a bad time to invent a story.
Do the research on the listing you already have
Open the listing you applied to. Highlight two or three duties. Those phrases should show up, in your words, when you talk.
Then screen the employer the way you already screen jobs. Read the About page. Skim recent news. Check the LinkedIn company page and a few employee posts for how they describe the work. Glassdoor comments can hint at pace. Treat reviews as anecdotes, not proof.
Penn Career Services is blunt: if you haven't held the job before, you still need to fully grasp the responsibilities. That's research, not vibes.
You can spend a weird amount of time polishing one sentence about culture and still walk in without a single example of work you actually enjoyed, which is the thing they can test, the thing they remember, and, yeah, the thing that separates a real answer from something you could paste on any company card on the board.
Write three lines before you practice:
- one duty you already like doing
- one team or product detail that is specific to them
- one way you'd contribute in the first months
If you can't fill those lines, you're not ready. Resume tools already pushed keywords through filters. This question is the human filter. Generic brand praise fails it.
Skip any claim you couldn't defend if they asked where you saw it.
What usually falls flat
| What you say | Why it hurts | Try this instead |
|---|---|---|
| Pay, remote days, or "any job" | Sounds transactional | Lead with the work |
| "Great culture" with no example | Fits every application | Name a workflow from the posting |
| Bashing your current employer | They picture you repeating it | Talk about work you want more of |
| "I'm a hard worker" | Vague, sometimes arrogant | One story with a result |
| Company praise, no duties | Feels like logo-chasing | Tie a company fact to a task you'd own |
Don't compare yourself to "other candidates." You don't know them. You also don't need to pretend you'd love every task. Pick the parts that are true.
To be honest, a lot of people over-research mission statements and under-research the day-to-day. Hiring managers live in the day-to-day.
How long this should take
Speak for a handful of sentences, then stop. If they want more, they'll ask.
Practice until it sounds like you
Read the answer out loud. Time it. If it runs long, you packed two answers into one.
Use this checklist the night before:
- [ ] I named a real task, not a slogan
- [ ] I used one story with a result I can defend
- [ ] I tied it to this posting or this team
- [ ] I cut anything true of every job on the board
- [ ] I can say it without looking at notes
Rehearse enough that you aren't hunting for words. Stop before it sounds like a press release. UC's STAR guidance is simple: the more you rehearse the stories, the more confident you sound. Confidence isn't volume. It's being able to stop at the result and wait.
If you use an interview-prep feature inside a job app, treat it as a timer and a filler-word check. Don't let it write the script. The words still have to be yours.
Ask one question back if it fits. "How does the team decide what to ship next?" shows you like the work. "What's the culture like?" is weaker.
Why this job over the others
Don't rank every employer you applied to. Contrast the work.
"I applied here because the role is built around X, which is the part of my last job I protected on my calendar. Other listings were broader generalist seats. This one matches the efficiency project I already ran, and your product roadmap is where I want to do that again."
Only cite a number that's yours. Don't wear someone else's case study.
People who like the work talk about the work. That's the signal retention-minded managers are after.
FAQ
Do I have to use STAR for "why do you like this job"? No. It's a motivation question. A short STAR story still helps because it proves the liking with behavior, which is what behavioral interviews are built to measure.
What if I don't like my current job? Talk about the tasks you do like, or the work you're moving toward. Don't dump on your boss.
Should I mention the job board or the ATS? No. They don't care how you found the listing unless they ask. Use the posting as source material, not as a plot point.
What if this would be my first role in the field? Lean on adjacent work, class projects, internships, or volunteer builds. Grasp the posting's duties first, then map one thing you've already done that looks like those duties.
Open the listing tonight. Highlight two duties. Write five sentences that follow the four-part shape, then read them out loud once.