The 3 questions you should ALWAYS ask in an interview
Most candidates treat the 'any questions for us?' slot as a formality. It's actually the most informative 10 minutes of the whole process — if you ask the right things.
The last candidate I interviewed asked me what my favorite part of the company culture was. I gave her a polite, forgettable answer. She nodded thoughtfully, thanked me for my time, and I'm pretty sure she has no idea whether she'd actually like working here.
That was a wasted question. It was also the only one she asked.
The slot nobody prepares for
Candidates spend hours rehearsing behavioral answers and about ninety seconds thinking about what to ask at the end. This is backwards. The questions you ask do three things at once:
- They're your last chance to signal how you think.
- They're your only chance to find out whether this job is actually any good.
- They usually happen with the hiring manager alone, which is the highest-information environment of the entire process.
Waste it and you're deciding whether to accept an offer based on glassdoor reviews and vibes.
I've landed on three questions over the years that I now ask in every interview I take. Each one does a specific job. None of them is clever. That's the point — clever questions sound like interview questions. These sound like someone who actually wants to know.
Question 1: "What does the person who's great in this role do differently from the person who's just fine?"
This one is diagnostic. It forces the interviewer to think about the actual work instead of the job description.
You'll get one of three kinds of answer:
- Specific and vivid. "The person who's great ruthlessly kills low-ROI ad campaigns even when marketing pushes back. The fine person just runs whatever paid channels the CMO asked for." This is a good sign. The hiring manager has a clear mental model of excellence.
- Generic. "They're proactive, take ownership, collaborate well." This is a yellow flag. Either the manager doesn't have a strong picture of the role, or they do and they can't articulate it — both make the job riskier.
- A long pause followed by something halting. Red flag. You might be the first person they've hired for this role, or the role doesn't really exist yet, or their last hire didn't work out and they haven't figured out why.
All three answers are useful. You're learning either what success looks like, or that nobody here knows.
Sample follow-up: "Can you give me an example of something the great person did in the last month?" Watch what happens next. If they can, you've just gotten a real look at what the job is. If they can't, you've learned the manager doesn't pay close attention.
Question 2: "What's something that's genuinely broken about working here?"
This one is pure calibration. Every company has things that don't work. The question is whether your interviewer is honest about them.
The exact phrasing matters. "What's a challenge?" lets them give you a polished answer. "Broken" pushes them into specifics.
Expected responses, in decreasing order of how good the company is:
- A concrete, slightly uncomfortable answer. "Our engineering team is stretched too thin. If you join, you will not get the tools you want in the first six months." Trust this person. They are telling you something real.
- A self-aware, mildly political answer. "Cross-team communication. We've been trying to fix it for a year. It's still annoying." Fine. Every company has this. At least they see it.
- "Honestly, nothing comes to mind." You are interviewing with someone who is either a liar, a stranger to their own company, or extremely bad at this question. Downgrade accordingly.
I asked this once in a final interview. The CEO took a breath and said, "Our sales team doesn't trust our product team, and I haven't fixed it. If you join product, expect to spend your first month rebuilding those relationships." I took the job. He was right about the problem, and he was also the kind of person who'd told me the truth before I signed — which is a better signal than any culture deck.
Question 3: "Is there anything about my background that's giving you pause?"
This one is strategic. Ask it in every interview, without exception, and ask it before the meeting ends.
Two things happen.
First, you find out what the objection is while you're still in the room to address it. That's worth more than any prep you did. If the hiring manager says, "Honestly, I wasn't sure about your lack of direct team management experience," you have 30 seconds to point to the two examples you didn't get to talk about earlier.
Second, the interviewer now has to mentally articulate their objection. Unstated objections kill candidates after the interview, when the manager is sitting alone at their desk debating. Stated objections get resolved. You want them stated.
A sample exchange:
Candidate: "Before we wrap up — is there anything about my background that's giving you pause?"
Interviewer: (beat) "I guess my one hesitation is that you've only worked at startups. We're much more process-heavy than what you're used to."
Candidate: "That's fair. Can I push back briefly? At my last role we went from 20 to 160 people in two years — I led the rollout of our OKR system and wrote the performance review template we still use. I understand why startups feel looser to people outside them, but I've spent most of my career building exactly the kind of process I think you're describing. If it's helpful, I can send you the OKR deck after this."
Three minutes ago, this candidate was a "no" because of a startup-versus-enterprise stereotype. Now they're a "maybe" with a follow-up. That's the single highest-leverage thing you can do in an interview, and almost no one does it.
What to skip
- Anything you could've Googled. ("What's your growth strategy?")
- Compliments dressed as questions. ("I love your mission — can you tell me more about it?")
- Anything about salary or benefits in the first interview. Save it for the recruiter.
- "What's your favorite part of working here?" It produces nothing you can act on.
Takeaway
Three questions. Every interview. Diagnose the bar for excellence, calibrate the company's honesty, and surface any unspoken objection before you walk out. If you only remember one — remember the third. It's the difference between a strong "no" after the interview and a strong "yes" after a follow-up email.
The interview isn't just them evaluating you. It's also you deciding whether to spend the next several years of your life in this building. Ask like it.