The Interview Questions That Actually Tell You Who You're Hiring

By the time a candidate makes it to a final interview, the resume has already done its job. The skills line up, the experience checks out, the references will probably be fine. What's left to figure out is harder to put on paper: will this person actually work well with the people already on your team, on an ordinary Tuesday, six months from now, long after the interview polish has worn off?

Here's a way to think about it that a lot of hiring managers find useful, even if it sounds a little strange at first. Imagine you and this candidate are on a business trip together. You're at the airport, through security, waiting at the gate, and the flight gets delayed. Not by twenty minutes, by hours. There's nowhere to go and nothing to do but wait it out. Is this someone you could sit through that with?

It's a deliberately unglamorous test. Nobody's résumé optimizes for "tolerable during a flight delay," which is exactly why it's useful. If a bad situation wouldn't make this person noticeably worse to be around, there's a good chance the ordinary friction of a workweek, tight deadlines, a frustrated client, a project that goes sideways, won't either.

Getting past the rehearsed answer

The obstacle every interviewer runs into is time. You have one conversation, maybe two, to learn something that will affect the next several years of working together. Candidates know the standard questions are coming and have polished answers ready. The way around this isn't necessarily asking harder questions, it's asking ones that are harder to fully prepare for, because they require the candidate to think in the room rather than recite.

A working set worth having on hand:

"What led you to apply here?" and "Why does this field interest you?" — these establish whether the motivation is specific to your company or generic enough to apply to any listing they came across that week.

"Tell me about a stressful situation and how you handled it." Listen less for the crisis itself and more for what they actually did, and whether they take any ownership of the outcome or only describe things that happened to them.

"What's your usual role on a team?" and "How would your friends or family describe you?" Both are trying to get at the same thing from different angles: how this person actually operates around other people, not how they think they're supposed to answer.

"Why do you think you'd be a good fit here?" is a test of how well they've actually researched the company, not just the job title.

"How do you define success?" and "How do you handle conflict on a team?" tend to reveal whether someone's instincts align with how your team actually operates, or whether there's a mismatch waiting to surface later.

"Tell me something about yourself that's not on your resume" and "What's the biggest mistake you've made at work, and what did you take from it?" both work because they can't be answered from a script. The second one in particular is a decent filter: candidates who can name a real mistake and a real lesson tend to be more self-aware than the ones who deflect into a humblebrag about working too hard.

"What motivates you?" and "How do you take criticism?" round things out by getting at durability, what keeps someone engaged past the honeymoon period, and how they behave the first time something they built gets pushback.

One caution worth building in

It's tempting to lean entirely on gut feeling after a good conversation, but instinct alone is a notoriously unreliable hiring tool, it tends to reward people who interview well rather than people who'll actually do the job well. Whatever questions you settle on, it's worth scoring answers against the same rubric across every candidate for a given role, rather than letting each interview stand entirely on its own impression. It's a small amount of structure that catches a lot of bias before it becomes a bad hire.

You won't use every question on this list in a single conversation, and which ones matter will shift with the role and the team you're building around. But the underlying goal doesn't change: get past the answer the candidate prepared in the car on the way over, and find out who you're actually about to bring on board.