The short version. Most engineers waste their interview questions on filler — "What's your favorite thing about working here?" — and walk away knowing nothing real. The questions below are designed to do the opposite. Each one is specific enough that a marketing answer doesn't fit, and the section after each batch tells you what a genuinely good answer sounds like versus what a red-flag dodge looks like.

Pick 8 to 12 of these for each company you're interviewing with. Match them to the round: managers get expectations questions, peers get day-to-day questions, leadership gets strategy questions. Don't ask all of them in one round — that turns the conversation into an interrogation. The goal is signal, not coverage.

Questions about the team and the role

The most-skipped category of reverse questions. Skipping them is how engineers end up six weeks in wondering why the role looks nothing like the JD.

  1. Why is this role open right now? Look for a specific story (growth, internal move, the previous person was promoted). Watch for vague "we're always hiring" answers that hide turnover.
  2. Who left the team in the last 12 months, and what happened to them? Names and outcomes. "X went to a startup, Y was promoted to staff" is healthy. Total non-answers, or repeated short tenures, are a yellow flag.
  3. How long has the average current team member been here? If everyone joined in the last 18 months, ask why. Could be growth, could be churn.
  4. What does the team's roadmap for the next two quarters look like? A real answer is specific projects, real users, and real constraints. "We're figuring that out" at a stable company is a yellow flag.
  5. Who is the most recent hire on this team, and what's been their experience so far? If you can talk to them in a later round, ask for it. New hires are unfiltered information.
  6. What does success in the first 90 days look like for someone in this role? Should be concrete and ramped: weeks 1-4 onboarding, weeks 5-8 first shippable thing, weeks 9-12 owning something.
  7. Walk me through a real project that this team shipped in the last six months — what went well and what didn't? Specifics. If they can't name one, the team isn't shipping. If they can name one but everything "went great," they're sanitizing.
  8. What's the one thing about working here that would make you leave if it didn't change? A great question because a thoughtful answer signals self-awareness. A non-answer signals exactly what you'd expect.

Questions about the manager

Engineers leave managers, not companies. These questions are for your hiring-manager round specifically — they let you evaluate the person you'll spend the most 1:1 time with.

  1. How do you run 1:1s? Look for: weekly cadence, candidate-owned agenda, mix of work and growth. Watch for: "we mostly chat as needed" (which means you'll never get one).
  2. How do you handle disagreement on the team — say, an engineer pushes back on a deadline you set? A good manager has a specific story. A bad one will tell you "we all just align."
  3. What's an example of someone on your team who got promoted recently — what did it take? Specific name, specific work, specific timeline. If nobody on the team has been promoted recently, dig into why.
  4. How do you advocate for your team's headcount and budget? Strong managers know exactly how their team gets resourced. Weak ones say "I trust the process."
  5. When was the last time you gave someone on the team critical feedback, and how did you deliver it? Tests whether they actually give feedback, or just nice-praise people into stagnation.
  6. What's your management style — and what kind of engineer thrives under you vs. doesn't? Honest managers can name both. Defensive ones only describe the thrivers.
  7. How do you measure whether you're being a good manager? Look for: regular skip-level feedback, low regretted attrition, growth on the team. Watch for: vague "people seem happy."

Questions about on-call, workload, and work-life balance

The biggest source of post-offer regret. Don't ask "do you have good work-life balance" — every company says yes. Ask the specific operational questions instead.

  1. How does the on-call rotation work — how many engineers, how long per shift, how is comp/time-off handled? Concrete operational answer. "Once every six weeks for a week, with comp time after a hard week" is healthy. "Always-on, but it's chill" is not.
  2. How many pages did this team get last quarter, and what were the most common root causes? If they don't track this, that's the answer. If they do, the number tells you everything.
  3. Walk me through the last weekend page someone on this team got — what happened, who responded, what changed afterward? Real story, not hypothetical. Tests the team's incident culture too.
  4. What does a typical week look like — meetings, deep work, on-call, code review? If they can't break it down, deep work doesn't exist. If they can, you have your answer.
  5. Is it normal to send Slack or email after working hours? Is it normal to expect responses? Asking about both sending and responding gets a more honest answer than asking about either alone.
  6. What's the team's policy on PTO, and how often do people actually take it? A two-week minimum that nobody uses is worse than an unlimited policy people actually use. The "actually take" framing is the whole question.
  7. If a release is at risk and we're behind, does the team work the weekend, slip the date, or cut scope? A high-functioning team has a default answer — usually cut scope or slip date. "Whatever it takes" is a flag.

The pattern beats the pitch

Cross-check answers between rounds. If the manager says "we never expect weekend work" and a peer says "well, last quarter we worked two weekends to make the launch," trust the peer. Patterns across interviewers tell you the truth; any single interviewer can be optimistic, defensive, or new.

Questions about engineering culture and craft

These get at the day-to-day reality of doing the work — code review, tech debt, decision-making, and how the team treats the codebase as a shared asset.

  1. What's the code review culture — average turnaround, expectations, who reviews what? Healthy teams have a defined cadence (under a day for normal PRs, faster for blockers). "Whenever someone gets to it" is a sign.
  2. How does the team make technical decisions — RFCs, design docs, ad-hoc Slack, ADRs? Process exists for a reason. A real answer shows a deliberate culture; "we just chat and figure it out" works at five people, not fifty.
  3. How much tech debt has the team taken on in the last year, and what's the plan for paying it down? No team is debt-free. The interesting question is whether the team is honest about it and resources cleanup.
  4. What's an engineering tradition or ritual on this team that you actually enjoy? Specific traditions (Friday demos, post-mortem reviews, eng book club) signal a real culture. Generic answers signal a generic team.
  5. How does the team handle production incidents — who runs the post-mortem, is it blameless, are action items actually completed? Tests whether incident culture is performative or operational.
  6. What testing and CI practices do you have? How long is the average CI run? "30 seconds and we trust it" beats "two hours and we mostly trust it" — and tells you a lot about engineering investment.
  7. What's the last thing the team did to improve developer experience for itself? Teams that invest in their own tooling are teams that take their own work seriously.
  8. What's the team's stance on AI coding tools — Copilot, Cursor, Claude Code, agents? How are people using them day-to-day? In 2026 this answer tells you more about the team's pragmatism and modernity than almost anything else.

Questions about growth, promotion, and trajectory

The questions that will determine whether this role takes you somewhere in two years, or just somewhere different.

  1. What's the leveling structure here, and what does it take to move up one level? Companies that have done the work have written guides. Companies that haven't will give a hand-wavy answer.
  2. Who was the last engineer at my level to get promoted, and how long had they been at this level when it happened? Real numbers. "Two years, three years" is a healthy honest range. "We don't really track that" usually means it doesn't happen.
  3. What career paths exist beyond senior — IC track, management, both? How is the IC track resourced? Strong IC tracks are rare. If they say "yes we have both" but staff+ engineers all end up as managers, you have your answer.
  4. How does the team think about cross-team and cross-functional moves — is it encouraged or discouraged? Mobility is a strong retention signal. Rigid orgs penalize internal movers.
  5. What's the calibration process like — who decides whether someone gets promoted, and how is it scored? Tests whether promotion is criteria-based or political. Good answers describe specific calibration committees and rubrics.
  6. What's the typical comp adjustment at promotion — does total comp meaningfully change, or just title? Promotion without comp is just a title change. Ask directly.
  7. What's the most surprising career outcome you've seen from someone on this team? Optimistic answers ("X started as a new grad and is now a staff engineer leading the platform org") signal a place people grow.

Questions about compensation, equity, and the offer

Save these for the recruiter or hiring-manager rounds where it's the right context. Asking real comp questions is the strongest signal you're a serious candidate.

  1. What's the salary band for this role at this level? If they refuse to share, they intend to underpay you. Politely ask why they don't share bands.
  2. What's the typical equity grant for this level — number of shares or RSUs, vesting schedule, refresher policy? For startups: ask the strike price and most recent 409A. For public companies: ask about refresher cadence and the most recent annual grant pattern.
  3. What's the company's stance on exit options — extended exercise windows for departing employees, secondary sales for tenured employees? Companies that take equity seriously support employees who hold it. Hostile policies tell you what they think of you long-term.
  4. How often does comp get reviewed — annual cycle, off-cycle adjustments, market refreshes? Healthy comp programs have a regular review and the means to fix outliers.
  5. What's the bonus structure — guaranteed, performance, target percentage of base? "Discretionary based on company performance" is the answer when the bonus rarely hits target.
  6. Do you offer relocation, sign-on, or a stipend for home office / remote setup? Asking signals you're negotiating in good faith. Companies that have a real package will tell you.
  7. What benefits actually get used a lot — and which ones look great on paper but nobody touches? Reveals which benefits are real. "We have a learning stipend but nobody knows how to expense it" tells you everything.

Questions about the company's future

The strategic-level questions that get at "is this company going to be a good place to work in three years," not just today.

  1. What's the company's runway and burn? When was the last fundraise, and when do you next need to raise? For startups, ask. The "we don't share that" answer at a startup is a yellow flag — strong companies are confident about runway.
  2. What does the team look like in a year — same size, double, half? Direction more than the number. A team that's going to triple has different problems than one going to stay flat.
  3. Who are the company's biggest competitors, and what's the honest case for why you'll win? Tests whether leadership has a clear-eyed view of the market or believes its own marketing.
  4. What's the biggest existential risk the company faces in the next 18 months? Honest answer signals strong leadership. "We don't really face existential risks" signals leadership that isn't ready for them.
  5. What's a strategic decision the company made in the last year that you disagreed with, and how was the disagreement handled? Tests psychological safety at a senior level and the company's tolerance for dissent.

The closer: questions to ask in the final round

  1. What would make this hire a failure 12 months from now? Forces the interviewer to name the actual risks of the role. The honest answer is a gift — it tells you what to optimize for if you take it.
  2. If I joined and decided after six months it wasn't working, what would you want me to do differently? Tests how they handle hard conversations and whether they treat early-stage departures as failures of the role or of the person.
  3. Is there anything about my background that concerns you that I can address now? Gives you a chance to handle objections directly. Brave question, almost always worth asking.
  4. If you were me — same role, same level, same other offers — would you take this job? Why or why not? The single most underrated closer. A good interviewer will give you a real answer.

The five red-flag answers to watch for

Watch out for these patterns

Research culture before the interview

Read what real engineers say about a company before you walk in — culture profiles, verified Glassdoor ratings, and current open roles, all in one place.

Browse Culture Profiles → How to Evaluate Culture →

How to use these questions well

Don't read from a list. Internalize the spirit of each question and ask it in your own words, in the flow of the conversation. Reading off a sheet kills the rapport.

Match the question to the round. The manager round is for expectations, growth, and how 1:1s work. Peer rounds are for code review, on-call, and what the week actually feels like. Skip-level and senior leadership rounds are for strategy and the company's future. Asking your peer about company strategy wastes both your time.

Listen for what's missing. A great interviewer will not answer every question perfectly. What you're listening for is whether they engage seriously, name real specifics, and tell you the truth even when it isn't flattering. The companies you want to join are run by people who can do all three.

Triangulate across rounds. The single most useful technique: ask similar questions to two or three different people and compare answers. Where they line up, trust the signal. Where they diverge, that's the conversation to have with yourself before you sign.

The end goal isn't to "win" the interview. It's to walk out knowing whether this is a place you want to spend the next two to four years of your life. Reverse interview questions, done well, get you that answer.

Frequently Asked Questions

What are reverse interview questions?+
Reverse interview questions are the questions a candidate asks the interviewer — not the polite "what's your favorite thing about working here" filler, but the ones designed to surface what working there will actually feel like. Good reverse questions force specific answers that reveal culture, management quality, on-call burden, and growth expectations. They're how you stop optimizing for the job offer and start evaluating whether you want the job.
What's the best reverse interview question to ask?+
The single best question is: "Why did the last person who left this team leave?" It's specific, hard to dodge, and forces the interviewer into either an honest answer (good signal) or a non-answer (also good signal). Variations: "Who left the team in the last 12 months and what happened to them?" or "When was the last time someone on this team was promoted, and what did it take?" Specific names and timelines make evasion much harder than generic culture questions.
What questions should I ask about on-call and work-life balance?+
Ask concrete and quantitative questions, not philosophical ones. "How many pages did this team get last quarter? What was the on-call rotation last week — who was on it, and how did their week go? Walk me through the last Sunday someone got paged and what happened." These force the interviewer to either describe a real recent incident (and how it was handled) or admit there's a problem. "Do you have good work-life balance" is a question that gets a marketing answer; the rotation specifics get you the truth.
How many reverse questions should I prepare?+
Prepare 8 to 12 strong questions tailored to each round. You'll usually get 5 to 10 minutes for questions per round — that's enough for 2 to 4 substantive questions, not a full deck. Match the questions to the interviewer: ask the hiring manager about expectations and trajectory, ask peers about day-to-day work and meeting culture, ask senior leadership about strategy and what would make this hire a failure. Don't waste a manager round on questions a peer could answer better.
What are the biggest interview red flags engineers should watch for?+
Five patterns to take seriously: (1) the interviewer dodges questions about why the role is open or who left, (2) everyone on the team is new — the entire "team in place" is under 12 months, (3) work-life balance questions get laughed off or rerouted, (4) the interview itself feels rushed (one round, fast offer, pressure to decide), (5) the interviewer bad-mouths a previous employee. Any one of these is a yellow flag; two or more is a red one. Trust the pattern, not the pitch.
Is it okay to ask about salary and equity in the interview?+
Yes — and you should, ideally early. The recruiter round is the right place. Ask for the band for this role, the typical equity grant for this level, the refresher policy, the strike price for options (and the most recent 409A valuation if it's a startup), and whether they support exit options or extended exercise windows. Companies that refuse to share a band or get cagey about equity are companies that intend to underpay you. Real numbers up front save weeks of mutual time.

Compare culture before you commit

Side-by-side culture comparisons of hundreds of tech companies. Verified Glassdoor ratings, real culture values, current open roles.

Compare Cultures → Browse Companies →