The questions to ask in an interview are the only part of the hour you control. Most candidates spend them on something they could have Googled.
The seven below get you what the careers page won’t: what the job actually is, what broke before you showed up, what happened to the person who held it last, and what the person across the table is quietly worried about.
Why “What’s the culture like?” never works
Start by cutting the question almost everybody asks. It’s about the company’s self-image, so you get its marketing copy back. Collaborative. Fast-paced. We work hard and play hard. Nobody has ever answered it with “we’re a mess, and the last two people in this seat quit.”
Culture matters, of course – Gallup puts managers at roughly 70% of the variance in team engagement, so the biggest driver of whether you’ll be happy is sitting right there answering your questions. But you can’t get at it head-on, any more than you’d check a restaurant’s kitchen by asking the host.
Here’s the test I give clients: a good question is one the interviewer can’t answer from the careers page. If they can recite it, you’ve learned nothing. If they have to stop and think, you’re getting real information.
The 7 questions to ask in an interview that get real answers
Question 1: “What does success look like in this role at 12 months?”
This sorts organized companies from disorganized ones in about four seconds.
A hiring manager who’s thought it through answers immediately and specifically: the system is migrated, the reporting cadence is running, two people are hired. One who hasn’t gives you adjectives – proactive, takes ownership, hits the ground running. Adjectives mean the job hasn’t been defined yet, and an undefined job gets graded against a standard nobody wrote down.
Question 2: “What’s the problem you need solved in the first 90 days?”
I use a medical analogy with clients: the patient vomiting blood is the symptom, not the diagnosis. The job description is the symptom, assembled from an old req and a few bullets from the last person who held the seat.
This question gets you the diagnosis. Companies don’t open headcount because a box on an org chart is empty; they open it because something is broken, late, or on fire. Therefore the real job is whatever they name here; the rest of the posting is decoration. It also changes the rest of the hour, which is why experience alone is a weak predictor of who succeeds in a new role – fit to the live problem beats a matching resume almost every time.
Question 3: “What happened to the person who had this job before me?”
The highest-signal question here, and the one candidates are most afraid to ask.
Ask it plainly, then listen to the shape of the answer, not the content. “She was promoted into the director role and still sits two desks away” tells you this job is a launchpad. “He decided to pursue other opportunities,” delivered with a small pause, tells you something else. If the answer stays vague, follow up once: “How long were they in the seat?” A string of short tenures in the same chair isn’t bad luck. It’s a pattern, and you’d be the next data point.
Question 4: “How does this team handle disagreement?”
Every team says it values healthy debate. Far fewer can describe the last time two people disagreed about something that mattered.
So make them describe it. A good answer sounds like a story with a resolution: two engineers split on the approach, we ran a two-week spike, the data settled it. A bad answer sounds like philosophy, or like relief that it doesn’t come up much – which means disagreement gets buried rather than resolved. This is the question that actually surfaces culture, because it asks for an event instead of a self-assessment. If you’re already weighing an offer, there’s more you can check before you accept.
Question 5: “Who makes the decisions that affect my work, and how do they get made?”
Titles lie about authority. I’ve watched clients accept director roles with no budget and no hiring authority, then spend a year wondering why they couldn’t move anything.
Ask specifically: who signs off on the roadmap, who controls headcount, who can kill your project. If the answer names three people you haven’t met, ask to meet them. Moreover, if the person interviewing you can’t explain how decisions get made, that’s the answer – they don’t get made cleanly.
Question 6: “What’s the hardest part of working here that you’d want me to know before I say yes?”
Use that phrasing close to verbatim. You’re giving the interviewer permission to be honest, framed as a favor to a future colleague rather than a trap.
Most people take the permission. You’ll hear about the reorg, the tooling debt, the quarter everyone worked weekends. None of that should scare you off, because every job has a hardest part. A flat denial should – “honestly, it’s great here” means either they won’t be straight with you or they haven’t been there long enough to know.
Question 7: “Six months from now, what would make you say hiring me was the right call?”
Close with this one. It’s a graceful handoff back to the interviewer, and it hands you their scorecard in their own words.
Whatever they say next is the standard you’ll be measured against, so write it down the moment you leave and reference it in your thank-you note. Few candidates do this, and it lands hard, because you’re showing them you listened and are already working their problem instead of your offer.
How to ask without sounding like an interrogator
Seven questions is a menu, not a script. Firing all of them in sequence turns a conversation into a deposition.
Pick three before you walk in. The hiring manager gets 1, 2, and 7. A peer gets 3, 4, and 6. A skip-level gets 5. Spreading your questions to ask in an interview across the loop also gives you a reason to talk to each person differently. Ask them in context, not only at the end, and write the answers down in the room. For logistics before the loop starts, the recruiter is the better source.
What good answers and bad answers sound like
After 20-plus years on both sides of the table and 250-plus mid-career tech professionals placed, the pattern holds: strong companies answer with specifics and dates, weak ones with adjectives and vision. Specifics mean somebody has done the thinking. Adjectives mean they’re hiring hope – the same lens worth applying to what hiring managers are actually looking for. Watch, too, for the interviewer who gets more engaged once you start asking. That’s the tell that you’ve moved from candidate being evaluated to colleague being recruited, which is where you want to stand before anyone talks about money.
Frequently asked questions
Is it rude to ask what happened to the last person in the role?
No. It’s standard due diligence and hiring managers expect it. Ask it neutrally, without implying you suspect something, and the answer tells you plenty either way.
Should I ask about salary in the first interview?
Only if they raise it first, or if you’re far enough along that a mismatch would waste everyone’s time. These seven serve you better early, and compensation lands harder once they want you.
Can I ask these in a screening call with a recruiter?
Some of them. Recruiters can usually answer 1, 3, and 5 accurately. Save the ones about team dynamics for people who do the work every day.
What to do next
If you want to find out which part of your search is actually leaking – strategy, story, materials, networking, or interviewing – take the RHINO quiz. Five minutes, no email required.
If the answers you get in the room aren’t enough, go get them outside it. Company Research: The People Who Left Tell the Truth covers how to reach former employees and what to ask them once you do.
And if you’d rather have someone sit with your actual interview loop and tell you which questions to ask which person, book a free strategy call.