8 Interview Questions That Reveal a Toxic Workplace

The interview works both ways

Most candidates spend the entire interview trying to impress the company. But the interview is also your best opportunity to evaluate whether the company is somewhere you actually want to work. The right questions, asked at the right time, can surface problems that job postings, Glassdoor reviews, and polished career pages will never reveal.

These eight questions are designed to be professional and appropriate while uncovering the things that make a workplace toxic. Pay attention not just to what they say, but to how they say it.

1. "What happened to the last person in this role?"

This is the single most revealing question you can ask. If the person was promoted, great — that suggests a growth path exists. If they left the company, ask a gentle follow-up: "Was there anything about the role or the team that contributed to their decision?"

Watch for: hesitation, vague answers ("they decided to pursue other opportunities"), or a quick pivot to a different topic. If the role has been vacant for a long time or if multiple people have cycled through it in a short period, that's a signal the role has structural problems.

2. "How does the team handle disagreements?"

Healthy teams disagree. What matters is whether they handle it well. A good answer describes a specific process: structured feedback, open discussion in meetings, clear decision-making authority. A bad answer is "we don't really disagree" (which means disagreement is suppressed) or an uncomfortable laugh followed by "we figure it out."

If a team can't articulate how they handle conflict, they probably don't handle it well. That means unspoken resentments, passive aggression, and decisions made by whoever is loudest or most senior.

3. "What does a typical day look like here?"

Listen for specifics. "You'd spend mornings in sprint planning and the afternoon on code reviews and feature development" paints a picture. "Every day is different — you never know what's coming" might sound exciting but often translates to "there's no structure and you'll constantly be firefighting."

Also listen for mentions of extended hours framed as normal. "Most people get in around 8 and leave around 7" is a nine-to-five company pretending to be a culture — it's an eleven-hour-day company being honest about it.

4. "How do you give feedback to direct reports?"

Ask this to your would-be manager. Strong managers have a clear answer: regular one-on-ones, quarterly reviews, real-time feedback on projects. Weak managers say things like "my door is always open" (which means they wait for you to bring up problems) or "we're pretty informal about that" (which means you'll never know where you stand until it's too late).

A manager who can't describe their feedback process probably doesn't have one. You'll spend your tenure guessing whether you're doing well until the annual review delivers surprises. For more on reading interview signals, our guide to interview red flags covers what to watch for from both sides.

5. "What's the biggest challenge the team is facing right now?"

This question tells you two things: what you're actually walking into, and whether the interviewer trusts you enough to be honest. Every team has challenges. If they say "nothing, things are great," they're either not being candid or they're not aware of their problems — both concerning.

A thoughtful, specific answer ("we're scaling faster than our processes can keep up" or "we lost two senior engineers and are rebuilding knowledge") shows self-awareness and transparency. That's the kind of environment where problems get solved rather than ignored.

6. "How does the company support professional development?"

Not "do you have professional development?" but "how." Companies that invest in their people can describe specific programs: training budgets, conference attendance, mentorship programs, internal mobility paths. Companies that don't invest in development will give you a vague answer about "opportunities to grow" or redirect to the job itself as the development opportunity.

Follow up by asking whether anyone on the team has used these programs recently. A professional development budget that exists on paper but never gets approved in practice is the same as no budget at all.

7. "What would make someone unsuccessful in this role?"

This is a subtler version of asking about culture fit. The traits and behaviors they describe as leading to failure tell you what the environment actually rewards. If "unsuccessful" means "someone who needs a lot of structure," you're joining a chaotic team. If it means "someone who isn't comfortable with 60-hour weeks," the work-life balance they mentioned earlier is aspirational, not actual.

Pay attention to whether the failures they describe are about skill gaps (trainable) or cultural expectations (baked in). Skill gaps you can close. Cultural mismatches only get worse.

8. "Is there anything about this role or team that gives you pause?"

This is a bold question, and not every interviewer will answer it honestly. But the ones who do will give you invaluable information. Some interviewers, when asked directly, will share genuine concerns: "The workload has been heavy since we lost a team member" or "The transition to new management has been bumpy."

Even if they don't answer fully, their reaction is data. A defensive response ("Why would you ask that?") is different from a thoughtful pause followed by an honest assessment. The interviewers who treat this question seriously are often the ones you'd want to work for.

Your questions are your protection

You can't fully evaluate a workplace from the outside, but you can gather far more information than most candidates do. These questions aren't adversarial — they're the due diligence you'd do before any major decision. Ask them respectfully, listen carefully, and trust the signals you receive. A company that can't handle honest questions during the interview won't handle honest feedback after you've started.