OfferDrill.

Interview questions

The hard ones

What motivates you, and how to answer it without sounding like everyone else.

This question sounds soft, but it's a real one, and most people waste it on words like "challenge" and "growth" that could describe anybody. Here's how to find the thing that actually gets you out of bed, say it in about sixty seconds, and back it up with one story that proves it.

Why they ask it

They're trying to figure out whether the work they have will keep you interested. Every job has a shape. Some are mostly solving puzzles alone. Some are mostly untangling problems between people. Some are repetitive and stable, some are chaotic and new every week. The interviewer knows which one this job is, and they're listening to see if what you describe matches it.

There's a second thing underneath. They want to know if you've ever thought about this. People who know what energizes them tend to stick around longer and need less managing, because they steer themselves toward the parts of the job that keep them going. People who've never thought about it tend to burn out quietly and leave in eight months.

And for a lot of interviewers, it's simply a warmth check. They're going to sit near you for a long time. They want to hear you talk about something you actually like.

What not to say

"I'm motivated by challenges and learning new things."

Every single candidate says a version of this. It tells the interviewer nothing about you, and it burns your best chance in the interview to be memorable. If you want to talk about learning, name what you learned last and why you chased it.

"Money. I've got bills."

It's honest, and it's true for almost everyone, but it answers a question they didn't ask. They know you need to be paid. Save the money conversation for the offer stage, where it does you some good.

A long speech about your values with no example attached.

Anyone can claim to be driven by impact or integrity. Without a story, it reads as something you rehearsed. One concrete thing you did beats three sentences about who you are.

Something that quietly describes a different job than this one.

If you say you love deep solo focus and the role is running five client accounts at once, you've just told them you'll be unhappy. Don't lie about it — but do pick, from the things that are genuinely true about you, the one that fits this work.

How to build a strong answer

  1. Find the real answer first, before you worry about how it sounds.
    Think of two or three times at work when you lost track of the hour. Not your proudest moments — the moments you didn't notice time passing. What were you doing? Fixing something broken? Explaining something to someone until it clicked? Getting a messy thing organized? Finishing something and seeing it used? That's your raw material. Almost nobody's honest answer is "challenges."
  2. Say it in one plain sentence.
    Turn it into a short, specific opening line. "I like taking something that's a mess and making it run." "I get a lot out of being the person who explains the hard thing." "What I like is finishing — shipping something and watching people use it." Plain words. No mission-statement language. Lead with this sentence so they know where you're going.
  3. Prove it with one story, thirty seconds max.
    Name a real situation, what you did, and what happened. "At [employer] we had [the actual problem]. I spent about [the real amount of time] rebuilding how we tracked it, and after that [the actual result]. I worked late on that without anyone asking, which is how I know I like that kind of work." The detail is what makes it believable. Skip the buildup and start in the middle.
  4. Connect it to this job in one sentence, then stop.
    "From the job description, it sounds like [specific part of the role] is a lot of that, which is why I applied." One line. Then be quiet. The whole answer should run sixty to ninety seconds. If you're still talking at two minutes, you've turned a good answer into a nervous one.

Examples to adapt

These are shapes, not scripts. Say them in your own words with your own facts — anything in brackets is a detail only you know, and it has to be the true one.

Mid-career, recently laid off, applying for a role close to what you did before.

Honestly, what keeps me going is fixing things that are broken in a boring way. At [employer], our [specific process] was held together with spreadsheets and three people's memory, and every month-end was a scramble. Nobody asked me to fix it. I spent about [the real amount of time] rebuilding it, and after that month-end went from [the actual before] to [the actual after]. I remember being genuinely pleased about it, which tells you something about me. I like the part where the chaos stops. Looking at this role, it sounds like [the specific messy area they mentioned] is in a similar place, and that's the part of the job I'd be most glad to take on.

It's specific, it's plainly true, and it tells the employer exactly what kind of work to hand you. The small self-aware line — "which tells you something about me" — sounds like a person, not a script.

Early career, one internship, not much to point to yet.

The thing I've noticed about myself is that I like being the person who makes the confusing thing make sense. During my internship at [employer], I was given [the actual task], and the documentation for it was scattered across [wherever it actually was]. I ended up writing a short guide for it, mostly because I needed one myself. My manager passed it to the next intern. That was the part of the summer I enjoyed most — more than the analysis itself, honestly. So what motivates me is that moment where something clicks for someone because of something I did. I know this role has a lot of [the specific part of the job], and that seems like the same thing at a bigger scale.

It doesn't pretend to have twenty years of evidence. One small, real thing, honestly told, does the job. Admitting she liked the guide more than the analysis makes it credible.

Changing fields, or coming back after time away.

What motivates me hasn't really changed across the different things I've done. It's working with people who are good at what they do and getting something finished together. When I was in [previous field], the days I liked were the ones where [the specific kind of collaborative work]. I got that same thing during [the actual recent experience — a course, a volunteer role, a contract], where [what happened]. I'm aware I'm coming into this field later than some people, so I'll be learning from people younger than me, and I don't mind that at all. Being around people who know more than me is genuinely one of my favorite parts of a job.

It names the change without apologizing for it and turns the thing he might be insecure about into evidence of what drives him. No invented experience — just the real recent thing, whatever it is.

What comes next

Answer this one well and the interviewer usually goes here:

  • What demotivates you? Or: what kind of work drains you?
  • Tell me about a time you lost motivation on a project. What did you do?
  • What did you like least about your last job?
  • How do you stay motivated on repetitive or routine work?
  • What would make you leave a job?
  • Where do you want to be in a few years?

Say it out loud before it counts.

Reading a good answer and giving one are different skills, and the gap shows up in the room. Offer asks you this question out loud, on a clock, and tells you what landed. The first one is free.

Practice this out loud

You already know the answer to this one — you just haven't said it out loud yet, so say it a few times in the car and let the real version come out.