Interview the interviewer: 5 questions that expose a broken process

You spend the whole interview being evaluated. Flip it. You are about to hand this company the next two years of your working life, and diligence is what you owe yourself before you sign. Three separate Reddit threads blew up because job seekers shared the exact reworded questions that got them honest answers instead of press releases. This is the full set, with what each answer tells you and what a dodge probably means.

The rewording principle

Every diligence question has two versions. The soft version is the one everyone asks, and it gets the scripted answer, because interviewers have heard it a thousand times and have a polished response ready. The sharp version asks about the same thing through the back door, using specifics a script cannot cover.

"Why is this role open?" gets the press release. "What changed that made you hire for this role now?" gets the truth. That swap is u/ColonnadeMaroon41's. "Why did the last person leave?" gets a shrug. "What did the last person in this role struggle with?" gets a pause, and then something real. The pattern, proven across three threads that blew up: the standard question gets the press release, the reworded question gets the truth.

One more thing about the swap: the sharp versions are not rude. They are specific. Every one of them asks about the role's mechanics, which is exactly the ground an interviewer expects a serious candidate to cover. You are not accusing anyone. You are reading the job the way they will read your resume.

The five below are the set worth memorizing. Ask them exactly as written.

Question 1: "What changed that made you hire for this role now?"

Every role exists because something broke, grew, or left. This question asks for the trigger event, and the trigger tells you what you are actually walking into.

A good answer names a specific event: a product launch that overloaded the team, a resignation, a funding round, a workload that finally cracked. A specific trigger means the role is real, budgeted, and tied to a need the company can articulate.

The dodge is "we are growing" with nothing behind it. Growing from what, to what, driven by which event? If nobody can name the change, the headcount may be aspirational, which means it can evaporate the first time a budget gets tight.

If the answer feels thin, probe with: "What happens if this stays unfilled for another quarter?" A real need has a real cost. "We would manage" tells you the role is optional.

Question 2: "How long has this role actually been open?"

Note the word "actually." The posting date is not the role age. Companies take postings down and repost them, which resets the clock you see and hides a search that has been stuck for months.

A role open for three months or more usually means one of three things: the spec is impossible (five jobs disguised as one), the scope keeps churning because the team cannot agree on what they want, or candidates keep getting to the final round and walking away. Each of those is information about the process you are inside of. None of them is a verdict on you, and all of them predict your odds.

The probe: "How many people have you interviewed for it?" A large number with no offer means the bar moves or the committee cannot decide. You want to know that before round four, not after.

Question 3: "What did the last person in this role struggle with?"

This is the rewording that does the most work. "Why did they leave?" invites a defensive non-answer, because departure stories can be personal. "What did they struggle with?" invites an operational answer, and operational answers are where the truth lives.

Listen for what the struggle was. Workload traps (the role was quietly two roles). Broken processes (everything required chasing three teams for approval). Skill gaps (they were hired for a job that did not match the actual work). Each one tells you what your first year would actually look like.

A company that answers this honestly is showing you something valuable: they know what went wrong, which means they can tell you what would go right. A company that claims the last person struggled with nothing is either not paying attention or not telling you.

The probe: "What would they warn me about?" If the interviewer hesitates here, the hesitation is the answer.

Question 4: "Is this a backfill or a new headcount?"

Two kinds of roles, two very different jobs.

A backfill means someone held this seat before you. Ask what happened with them and what the team learned from it. A backfill with a clear story (promoted, relocated, retired) is usually safe ground with defined expectations. A backfill with a vague story deserves Question 3 again, harder.

A new headcount means the role is being invented. That can be a chance to shape the job, or it can mean nobody knows what success looks like yet and you will be graded against a moving target. The probe for new roles: "Who did this work before the role existed?" If the answer is "everyone, between everything else," expect chaos until the role is defined. If the answer is "nobody, and that is the problem," the pain is real and the mandate is usually real too.

Question 5: "What makes someone fail in this role in the first 90 days?"

This one exposes the expectations nobody wrote into the job description. Every role has a hidden syllabus: the deliverable your manager actually needs by day 90, the relationship you have to build first, the process landmine that gets every newcomer.

A thoughtful answer means the company has thought about your success, which correlates with onboarding that exists. No answer at all is its own answer: if they cannot describe what failure looks like, they have not defined success either, and you will find out what it was at your first review.

Reading the answers: a 10-minute scorecard

Five answers is enough data to make a call, if you write them down right after the interview while they are fresh. Score each answer one of three ways.

Clear: specific, concrete, consistent with what you have heard elsewhere. Vague: generalities, buzzwords, answers that could apply to any company anywhere. Alarming: contradictions, visible discomfort, or a straight dodge on a question that should have an easy honest answer.

One vague answer is normal; interviews are human. A pattern of them is not. Two or more alarming reads is a walk-away signal, and the best time to see it is now, when you have leverage and other options, not at the offer stage when you are emotionally invested. Remember that an interview is the best behavior this process will ever show you. If the answers are evasive while they are still trying to win you, they do not improve after you sign.

The scorecard also keeps you honest in the other direction. When a search runs long, the temptation is to talk yourself into whatever is in front of you. Five written answers resist that editing. If the page says clear, it was clear. If you do get to offer stage with mixed signals, run the offer through the job description red flag checklist, and if you are weighing it against another one, our two-offers decision piece walks the comparison.

When to ask what

Do not fire all five in one conversation. On the recruiter screen, ask the factual ones: how long the role has actually been open, and whether it is a backfill. Save the deeper ones for the hiring manager, who owns the answers. Anything still unresolved, ask again before you sign. One good question per conversation is enough to start.

Frequently asked questions

What questions reveal red flags in an interview? The ones that ask about the role's history and mechanics: what changed to create it, how long it has actually been open, what the last person struggled with, whether it is a backfill, and what makes people fail in the first 90 days.

Will asking hard questions hurt my chances? Framed as diligence, they signal seniority. The Reddit threads behind this guide report interviewers engaging more, not less, when the questions are specific.

What does it mean if a role has been open for months? Usually a stuck process: scope churn, an impossible spec, or failed rounds before you. It is information about the process, not a verdict on you.

How can I tell if a job is a backfill? Ask directly: "Is this a backfill or a new headcount?" Then ask what happened with the previous holder and what the team learned from it.

What is a good answer to "what changed that made you hire now?" A specific trigger: a launch, a resignation, new funding, a workload breaking point. "We are growing" with no specifics is the dodge.

When should I ask these questions? One or two on the recruiter screen (role age, backfill), the deeper ones with the hiring manager, and anything unresolved again before you sign.

What if the interviewer will not answer? Evasion is an answer. Note which question they dodged. Two or more dodges across the set is a strong caution signal.

Should I ask about work-life balance directly? Ask about mechanics instead: what a typical week looks like, how urgent requests are handled, when the team is offline. Mechanics get honest answers; values questions get scripts.