How to Answer "What Do You Look for in a Job?" (With Sample Answers)

This question has a trap built into it. Answer with what you actually want and you risk naming something this job doesn't have. Answer with a description of the job posting and you sound like you're reciting it back. The way through is to name things that are true, checkable against this role, and specific enough to be believable.

What the interviewer is actually testing

Will you be satisfied here? The most common cause of a hire leaving within a year is a mismatch that was visible at interview and nobody named.
What actually motivates you. Autonomy, craft, impact, learning, stability, pay — all legitimate, and each suits different teams.
Have you thought about it at all? Candidates who've articulated what they want tend to make better decisions and negotiate more honestly.
Whether you're interviewing them back. Most good interviewers respect this.

How to build your answer

Name two or three things, not seven. A long list reads as a wish list; two or three read as priorities. For each one, give a sentence of evidence from your own history — the reason you know it matters to you — and then tie it to something concrete about this role or company.

Order matters. Lead with something about the work itself. Compensation and flexibility are entirely reasonable to want, but leading with them shifts the conversation to terms before you've established value.

One thing worth saying plainly: if a genuine requirement of yours might be a dealbreaker — fully remote, a hard salary floor, no on-call — this is a reasonable moment to surface it. Discovering it at offer stage wastes everyone's time, including yours.

Sample answers

Sample 1 — software engineer

"Three things, in order.

First, ownership of something end to end. My best year was one where I owned a service from design through to being on-call for it, and my worst was one where I implemented other people's designs and never learned whether they worked.

Second, colleagues who'll tell me I'm wrong. I got noticeably better in an environment with rigorous code review and noticeably worse in one where everything was approved in four minutes.

Third — and I'll be direct — genuinely remote rather than remote-with-an-asterisk. I've worked in a hybrid setup where the important conversations happened in a room I wasn't in, and I don't want to repeat it.

The ownership piece is what made me apply here specifically, given the team structure you described."

Sample 2 — early career

"Mostly, somewhere I'll get better quickly.

Concretely that means feedback that's more frequent than a twice-yearly review, and working near people who are further along than me. In my current role I'm the only person doing what I do, and I've learned a lot slower than I would have with someone to look over my work.

The second thing is understanding why the work matters. I don't need to be in strategy meetings, but I want to know what happens to what I build.

Which is partly why a team of this size appealed — from the job description it sounds like people here see the whole path from problem to customer."

Sample 3 — senior candidate

"At this stage I'm fairly clear on it. Two things.

Problems that are hard for interesting reasons. I've spent the last two years on a system where the difficulty was mostly organisational — six teams and no clear owner. I'd rather the difficulty was technical.

And a company where I can see the connection between the engineering and whether the business works. I've been in a place where engineering was a cost centre that shipped what it was told, and I found it demotivating in a way I didn't expect.

I'll also say what I'm not optimising for: title. I've turned down a manager role once already because the work underneath it wasn't what I wanted."

Sample 4 — career changer

"Something I'm honest about, since I'm changing fields: I'm looking for a team that's hired a career changer before and knows what the first six months look like.

Beyond that, work where the feedback loop is short. Part of what pushed me out of my previous field was waiting eighteen months to learn whether a decision was right. I want to try things and find out.

And a manager who's specific. I'm going to be wrong about things a person with five years in this field wouldn't be, and vague encouragement won't help me fix that."

Common mistakes

Reciting the job posting. The interviewer wrote it. They'll notice.
Leading with perks. Salary, holiday and flexibility are legitimate; opening with them makes the rest of the interview about terms.
Naming something this job clearly lacks. Saying you want a large, structured organisation to a twelve-person startup answers the question and ends the conversation.
Pure abstraction. "A collaborative culture where I can grow" could be said by anyone about anything.
Framing it as escaping your last job. "Somewhere without micromanagement" tells them about your last manager. Say what you want instead.
Listing seven things. It suggests you'll be hard to satisfy.

Follow-up questions to expect

"Which of those matters most?" — Have a ranking ready. Refusing to prioritise is itself an answer.
"Has your current job got any of these?" — Be fair to your employer. Naming what's genuinely good there, and what's missing, is more credible than a blanket complaint.
"What would make you turn us down?" — Occasionally asked, and worth answering honestly. It's your chance to surface a dealbreaker before it costs you both a hiring process.