The Reverse Interview: The Questions Senior Engineers Should Ask — and What the Answers Reveal

Every interview loop ends the same way. The interviewer leans back, glances at the clock, and says: "So -- what questions do you have for me?" Most candidates treat it as a formality. They lob a softball about "the culture," nod at the answer, and let the last ten minutes evaporate. For a senior engineer, that is a wasted move on two fronts at once.

First, you are about to make one of the most expensive decisions of your career -- a two-to-four-year bet on a team you have spent maybe four hours with -- and this is the only unstructured time in the entire process to actually investigate it. Second, whether you realize it or not, you are still being graded. The reverse interview is the half of the loop where the candidate holds the pen. Used well, it does both jobs simultaneously: it de-risks the decision you are about to make, and it signals the exact judgment a senior role demands. This guide walks through the questions worth asking across the dimensions that actually determine whether you will be happy eighteen months from now -- team health, on-call, manager quality, growth, and business runway -- and, just as important, what a healthy answer sounds like versus a quiet red flag.

Your Questions Are Being Graded Too

Before we get to what to ask, understand why it matters beyond your own due diligence: the questions you ask are read as a direct proxy for how you think. Nothing makes this clearer than what executives say when they are off-script.

The flip side is that a sharp, specific question is one of the strongest seniority signals you can send. And the research on conversation is unusually precise about what "sharp" means. Harvard researchers studying what makes people more likeable in conversation found that it is not the sheer volume of questions that matters -- it is a particular type. As Harvard Business School's summary of the work puts it, "the rewards of asking more questions were driven almost entirely by asking more follow-up questions. Asking more mirror questions doesn't increase likability, either." A follow-up question -- one that builds on the answer you just heard -- proves you were listening and thinking. A canned question from a list proves only that you have a list.

So the goal of the reverse interview is not to fire off twenty questions. It is to ask a few good ones and then follow up on the answers. That is where both the real information and the rapport live.

What You're Really Deciding: A Multi-Year Bet

It is worth being honest about the stakes, because they justify the diligence. The odds that any given engineering job is actually a good one are not encouraging.

That dissatisfaction translates into motion. The same survey found that about 54% of developers are actively considering or have recently made a career move. When you accept an offer, in other words, you are joining a workforce where more than half the people around you are at least half-looking. The question the reverse interview has to answer is whether this particular team is one of the quarter worth staying in.

Crucially, the Stack Overflow data also tells you what to probe. When developers ranked the factors that drive job satisfaction, the top three were autonomy and trust, competitive compensation, and getting to solve real-world problems. "You like your manager" ranked only ninth out of fifteen factors. That does not mean managers don't matter -- they matter enormously for retention, as we'll see -- but it means your questions should be weighted toward the substance of the work and your autonomy over it, not just whether your future boss seems nice over a video call.

And the financial stakes compound the experiential ones. Levels.fyi's 2025 pay report puts median total compensation at $312K for senior engineers and $457K for staff -- a 46% jump for a single level. Choosing a team where you stall at senior, versus one where you reach staff, is a six-figure annual decision. The reverse interview is your diligence on that decision. (If the offer itself is the question, our guides on defending your level and the counter-offer trap go deeper.)

Questions That Reveal Team Health and Delivery

The fastest way to read a team's engineering health is to ask how software actually gets from a developer's machine into production. The gap between good teams and struggling ones here is not subtle -- it is enormous.

Ask it, and then follow up: "What's your lead time from merge to production? How long does a typical pull request wait for review? What does a deploy actually involve?" A healthy answer sounds like on-demand or daily deploys, code review measured in hours, and a pipeline nobody is afraid of. A concerning answer sounds like monthly release trains, review queues measured in days, and a release process that requires a designated person and a held breath.

Then probe the quality of the day itself. Productivity is not one number, and any team that claims it is should worry you. Microsoft Research's SPACE framework is built on exactly that premise: developer productivity "cannot be measured by a single metric or dimension" and spans five of them -- satisfaction, performance, activity, communication, and efficiency. The dimension candidates most underrate is flow. By one frequently cited estimate compiled by DX, developers lose about 23 minutes of focus per interruption -- so a team where engineers are pulled into six meetings a day is bleeding output no commit count will reveal. The same firm's research across hundreds of organizations found that teams with strong developer experience perform 4-to-5x better on speed, quality, and engagement. So ask: "How fragmented is a typical engineer's day here? How much protected focus time do people actually get?" The answer tells you whether you'll be building or just attending.

Questions That Reveal the On-Call Reality

If there is one topic where candidates are too polite to dig and pay for it later, it is on-call. The operational load of a team is one of the strongest predictors of whether you will burn out, and it is almost never advertised honestly in a job description.

You have a clean benchmark to measure their answer against. Google's own SRE book states the sustainable ceiling plainly: "the maximum number of incidents per day is 2 per 12-hour on-call shift." So ask: "How big is the on-call rotation, and how many pages does a typical shift get? How often do they fire overnight?" Overnight matters more than people think -- incident.io reports that about 36% of pages happen overnight, and those incidents take nearly twice as long to mobilize a response because someone is being dragged out of sleep.

Then ask about toil -- the manual, repetitive work that crowds out engineering. The trend is going the wrong way: data compiled in the 2026 state-of-incident-management roundup shows operational toil rising from 25% to 30% of SRE time -- the first increase in five years -- and, citing Harness, that 78% of developers spend at least 30% of their time on manual toil. A strong team treats toil as a number it actively budgets down. A struggling one treats it as just "the job." Your follow-up: "Is on-call compensated? And what's the team doing to reduce paging volume?" Silence on both is your answer.

Questions That Reveal Your Future Manager

Your direct manager is the single highest-variance factor in whether the job works out -- and one of the few you can actually assess in the loop, because you will probably interview with them. The data on their importance is overwhelming.

You cannot fully vet a manager in an hour, but you can ask questions whose answers are hard to fake. Try: "How long have you managed this team? How big is it? How do you run your one-on-ones, and how often?" Team size and meeting cadence are concrete proxies for whether you'll get attention. Gallup's research on span of control found that employees were highly engaged -- "about seven in 10" -- when they strongly agreed they got meaningful feedback, versus only "one in four" when they didn't; and Quantum Workplace found just 38% of employees have weekly one-on-ones, with the most engaged people meeting their manager weekly or monthly. A manager running a team of twelve who does one-on-ones "as needed" is telling you something real.

One honest caveat keeps this from being a referendum on likeability. The cleanest research on why people actually leave complicates the "people quit managers" cliché: Culture Amp's analysis found that development opportunities (52%) dominated departure decisions, with the manager cited by just 12% -- roughly on par with pay. The lesson is not that managers don't matter; it's that you should probe whether this manager will actively grow you, not just whether they seem pleasant. Which leads directly to the next dimension.

Questions That Reveal Whether You'll Actually Grow

For a senior engineer, stalled growth is the most common reason a job that looked fine on day one feels like a trap by month eighteen. And it is one of the most reliably mismeasured things in any interview, because every company claims to invest in development.

The trouble is the gap between what companies say and what they do. LinkedIn's 2025 Workplace Learning Report found that 88% of organizations are concerned about retention and name providing learning opportunities as their No. 1 retention strategy -- yet only 36% qualify as "career development champions" with programs that actually work, and just 15% of employees said their manager helped them build a career plan in the past six months (down from 20% the year before). The say-do gap is enormous, which is exactly why you ask for evidence, not intentions.

Ask: "Who was the last person promoted on this team, and how long did it take them? What's the concrete difference between a senior and a staff engineer here -- is there a written ladder?" A manager who can name a recent promotion, describe the rubric, and point to a written framework is showing you a real path. One who says "we're pretty flat" or can't produce a single example is, too. Velocity also varies wildly by company type: SignalFire's analysis found engineers at startups get promoted about 22% faster than at large companies (2.1 years between promotions versus 3.18 at a place like IBM). Neither is wrong -- but you should know which game you're signing up for. Our breakdown of the promotion-versus-job-hop math is the companion read here.

Questions That Reveal the Business Runway

Engineers are oddly squeamish about asking how the business is doing, as if it were impolite. It is not impolite -- it is the most basic form of diligence, and skipping it is how talented people end up surprised by a layoff. The failure statistics are sobering, especially at startups.

And the risk is no longer confined to startups. Crunchbase's tracker counted at least 127,000 U.S. tech layoffs in 2025 -- a 33% jump from 95,667 in 2024 -- which means "the company is big and well-known" is no longer a substitute for diligence. So ask, at any size. At a startup: "When did you last raise, how much, and what's the current runway? What's the path to the next round or to profitability?" At a larger company: "How is this specific org funded internally -- is it a growth bet the company is leaning into, or a cost center?" A founder or hiring manager who answers crisply is signaling confidence. One who deflects -- "we don't share that" at the offer stage -- has told you where you'd rank if the numbers got tight.

Questions That Reveal What You'll Do All Day

The single biggest gap between a role as pitched and a role as lived is usually the same thing: maintenance. The job ad describes greenfield features; the calendar is full of incidents and legacy systems. The way to surface that gap before you sign is to ask about technical debt directly.

The macro numbers explain why. A CISQ study put accumulated U.S. software technical debt at $1.31 trillion, growing 14% a year, and McKinsey case studies cited by one analysis describe a single bank whose 1,000-plus systems generated over $2 billion in tech-debt cost, and an insurer estimating debt at 15-60% of every IT dollar. Some of that will be yours. So ask: "What percentage of the team's time goes to new work versus maintenance and incidents? What's the oldest system I'd be touching, and is debt tracked and paid down deliberately?" A healthy answer is honest about the split and shows debt is on a roadmap. A red flag is a pure greenfield pitch with no acknowledgment of the legacy that pays the bills -- because it almost always exists, and someone is about to inherit it.

How to Ask So It Lands as Signal

Knowing what to ask is half of it; the delivery is the other half, and it is where the seniority signal is won or lost. A few principles tie the whole reverse interview together.

Bring more than you'll use, and tailor by person. Walk in with eight to ten questions and expect to ask four or five. The runway question is for a founder or hiring manager; the on-call and tech-debt questions are best aimed at the engineers you'll work alongside; the growth questions belong with your future manager and, if you get one, a skip-level. Asking your potential peer about fundraising, or the CFO about pager volume, just wastes a slot.

Follow up; don't read a checklist. This is the single highest-leverage habit, and it's the one the Harvard research backs directly. The first question gets you the rehearsed answer; the follow-up gets you the truth. "How's on-call?" earns a polished reply. "You mentioned it gets noisy during releases -- what's the team done about that?" earns something real. The follow-up is also what makes you memorable: it proves you were listening, which, as the research on follow-up questions and likability shows, is what actually builds rapport.

Triangulate across interviewers. Ask two or three different people the same core question -- "what's the biggest challenge facing the team right now?" -- and listen for whether the answers converge. Alignment is a green flag. Three wildly different stories about the team's top problem is itself the signal, regardless of what any one of them says.

Weight your questions toward the things that actually retain people, not the perks. The Conference Board's 2025 job-satisfaction survey found that job switchers cited culture and growth opportunities -- not compensation -- as their primary reason for moving. Pay gets you in the door; the things the reverse interview is designed to surface are what determine whether you'll still be glad you walked through it two years later. The "any questions for me?" moment is the one part of the entire loop you fully control. Treat it like the diligence it is.