Leadership IQ Research
How to spot a toxic candidate in a job interview
They looked perfect on paper. They interviewed beautifully. And three months in, you realized you'd hired a nightmare. Here's the science of catching them before you make the offer.
We've all hired somebody we thought was fantastic. Smooth, articulate, polished. And then three months in, we looked at them and thought: oh my gosh, what happened to you? This person is a nightmare.
So how did they get all the way through our interview process?
Here's the uncomfortable part. When we asked hiring managers about it afterward, 86% said that in hindsight, there were clues. Words the candidate used in the interview that, looking back, perfectly predicted this person was going to be a terror to deal with.
They heard the clues. They just didn't know what they were listening for.
There's a reason for that, and it's worth sixty seconds before we get to the interesting part.
Our Hiring for Attitude study tracked 5,200 hiring managers and roughly 20,000 hires over three years. 46% of new hires failed within 18 months.
But the number that matters is why. Only 11% failed for lack of skills. 89% failed for attitude — not coachable, low emotional intelligence, more motivated to get the job than to do it, or simply the wrong temperament for that culture.
And once you think about it, it's obvious why. Testing skills is easy. Hand a programmer thirty lines of code and have them find the errors. Hand a nurse a fetal monitor. Skills are black and white.
Testing attitude is the hard part. There's no laptop you can hand someone to measure coachability. So most companies don't really test it at all — they take a gut read and hope.
Which brings us to the interesting part.
Part One — Read this answer
Before I explain anything, try it yourself
I want to show you something rather than tell you about it. Below is a real interview question and a real candidate's answer — an actual response, not something I made up to prove a point.
Read it, and rate the candidate on a scale of one to seven. One means terrible fit. Seven means great fit. Be honest with yourself about your first instinct.
The interview question"Could you tell me about a time when you were asked to do something you didn't know how to do?"
The candidate's actual answer
"Oh, that's easy. I was always learning on the fly at my last job, mostly because we didn't have a lot of processes in place. Customers were always complaining that our billing system was seriously flawed, and yeah, they were right. I got stuck with way more tough problems than anyone else because my boss knew that I was really good at problem solving. Reaching out to a manager is one place you can start in this situation, or you can look for examples from how someone has solved things in the past — that can work too. I remember one time when a customer had a billing issue and my boss told me to check with my coworker, Sam, to see if he had any knowledge of the case. But Sam had nothing. In situations like this, I will take it upon myself to track back into the customer's records for clues, or I will call the customer to see if something was missed. I find that there's usually an answer if you look hard enough, but a lot of problems could be easily avoided if people would just be more accountable from the start. I've honestly never had a challenge I wasn't 100 percent certain I couldn't beat. I don't believe in failure."
Rate this candidate.
Go with your gut — the same way you would in a real interview.
Here's what everyone else said
I run this exact exercise in live sessions with hundreds of hiring managers and HR executives at a time. Roughly 60% of them rate this candidate a 5, 6, or 7. They'd move this person forward.
This is a bad answer. Not a borderline one — a genuinely bad one, with red flags stacked from the first sentence to the last. Keep reading and I'll show you every one of them.
When I ask people what they liked about that answer, the responses are consistent and reasonable. They say the candidate has a learning mindset — they were "always learning on the fly." They mention the problem-solving ability. They note the optimism: there's usually an answer if you look hard enough. Somebody who doesn't believe in failure.
All perfectly sensible. And all of it is wrong.
Part Two — The science
Attitude leaves a fingerprint in the words
Here's where this stops being an art and becomes something you can actually measure.
We asked 1,427 professionals to answer 15 open-ended interview questions as though they were applying for a job. After statistical validation, we had 20,572 answers. Then we had a panel of hiring managers and HR executives grade every one of them: is this a high performer answer, a low performer answer, or somewhere in between?
Then we did something nobody had done before. We took the high performer answers and the low performer answers and ran a linguistic analysis on both — comparing the actual words, the pronouns, the verb tenses.
The differences were staggering.
Low performers say "you" instead of "I"
Low performer answers contain 392% more second-person language. High performer answers contain 21% more "I" language. When someone stops telling you what they did and starts telling you what one should do, they've psychologically disassociated from the story. They're lecturing you in the abstract because they don't have a real example.
High performer
"I called the customer on Tuesday and I asked them to share their concerns…"
Low performer
"You should always call the customer and ask them to share…"
Notice what the second one does not tell you: whether they ever actually called a customer. It only tells you they know what the best practice would be. That's not an answer. That's a book report.
Low performers avoid the past tense
High performer answers contain 38% more past tense verbs — because they're telling you about something that actually happened. Low performer answers contain 104% more present tense and 71% more future tense. People without a real experience to share tend to spin a hypothetical instead: "when there is a problem, it's best to call the customer."
High performer
"I had a customer who was having issues with her server and was about to miss her deadline."
Low performer
"When a customer is upset, the number one rule is to never admit you don't know the answer."
Low performers speak in absolutes
Twice as many absolutes — always, never, impossible, unquestionably. Absolutes can signal insecurity, a need to show off, or black-and-white thinking. Ask yourself: when was the last time you experienced a situation in the real world that was always a certain way?
Low performers use far more negation
No, not, can't, couldn't, didn't. It's a cliché that hiring managers don't want to hear "can't" — but there's now evidence the cliché is true. Tension, low emotional intelligence, and pessimism all show up as negation.
Low performers name more negative emotions
Aggravated, irritating, pessimistic, unhappy. When a candidate openly discusses negative emotions, it raises the question of why they couldn't find a more positive resolution.
Low performers pile on adverbs
Quickly, constantly, often, usually. Insecurity or a need to paint oneself in a better light triggers embellishment. Instead of describing the time they had a brilliant idea, you get "I was constantly coming up with great ideas."
One more you probably haven't thought about since high school
There's a category of grammar called modal verbs — auxiliary verbs that imply probability and possibility rather than fact. Could. Should. Would. May. Might.
Notice what they're not saying. They're not saying "I did this thing." They're saying "I could do this. I would do this. You should do this." Possibility instead of history. Once you start hearing modals in an interview answer, you'll notice how much of the answer is describing a world that never actually happened.
The 13 words to listen for
Put all that research together and you get a cheat sheet. These are the 13 words that, once you know why they're there, become almost impossible to un-hear:
Absolutes · second-person pronouns · modal verbs · negation · negative emotions · adverbs
An important caveat
Does this mean anyone who says "always" or "never" in an interview is automatically a low performer? Of course not. Linguistic analysis is a gold mine for assessing attitude, but it's one part of a bigger process. The most successful hiring managers recognize the warning signals — and then probe deeper to get to the truth.
If you take nothing else from this page, take this: listen for "I did" versus "you should." That single distinction will change more interviews than anything else here.
Part Three — Back to the answer
Now let's go back to that candidate
Remember the answer you rated? The one 60% of hiring managers approve of? Let's walk through it with what you now know. Here it is again:
The interview question"Could you tell me about a time when you were asked to do something you didn't know how to do?"
"Oh, that's easy. I was always learning on the fly at my last job, mostly because we didn't have a lot of processes in place. Customers were always complaining that our billing system was seriously flawed, and yeah, they were right. I got stuck with way more tough problems than anyone else because my boss knew that I was really good at problem solving. Reaching out to a manager is one place you can start in this situation, or you can look for examples from how someone has solved things in the past — that can work too. I remember one time when a customer had a billing issue and my boss told me to check with my coworker, Sam, to see if he had any knowledge of the case. But Sam had nothing. In situations like this, I will take it upon myself to track back into the customer's records for clues, or I will call the customer to see if something was missed. I find that there's usually an answer if you look hard enough, but a lot of problems could be easily avoided if people would just be more accountable from the start. I've honestly never had a challenge I wasn't 100 percent certain I couldn't beat. I don't believe in failure."
They never answer the question
I asked for a time — a specific event, in the past. What did they give me? "Reaching out to a manager is one place you can start… or you can look for examples from how someone has solved things in the past." Those are hypotheticals about what one could theoretically do. Not one thing they actually did.
They tease you with a story, then bail
They start to give you something real — "I remember one time when a customer had a billing issue" — and your ear relaxes, because it sounds like a specific example is coming. It never arrives. Sam had nothing, and then they immediately retreat back into "in situations like this, I will…"
"I did" versus "you should"
Run the whole answer through that filter. "One place you can start" — that's you should. "You can look for examples" — you should. Where's the I did? The one time they reach for first person — "I find that there's usually an answer" — it immediately dissolves into a complaint about other people not being accountable.
The verbs are all wrong
I asked about the past. Count the past-tense verbs describing what they actually did. There aren't any. Instead: "I will take it upon myself," "I will call the customer," "problems could be easily avoided." Modal verbs and future tense — probability and possibility, not history.
Absolutes stacked on absolutes
"I was always learning on the fly" — really? Never a moment where you weren't learning? "Customers were always complaining" — there was never one customer who didn't complain? Not one? Always is a big word, and this answer is built out of them.
The line that should stop you cold
"I got stuck with way more tough problems than anyone else." Sit with that. Not "I was trusted with more tough problems" — stuck with. And not more than most people. More than anyone else on the entire team. Nobody else got as many as they did. That's a toxicity red flag, and it slipped out in passing, unfiltered, while they were trying to compliment themselves.
"I don't believe in failure"
This is the one everybody reads as confidence. It isn't. It's a person who cannot name a single real mistake. Combined with "I've honestly never had a challenge I wasn't 100 percent certain I couldn't beat" — that's not resilience, that's an absolute wrapped around an evasion.
Why this matters more than the obvious bad answer
You will occasionally get a spectacularly awful answer — a candidate who tells you their last boss was an idiot and every coworker was lazy. Those are easy. You don't need me for those.
This answer is the hard case, and it's what you'll actually encounter. There are no flashing red lights. It sounds fine. It sounds better than fine — it sounds positive and proactive, which is exactly why 60% of interviewers wave it through. The subtleties are where the problems are. Not the glaringly obvious stuff.
And remember one more thing about that answer: this is as good as this person gets. This is their Sunday best. They're trying to get the job. Are people more polished when they're trying to impress you, or six months after they've got the job?
"Toxic" isn't one thing
Worth pausing here, because that candidate raises a question: toxic to whom?
Yes, some people are toxic anywhere — the liars, the cheats. Those exist. But far more often, you're dealing with someone who is toxic in your particular culture and would be perfectly fine somewhere else.
If you have a fast-moving, constantly-changing culture and you hire someone change-resistant, that person will likely become toxic on your team. Put them in a stable, methodical organization and they're great. If you have a deeply collaborative culture and you hire someone highly individualistic, they'll probably become toxic in your environment — and thrive at a company built for individual contributors.
They're not bad. You're not bad. You're just bad together.
This is why you can't copy someone else's hiring. Southwest and Google are as different as night and day. You can't hire like Southwest unless you are Southwest. Which means the first real question isn't "how do I spot toxic people" — it's "what does toxic look like here?" Answer that, and everything else on this page has something to aim at.
Part Four — Your questions
You're giving away the answers
Everything above assumes you asked a question worth answering. Most interviewers don't — and the way they ruin their questions is so small you'd never notice it.
First, the questions to stop asking entirely
Tell me about yourself. What are your strengths? What are your weaknesses? Those are the three most common interview questions in North America, and every candidate has them rehearsed.
"Sure — I'm a motivated self-starter. I love individual accountability, but you know what, I also love working on teams."
"Weaknesses? Well, I don't like to share this too much, but sometimes I care too much. Sometimes I work too hard, and it can be a little intimidating to other people because I'm just so dedicated."
When you ask those questions, you are not testing attitude. You're testing acting ability and memory. They're not evil questions — they're just a complete waste of the twenty minutes you have.
Same goes for hypotheticals. What would you do if the server crashed at 2 a.m.? — "I'd instantly assemble a SWAT team, triage the customer needs, and bring the servers back in stages." Lovely. Now: will they actually answer their phone at 2 a.m.? You have no idea. When you ask a hypothetical question, you get a hypothetical answer.
And the leading question is the worst of all. "We're an incredibly collaborative culture — you're comfortable with that, right?" You just told them the answer and asked them to repeat it back.
Now the mistake that even good interviewers make
Here's the frame that fixes this. There are two kinds of people in the world: problem bringers and problem solvers.
Ask a problem solver about a problem, and they'll tell you about the problem — and then, automatically, with no prompting from you, they'll tell you how they solved it. They can't stop themselves. It's who they are.
Ask a problem bringer about that same problem, and they'll tell you about the problem. And stop.
That difference is pure gold. And you only get to see it if you stay out of the way.
The rule
Never ask people how they solved the problem. Ask them about the problem — and then stop talking. Let them choose. What they choose tells you everything.
Watch how easily it gets ruined:
Ruined
"Tell me about a time you had to adapt to a difficult situation — and what did you do?"
Fixed
"Could you tell me about a time you faced a difficult situation?"
Two things went wrong in that first one. The obvious one is "and what did you do?" — you've just handed them the ending and told them to skip to the part where they win. The subtler one is the word adapt. It presumes they adapted. Maybe they didn't. Maybe they sat there paralyzed — and wouldn't you want to know that before you hired them?
Ruined
"Tell me about a time when you had to balance competing priorities and did so successfully."
Fixed
"Could you tell me about a time you faced competing priorities?"
Again, two problems. "And did so successfully" tells the candidate: only tell me about your wins. And balance smuggles in the answer — I don't want to know about a time you balanced priorities, I want to know about a time you faced them, and then I need you to tell me whether you balanced them or dropped every one of them on the floor.
The magic words are faced and experienced. They're neutral. They presume nothing.
Fair warning
Every client who implements this tells me the same thing. The first "holy mackerel" moment comes when they stop giving away the right answers — because the stuff that comes out of people's mouths will blow your mind.
Ask someone about a time they faced a difficult situation, and you'll hear: "Oh, geez, every day was a difficult situation at my last job. It sucks over there. That's why I'm interviewing with you guys." That's a fantastic answer. It's terrible, and you shouldn't hire that person — but you learned it in two minutes instead of never.
Part Five — The part nobody does
Interviewing is a test. Where's your answer key?
Here's the thing that ties all of this together, and it's the step almost every company skips.
Interviewing is a test. You're giving candidates a test. So what's the point of administering a test if you don't have an answer key that lets you grade it?
An answer key — we call them Answer Guidelines — is simply a set of real-life good and bad answers to your interview questions, with an explanation of what makes each one good or bad. That's it. That's the whole idea. And it's the difference between hiring managers who guess and hiring managers who know.
Because here's what happens without one. Go back to that candidate you rated at the top of this page. In a live session with hundreds of hiring managers, the ratings for that answer spread across the entire scale. Some people give it a 2. Plenty give it a 6.
Why that spread is dangerous
If those were all hiring managers at your company, look at what you actually have: one manager is hiring this person and another is rejecting them. Same candidate. Same answer. Opposite decisions.
Whichever answer is right, your process is a coin flip. And that is precisely how bad attitudes sneak into a culture — not because everyone is bad at hiring, but because nobody is hiring the same way.
The fix is what I call a calibration exercise, and it's the single most valuable thing you can do with your hiring team this month. Take a real answer. Have everyone rate it independently. Then show the spread and talk through it together.
The first time a team does this, ratings are all over the map. By the second or third or fourth round, everyone lands within a point of each other. That's the goal. Not perfect agreement with me — internal consistency, so that the same candidate gets the same evaluation regardless of who happens to be in the room.
There's no other way to train this that works. You have to look at real candidate answers, and you have to make people evaluate them out loud.
One more reason this matters now
Candidates are using AI to game your interviews. That's not a prediction — it's happening right now.
So how do you stop it? You do what teachers do. If I give you a take-home assignment, I cannot prevent you from using AI — detectors are borderline useless and at worst actively biased. But if I get you in a room and hand you one of those old blue exam books, we're back to reality.
Which means the asynchronous video interview — where the candidate gets time to compose an answer off-camera — is now the worst tool you own. You've given them five quiet minutes with ChatGPT and a script to read back to you.
The counterintuitive conclusion: as AI gets better, live human interviewing skill becomes more valuable, not less. The ability to hear a rehearsed answer in real time is about to be one of the most important skills in your organization.
You already know what a toxic hire costs you.
You've lived it — the person who looked flawless on paper and turned out to be the wrong human entirely. The energy they took out of the room every single day.
It doesn't have to keep happening. We've trained more than 100,000 leaders on Hiring for Attitude, and we customize every piece of it for your culture:
We find the attitudes that actually separate your best people from your worst — because they're rarely the ones written on your wall. We build the interview questions that reveal those attitudes instead of giving them away. And we hand you the answer key, so every manager on your team hears exactly what you just heard.
See how we can helpQuestions before you start? Email jill@leadershipiq.com — Jill Sutherland, Director of Client Services.




