You're looking for work that uses a skill you already have, lets you improve at something this employer can actually teach, and matches how the team gets things done. Put it in their language, not yours.
They want to know you'll do the work, stay long enough for the hire to pay off, and not treat the role as a parking spot. This is the filter that matters.
Can you name what you want without centering only yourself?
Keep the spoken version to about 45 to 90 seconds. Three to five sentences is plenty. Write it, then cut every line that doesn't name the work or this company.
Why they ask
Interviewers use this question to see if your motives match the role, the culture, and how long you are likely to stay. A fuzzy answer sounds like spam.
Four moves that keep you on track
Thing is, you don't need a clever speech. Spend fifteen to twenty minutes on the company site, the job post, and one recent news item so your answer names something real. Then write the four lines below.
- Pick two professional priorities, not a pile of values. Skill-building, ownership, patient outcomes, quota support, or mentoring others are fair. Leave salary, commute, and title-chasing for later unless they ask.
- Tie each priority to a duty in the posting or a project the company already talks about. If you can't point to the page, you aren't ready.
- Add one short proof. A STAR-shaped story works: situation, task, what you did, what changed. Keep the result in plain numbers or a clear before-and-after.
- Close on this seat. One sentence on why this team, product, or mission is the match.
Read it out loud once. If you run past ninety seconds, you packed in too much.
Sample answers you can rewrite tonight
Don't memorize these word for word. Swap the skill, their goal, and one fact you found.
A solid general version sounds like this: "I'm looking for a role where I can use process design to cut cycle time and keep growing in cross-functional work. Last year our refund queue sat at two weeks. I mapped the handoffs, automated the obvious steps, and most cases landed in two days. Your posting calls out the same cleanup work, and that's the work I want next."
People try to pack in every value they have, growth and impact and flexibility and learning and purpose all in one breath, and then they never mention the actual job, which is the only part the interviewer is waiting to hear, and you can watch them fade when the answer stays abstract.
Here's a tighter career-change version. "I'm moving from account management into customer success because I already handle renewals, messy tickets, and the handoff between sales and support. I want a seat where those skills reduce churn, not just close a quarter. Your onboarding program and the way this team owns the full customer path are why I applied."
For someone already in the field: "I want a role with real ownership of a roadmap slice, not another year of tickets with no say in priority. I led a pricing experiment on a small product line, we shipped it in a quarter, and win rate on that segment went up. Your PM posting sits on both the consumer and enterprise lines, and that mix is what I'm hunting."
Notice the pattern. Two wants. One proof. One reason it's this job.
What not to say
Don't lead with money, remote days, or how much you disliked your last boss. Those topics can come after they want you.
- Don't trash a former employer or team.
- Don't promise you'll be CEO in two years if this job is individual-contributor work.
- Don't stop at "growth" or "a good culture" with no tie to their work.
- Don't make pay the first thing you mention. If they press, give a researched range and stay open on the total package.
A bad line is "higher pay and fewer hours." A better line is the STAR story plus why their team is the place to do that work. If the only true reason you're leaving is burnout, still talk about the work you want, not the wounds.
Entry-level, mid-career, and leadership versions
| Stage | Lean on | Sample line |
|---|---|---|
| Early career (about 0-3 years) | Learning inside the work, mentorship that is real, a chance to ship something small | "I want hands-on time in [craft] and a team that reviews work, not a sink-or-swim desk." |
| Mid-career (about 4-10 years) | Ownership, a metric you can move, room to lead a slice without a fake title | "I want to own [process or product] end to end and grow people around it." |
| Senior / leadership | Strategy, developing others, decisions that show up in revenue or risk | "I want a seat where team goals and company goals are the same conversation." |
If you're early in your career, talk about learning. Talk about learning in the work itself, not a vague hope that someone will mentor you someday if the stars align.
Executives should flip the last sentence into a question they actually want answered. "How does this role feed your next two planning cycles?" is fair. Don't use it to dodge what you want.
Tech, healthcare, sales, and remote interviews
Turns out the same skeleton works. Only the nouns change.
In tech, name the stack or the problem, not "innovation" as a personality trait. "I want to keep building in [language or domain] on problems with real users, and grow toward [AI, reliability, or platform work] if that's what this team needs." Point at a product, a repo culture, or a public engineering post. Hybrid or remote tech screens often probe self-direction, so add one example of updates you sent without being asked.
Healthcare answers land when they stay with patients and the team, not a TED-talk about purpose. "I came into this field to improve outcomes for [population you actually served]. I want a unit that uses current protocols and still has time to teach. Your [clinic, floor, or program] is the setting I want to work in." Keep PHI out of the story. Use process and teamwork, not case gossip.
Sales wants quota, support, and a motion you understand. "I do well when the target is clear and the team shares pipeline hygiene. I want a role where I can run [inbound, outbound, or expansion] with a real enablement loop. Your [segment or product] matches the deals I've already closed." Don't brag about crushing a former employer. Show the motion.
Remote and gig-style work still need a team answer. Autonomy is fine. Isolation as a brand is not. "I want a remote seat with clear owners and written updates, because that's how I stay fast. I also want enough live time that I'm not a ticket machine." If the role is a short contract, say you want a scoped project, a clean handoff, and a shot at more work if the fit is real. Hiring managers still worry about "team fit" on distributed crews. Give them a self-starter example, then ask how the team actually meets.
Where job boards, resumes, and ATS fit
To be honest, the interview line is easier if your search was already honest. You already used those two priorities as filters on job boards: function, seniority, remote or on-site, industry, even keywords from the posting. That way you aren't inventing a speech for a job you only skimmed.
Your resume should use the same language. If you say you want cross-functional work, the bullets should show it. Applicant tracking systems parse skills, titles, and phrases from the posting. They don't grade charm. Mirror the real duties, not a cloud of soft words. A resume tool can flag missing keywords. It can't invent a motive you don't have.
When you apply through a board or a company portal, save the posting. Interviewers quote it back. Your "what I'm looking for" answer should sound like a person who read that file, not a person who read a blog.
Generic lines versus a tailored one
| Aspect | Generic | Tailored |
|---|---|---|
| Memory | Forgettable in a long slate | Names their work |
| Fit signal | Could be any company | Shows you did the homework |
| Risk | Sounds uninterested or desperate | Sounds like a deliberate move |
| Example | "I'm looking for growth opportunities." | "I want to grow in people leadership on your B2B line, where the calls hit revenue." |
Customization is the whole game. Professional motives beat personal-life motives in this question. Save daycare and commute for the offer stage unless they raise them first.
A practice run that doesn't sound scripted
- Highlight two duties and one company fact on the posting.
- List three skills you can prove. Circle the two that match those duties.
- Draft one STAR story of 4-6 sentences. Cut it to 3.
- Write the 60-second answer. Time it on your phone.
- Record it once. Listen for filler and for any swipe at a past boss.
- Swap one noun so it only works at this company.
- Prep one follow-up: how the team sets goals, how juniors get coached, or how remote check-ins work.
- If pay comes up, have a market range ready and tie it to the scope, not your bills.
Do this the night before. Fresh research beats a speech you reused for six applications.
FAQ
Why do they ask what I'm looking for in a job? They want motivation, culture fit, and a hint you won't leave in a hurry. Alignment is the point. Charm is not.
How is this different from "What motivates you?" They overlap. For motivations, stay with professional drivers: solving a messy process, hitting a number, teaching a junior. Use the same STAR proof. Don't wander into hobbies.
What should entry-level candidates say they want? A foundation in the actual craft, feedback, and a chance to ship something small. "I want to learn" is weak until you name the skill and the work.
How do I handle a salary follow-up? Give a researched range and say you're flexible on the full package. Don't open with money when they asked what you're looking for in the job.
What if I really want remote work? You can say flexibility matters if the posting is remote or hybrid. Pair it with how you communicate. "I want a remote role with clear owners and written updates" is stronger than "I don't want an office."
Open the posting you're chasing. Highlight two duties. Write one 60-second answer that uses those duties, one proof from your last job, and one fact about this team. Record it once, fix the ramble, and stop there.