OfferDrill.

Interview questions

The hard ones

What to ask when they say, "Do you have any questions for us?"

This gives you a short list of questions that work in almost any interview, and a simple way to pick the right two or three on the spot. It also tells you what to do when your mind goes blank, because that part is fixable with a piece of paper.

Why they ask it

Part of it is manners. They've been talking for forty minutes and they want to give you a turn. But they're also still evaluating you, and this is the one moment where you choose the topic.

What they're listening for is whether you've thought about the actual job. Not the company's stock price or its mission statement, the job. Someone who asks how work gets reviewed, or what the last person struggled with, sounds like a person picturing themselves doing the work. Someone who asks nothing sounds like a person who wants any job, not this one.

There's a quieter thing happening too. Good interviewers know you're interviewing them. If you ask nothing, they wonder whether you'll take the offer and leave in six months, or whether you just don't care enough to be curious. Two decent questions settle that.

What not to say

"No, I think you covered everything."

It reads as no interest, even when you mean it as politeness. If you truly have nothing new, at minimum say what you'd have asked: "You answered my big one about how the team is structured. The other thing I wanted to know is what the first ninety days look like." That still counts as a question.

"What's the company culture like?"

You'll get a canned answer about collaboration and work-life balance and you'll learn nothing. Ask something they can't answer on autopilot: "When someone disagrees with a decision here, what actually happens?"

Anything answered in the first line of the job posting.

"So what does this role do day to day?" tells them you skimmed. It costs you more than silence would. If you want the day-to-day, anchor it: "The posting mentions reporting and vendor management. Which one eats more of the week?"

Pay, vacation, and remote days in a first conversation with the hiring manager.

There's nothing shameful about these questions and you're entitled to answers. It's timing. Recruiters are the right person for comp and logistics, and they usually raise it themselves. With the hiring manager on a first round, leading with it shifts the subject before they've decided they want you.

A question that's really a speech about yourself.

"In my last role I rebuilt the whole intake process, so I'm curious whether you'd want me doing that here?" That's a brag with a question mark. They notice. Ask the clean version: "How happy are you with the intake process as it stands?"

How to build a strong answer

  1. Write five questions on paper and bring the paper.
    This is the whole fix for freezing. Nobody has ever been marked down for looking at a notepad. Pull it out and say, "I wrote a few down." It looks prepared, not unprepared. Five, because two or three will get answered during the conversation and you need spares.
  2. Pull from four buckets so your questions aren't all the same shape.
    One about the work: what does success look like at six months, what's the first problem you'd want solved. One about the person across from you: how long they've been there, what keeps them there, what surprised them. One about how the team runs: how decisions get made, how feedback happens, what the team is bad at right now. One about process: timeline and next steps. Four buckets, one question each, and you're never scrambling.
  3. Ask two or three. Then stop.
    This isn't your turn to interrogate them. Listen to the answer and react to it like a human — "That's useful, so the reporting piece is the bigger lift" — instead of reading straight to the next item. A short exchange with real back-and-forth beats six questions fired in a row.
  4. Close with the timeline, then say you want the job.
    End with "What are the next steps, and when do you expect to decide?" Get an actual date if they'll give one. Then add one honest sentence about your interest: "I'll say plainly that this sounds like the kind of work I want to be doing." Say it only if it's true. If you're unsure, thank them for their time instead.

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, talking to the hiring manager who would be your boss. Adapt the wording, don't memorize it.

I do, I wrote a few down. First one — if you look back a year from now and this hire went really well, what happened? What got fixed or built? Second, I'm curious about the team as it stands. What's the thing that frustrates them most right now, the thing you'd love a new person to take off your plate? And one about you, if that's all right: you've been here [however long they said]. What's kept you? Last thing, just practically — what are the next steps, and when are you hoping to decide?

The first question makes them describe the job in terms of results, which tells you what they'll actually judge you on. The second gets you a real problem to talk about, sometimes with time left to say how you'd approach it. Asking why they stay is a genuine question and people like answering it. The timeline question means you leave with a date instead of a guess.

Early career, one internship, on a first-round call with a recruiter or HR.

Yeah, a couple. What's the interview process from here — how many rounds, and who would I be meeting? Second, for someone coming in at this level, what does the ramp-up look like? Is there training, or is it more learning from whoever you're sitting with? And is there anything about my background that gives you pause, that I could clear up while I've got you?

A recruiter can actually answer all three. Process questions are exactly what they're for, and asking shows you're organized. The ramp-up question is honest about where you are without apologizing for it. The last one is optional and a little bold — it works with recruiters, who tend to tell you the truth, and it can surface a fixable misunderstanding about a gap or a missing skill before it quietly sinks you.

Interviewing at a company in the middle of change — a merger, layoffs, a new leader — or interviewing after you were laid off yourself.

I have two. The first is about the team's shape. I know [the change they mentioned, or what's public] has been going on. How has that landed on this team, and where do things sit now? I'd rather walk in knowing. The second is about the role itself — is this a new position, or am I replacing someone? And if you're replacing someone, what would you want to go differently this time? Then just the practical one: what's the timeline on a decision?

You can ask directly about instability. Grown-ups do. It signals you've been through a hard stretch and didn't get brittle about it, and their answer tells you a lot about whether this job is solid. The new-role-or-backfill question is one of the most useful in the whole list and almost nobody asks it.

What comes next

Answer this one well and the interviewer usually goes here:

  • "Anything else?" — have one spare ready so you're not caught flat.
  • "Based on what you've heard today, are you still interested in the role?"
  • "What are you looking for in your next position?"
  • "Where else are you in your search? Do you have other offers?"
  • "What are your salary expectations?" — expect this from the recruiter, often right after your questions.
  • "How soon could you start?"
  • "Is there anything we didn't cover that you want us to know?"

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

Freezing here isn't a character flaw, it's just a question you never prepared for — so prepare for it once, on paper, and it stops being the part you dread.