The Reverse-Interview Question Table, by Interviewer and Answer

When the interviewer turns it back to you and asks what questions you have, most candidates recite impressive-sounding questions to the wrong person and walk out with reassurance instead of facts. This guide is for candidates in an interview loop who want to pick, for each person in the room, the two or three questions that surface what they still do not know, and to grade each answer as a green, amber, or red signal. It is a lookup table: jump to the fact you still need, read the row, and leave.

Public lists hand you 30 to 70 undifferentiated questions grouped by vague theme. The problem is not the questions. It is that the right question asked of the wrong interviewer produces a fluent, secondhand, useless answer. So the organizing unit here is one fact, one owner, and one decoding of what a specific versus an evasive reply proves.

Who can actually answer what

Each interviewer type owns a different slice of the truth, and asking outside their slice wastes your best source. Route the question to the one person equipped to answer it.

• Recruiters own process. The number and format of rounds, whether there is an assessment, timeline, and logistics. They are your source for the shape of the loop and, often, the first stop for compensation.
• Hiring managers own scope and success. This person runs the team, will likely become your direct manager, and is your best resource on the specific responsibilities of the role, their management style, team goals, and workplace culture.
• Peers own ground truth. A potential future colleague can tell you what it is actually like to work there, will often be more honest than the hiring manager, and can name the skills critical to success.
• Skip-levels own strategy. Director and VP interviews veer from the normal structure. Use them to learn about the leader, make a connection, and discuss career growth within the organization.

The trap is defaulting scope questions to whoever screens you first. One recruiter puts it plainly: she has never known a recruiter to have insight into the problems the team is trying to solve, and says that is a question for the hiring manager or the team. A recruiter will still answer it, fluently, because refusing feels unhelpful. That fluent answer is secondhand and you should not weight it.

Refolk's index makes the routing stakes concrete. You are more likely to be interviewed by the person who defines success than by a specialist recruiter, so misrouting scope questions burns your best source.

The question table, row by row

Here is the reference. Each row is one question, the fact it extracts, the interviewer who can reliably answer it, and how a specific versus an evasive reply decodes. Jump to the fact you need.

The pattern to notice: the fact and the owner are locked together. "What does success look like" is a hiring-manager question because a hiring manager should be able to define it, and it becomes a consistency probe when you also ask peers and the skip-level. "What range was the role scoped at" is a recruiter question because comp routes cleanest through the person who owns process. Move a question one column left or right and the answer degrades into guesswork.

How to decode any answer

The load-bearing distinction is specific versus vague, not confident versus nervous. A good answer names timelines, outcomes, and trade-offs. A bad answer is vague, defensive, or redirects the question back to you.

Grade on three levels:

• Green. The answer names a concrete outcome, timeline, or example. "In your first quarter you would own the billing service migration and success is a clean cutover by end of Q2." You can act on this.
• Amber. Directionally reasonable but generic. "You'd contribute to the roadmap and grow into more ownership." Not a lie, but not usable. Follow up once for a specific before you downgrade.
• Red. Vague after a follow-up, defensive, or flipped back to you. The named worst case in the record is an interviewer who answered "your job is to make me happy" with no definition attached. Evasion here usually means one of two things: they do not know, or they think the honest answer will scare you away.

The single most valuable extraction is the 3/6/9/12-month success horizon. Every hiring manager should be able to offer a perspective on it, and if they cannot, you will not know when you are succeeding. Without tangible markers the "success" answer degrades predictably into reassurance, which is why a specific horizon is worth pressing for twice.

Consistency, not eloquence, is the load-bearing signal; the same question asked three times exposes what one polished answer hides.

There is a second decoder that only works across interviewers: the consistency test. Career expert Amanda Augustine flags it directly - everyone involved should have similar responses to "what does success look like in this role," and if the hiring team is unclear on your exact duties or team, you are likely to face unclear expectations. So ask the success question of the manager, a peer, and the skip-level. Matching answers are green. Divergent answers are red, because the divergence is organizational conflict about the role that you would inherit on day one.

How many to prepare, and how long each answer should run

Prepare more than you will ask, because the conversation answers many of your questions before your turn. The research-backed target is 8 to 10 prepared and 3 to 5 asked at the end. Sources vary, and the variation is useful: a floor of two or three still beats having none.

HBR frames the end of the interview as time-bound triage: if you were scheduled for an hour and they turn to you with five minutes left, choose the two or three questions most important to you. For peer rounds, prepare at least two questions per peer, since peers are where ground truth leaks and you want backups if one gets answered early.

Answer length is a signal you control. Keep your questions and follow-ups tight, roughly 60 seconds, with a skip-level director or VP, and allow 90 seconds to two minutes with a peer or hiring manager. Rambling at the skip-level reads as a lack of judgment about their time.

One number cuts against overthinking this: having no questions at all is a documented red flag on your side. A recruiter told The Muse that when an applicant has no questions, that is a red flag. So the floor is real. Prepare the pool.

The procedure, loop to grade

Run this in order. It turns a pool of questions into a graded picture of the role.

Step one is implied across the sources rather than documented as a formal first move, but it is what makes the rest work. Without an owner map you will ask scope questions of recruiters and comp questions of peers, and grade the noise you get back as signal.

When to raise comp, level, and timeline

Route compensation to the recruiter and flip the question to a range. The timing guidance genuinely conflicts, so decide deliberately rather than defaulting.

The hold camp says wait: ask for the range only after they have expressed strong interest or extended an offer, and career-center guidance is consistent about holding compensation until the employer raises it or you make it to an offer. The early camp of recruiters disagrees - a talent acquisition manager argues expectations should come up in the first discussion because everyone's time is valuable and it is better to know you are aligned. Both can be right depending on how tight your market is.

The practical middle is to direct comp to the recruiter first and avoid naming your own number. Flip it:

Before I anchor on a number, can you share the range the company scoped this role at? I want to make sure we are aligned on level before we both invest more time.

Timeline questions belong at the end, directed to whoever runs the process, usually the recruiter. Ask what the next steps are and when you can expect to hear back. That single question gives you a date to hold them to and a signal about how organized the process is.

One structural note for UK candidates: expect the manager to handle process and comp sooner. In Refolk's index there are about 24 times fewer recruiter and talent-acquisition profiles in the UK than in the US, and thinner dedicated-recruiter density pushes those conversations onto hiring managers earlier.

How this goes wrong

This section is the one to read twice, because the failure modes produce answers that feel like signal and are not. Each row below pairs the mistake with the check that catches it.

Asking the recruiter a scope question. The false positive is a fluent recruiter answer that sounds authoritative but is secondhand. Recruiters generally lack insight into the team's actual problems. Check: route scope, success, and team-problem questions to the hiring manager or a peer.

Mistaking a confident vague answer for a good one. Confidence is not specificity. Check: demand a named timeline, outcome, or trade-off, and treat a redirect back to you as the tell.

Grading one interviewer in isolation. A single strong answer can hide organizational disagreement. Check: compare the same question across interviewers; divergence signals internal conflict about the role.

Reading evasion as modesty. A hedge is not humility. Check: shying away usually means they do not know or fear the answer will scare you off, so follow up once and grade what you get.

Raising comp or flex too early. The false positive is an interviewer who answers politely while quietly downgrading you. Check: save flexibility for round two and frame it around the team, not what the company gives you. Remote or flex questions in round one raise doubts about commitment before you have established fit.

Digging for reassurance disguised as a question. "Would you consider me a strong fit?" reads as fishing for compliments and turns a recruiter off. Check: if the question seeks a compliment rather than a fact, cut it.

Treating the peer round as a casual safe zone. Most candidates ask peers about lunch and vacation and get happy talk. Check: probe operational reality - roadblocks, workflow problems, conflicts - because peers leak what HR conceals only if you skip the pleasantries.

Skip-level rambling. Long-winded questions to a director or VP read as poor judgment about their time. Check: keep it to about 60 seconds.

Sourcing the people who can answer

The cleanest way to close a fact gap is to talk to someone before the loop who is not being interviewed alongside you. A current engineering manager or a recent leaver can give you the scope and stability read you cannot always trust from inside the process. Finding the right named person is the friction, and it is the friction Refolk removes: describe the person you want and Refolk returns real profiles to reach out to.

Refolk also tailors the story you bring into the room. It writes your resume from your own history, tailors it to each posting, and scores how well you actually fit, so the questions you save your energy for are the ones that decide the offer.

Keep the table current

Before you call your prep done, run this check. It converts the whole guide into a single pass over your loop.

The mechanics that make this evergreen are not the specific counts but the routing and the grading. Interviewer roles will keep owning the same slices of truth: process, scope, ground truth, strategy. Comp timing guidance will keep splitting between hold and early, so keep deciding deliberately rather than defaulting. And the specificity test - a named timeline, outcome, or trade-off - will keep separating a green answer from reassurance no matter how the market shifts. Re-run the loop map for each new process, and the table works again.