An interviewer asks, "What would you do if you had a coworker you didn't get along with?" Fine. That one makes sense.
Some people at work just don't click with you. Opinions clash. Do you hand the work off, adjust how close you stay, or bring in your manager to sort it out if you have to? As a way to see how an applicant handles people, it's a perfectly normal question.
But when the questions start evolving like this, things change.
"Would you be okay if someone on the team comes on really strong?"
"What if someone from another department you barely work with was badmouthing you?"
"If someone said something untrue about you, how would you feel and what would you do?"
And it isn't just once. You get a similar scenario a second time, then a third.
By then, a different interview has started in the applicant's head.
"Wait, what is going on at your company?"
1. Once is standard. Three times looks like a pattern
If it comes up once, you can brush it off as a general check on stress tolerance and getting along with people.
"What if there's someone you find difficult?"
Yeah, yeah, people are people. Work is work. These things happen. End of story.
But when specific examples of the same kind keep showing up, the question itself starts to become information.
Pushiness.
Badmouthing.
A weird reputation coming from a department you have nothing to do with.
How to respond to unreasonable remarks.
The interviewer may simply be checking, "Is this person going to be okay here?" From the applicant's side, though, the thought slowly becomes:
"That's a pretty detailed example, isn't it?"
Once is a question. Three times is a tendency.
At this point it feels less like an aptitude test and more like a regression test for the workplace (the kind software teams run to see if old bugs come back).
2. "Difficult people" makes sense. So why is "badmouthing from another department" so specific?
"How do you work with people who think differently from you?" is abstract. It could happen at any company.
But once the setup gets as precise as "someone from a department you hardly deal with at work is saying bad things about you," the applicant naturally starts wondering where that scenario came from.
In a math word problem, you just solve it and say nothing.
In an interview, the person who wrote the problem is sitting right in front of you.
So the natural reaction is:
"Does that kind of thing actually happen here?"
Of course, a specific question doesn't prove that the same incident happened at that company. The interviewer might just have picked an easy-to-grasp hypothetical. They might be drawing on experience at a previous employer. It might be a standard question sheet the whole hiring team uses.
Still, the more specific it gets, the more the applicant learns something new: why is this case worrying them so much?
The interviewer is scoring the applicant's answers.
The applicant starts scoring the question sheet.
And just like that, the interview turns into a mutual review.
3. And if the person asking also feels a bit pushy, it's complete
Let's add one more condition.
The interviewer asking "Are you okay with pushy people?" gives off a bit of pressure themselves.
Now the question has an extra layer.
Interviewer: "Can you work with pushy people?"
What's going on in the applicant's head: "I'm currently getting the demo version."
Of course, an interviewer who speaks firmly isn't necessarily the problem person in the workplace. They may have been deliberately watching your reaction because it's an interview. Or they may just be asking tough questions because that's their role.
So jumping to "this person is the reason the last hire quit" is a total leap.
But humans build hypotheses from what's in front of them.
The question is oddly specific.
Similar questions keep coming.
And the person asking also gives off a bit of pressure.
Once all of that is on the table,
"No, surely not. But I can see how it looks."
is not a strange reaction.
What matters isn't establishing the backstory as fact. It's that the company is sending signals that look that way to an applicant.
4. The moment an interview question stops testing the applicant and starts describing the company
What the employer is after is probably this:
"If something unpleasant happens in the workplace relationships, will this person quit right away?"
That's a reasonable thing for a hiring side to want to know. Some people do quit over relationships, and companies want to cut down on mismatches after hiring.
But depending on how a question is built, it can send a second message at the same time.
If you keep repeating
"Could you put up with a pushy person?"
the applicant hears,
"Are you hiring on the assumption that there might be pushy people here?"
Pile on
"Could you handle it if people badmouthed you?"
and another reading appears:
"Are you looking for someone who can absorb badmouthing, instead of fixing an environment where it can happen?"
The company meant to make the applicant hand in an instruction manual for themselves.
But as the questions kept coming, the company's own instruction manual came out of the printer too.
That's the picture.
5. But "they asked" does not mean "that person actually exists"
This is where it's worth separating the joke from what you can actually establish.
Being asked a similar question three times doesn't tell you any of the following:
- Whether there really is a pushy employee
- Whether someone was harassed in the past
- Whether the previous person quit because of relationships at work
- Whether that interviewer was the cause of anything
- Whether the company is ignoring a problem
All of these stay unconfirmed without more information.
If you jump to "it's definitely that guy's fault," you get sloppy too.
On the other hand, you don't need to throw it all out as "the question means nothing."
The right spot is somewhere in between.
It's not proof. But it can be a signal worth checking.
That's the most usable distance to keep.
6. If the company really wants someone who can "put up with it," the issue is organizational design, not hiring
Suppose the company really does know that "there's a pushy person" or "gossip and clashes tend to happen."
And suppose the only fix is,
"Okay, next time let's hire someone who can put up with it."
That would be pretty interesting.
Instead of reducing the problem, they're selecting for people with a high tolerance for it.
In the short term that looks rational. If the last person wasn't a fit, hire someone who is.
But if the company still has causes it could change, trying to solve everything through hiring leaves the cost in place.
If the communication is too pushy, what will they do about feedback and management?
If groundless rumors affect the work, what do fact-checking and the channels for raising concerns look like?
If friction with a particular person keeps recurring, is it right to put the cause only on someone's "patience"?
The important point here is that "making the people on the receiving end tougher" and "building a setup where harm is less likely to happen" are different jobs.
Checking an applicant's people skills isn't wrong in itself.
But if the company has levers it could pull to improve things and still leans only on "procuring people who can endure it," you can see where that company tends to put the blame.
7. "So is this a company with people like that?" can sound provocative, but as a clarifying question it's quite reasonable
If you throw the original counter-question back as bluntly as it comes, it does sound confrontational.
"Is this a company full of people like that?"
Depending on the interviewer, the room can go cold in an instant.
But the information you want is legitimate.
If you smooth it out a bit, you could ask something like this:
"Is that a general scenario, or is it something that tends to actually happen in this department?"
"If that kind of interpersonal trouble comes up, is there a system where a manager or HR steps in, beyond the two people sorting it out themselves?"
"You've checked on this point several times. Is it something especially important for the team I'd be placed in?"
That way the applicant can find out the background of the questions without picking a fight.
An interview isn't a ritual where you ask permission.
It's also a place where the employer and the worker check whether they can work together on these terms.
So just as the company checks how well you handle difficult relationships, you're free to check how well the company handles them.
8. In fact, the most informative thing is how the interviewer answers your follow-up
The answer to "Why do you ask that?" reveals a lot about company culture.
For example, if they say,
"It's a general question. We're not thinking of any particular problem."
then that's one explanation, and it stands on its own.
If they say,
"Actually, a lot of people in this department speak their minds plainly, and some people in the past were thrown off by it."
then at least they're giving you concrete background.
If it ends with just
"Getting along with people like that is part of the job."
that gives you something to look at: how far does this company treat friction as a matter of individual adaptation?
And if they can go further and explain the system, like
"When a problem comes up, the manager steps in like this."
"There's a way to consult HR."
"If the same problem continues, we review assignments and management too."
then it means something very different from a plain "just put up with it" question.
In other words, you don't have to judge a company from the question alone.
Question, then ask the reason, then watch the response.
Do that much, and speculation gradually turns into observed data.
9. Summary: in an interview, the question sheet is being screened too, not just the applicant
"What would you do if you had a coworker you didn't get along with?" is a perfectly ordinary question on its own.
But when pushiness, badmouthing, odd reputations from other departments, and unreasonable remarks all come up as closely related scenarios, again and again, it's natural for the applicant to wonder, "Wait, did something actually happen?"
And if the person asking also gives off a bit of pressure, the whole thing becomes a polished comedy sketch.
Interviewer: "Are you okay with pushy people?"
Applicant: "I'm running a function check right now."
Still, being funny is no reason to turn the backstory into fact.
You can't say "the last person quit because of that guy."
At the same time, there's no need to treat repeated questions as telling you nothing.
A question reflects what the company sees as a risk.
And whether a company "reduces problems" or "selects people who can put up with them" is an important difference when you're reading workplace culture.
An interview isn't a one-way screening.
While the applicant is answering, the company is answering too, the whole time.
Sometimes the question itself is the one doing the most talking.
