We have all dealt with that one coworker who seems to hate us for absolutely no reason from day one. You try to be nice, you try to be professional, but they look at you like you’re something they accidentally stepped on in the parking lot. One guy on Reddit has been living this nightmare for eight months, and it finally culminated in an after-work happy hour blow-up that has the entire office picking sides. If you’ve ever wanted to see a petty assumption backfire in the most awkward way possible, this is the workplace drama you’ve been waiting for.
The Original Poster (OP) has been at his software company for six years, working his way up from a fresh grad to a department head. He’s clearly good at his job, but things got weird when “Shauna” was hired eight months ago. From the jump, Shauna treated him with zero respect, despite the fact that he literally outranks her. She would ignore him, interrupt him, and basically act like he didn’t exist. The OP couldn’t figure out what the f*ck he had done to deserve the cold shoulder, until a few drinks were poured at a company gathering one Friday.
As the team sat around sharing stories about how they got hired, Shauna finally let her true feelings fly. When it was the OP’s turn to speak, she interrupted him with a sarcastic comment about being the “company owner’s relative.” It turns out, Shauna had spent nearly a year hating this guy because they share the same last name as the big boss. Instead of realizing that their name is one of the top 20 most common names in the country, she just decided he was a “nepo baby” who didn’t earn his seat at the table.
The look on Shauna’s face when a coworker explained that the OP and the owner aren’t related in any way, shape, or form must have been priceless. She tried to laugh it off, but the OP wasn’t in a laughing mood. After eight months of being treated like sh!t for a crime he didn’t commit, he decided to fight fire with fire. He shot back with, “Yeah, that’s also rich coming from a diversity hire.” The table went dead silent, Shauna got upset, and she bolted from the gathering ten minutes later.
Now, the office is in a total tizzy. The other women at the table told the OP he went too far, but he’s standing his ground. He’s tired of being judged by someone he thinks was “too stupid” to realize that people can have the same last name without being cousins. Shauna even called in sick the following Monday, presumably to avoid the sheer embarrassment of her own making, but the OP is left wondering if his “eye for an eye” comment made him the villain of the story.
Let’s be real for a second: calling someone a “diversity hire” is a massive, nuclear-level insult in a professional setting. It implies that the person didn’t get their job because of their talent, but just to fill a quota. It’s a b!tch move to make, and it usually ends with a trip to HR. But on the flip side, Shauna spent eight months being a total ahole to her superior based on a completely fabricated “nepo baby” narrative. She was judging his merit just as much as he was judging hers.
The hypocrisy of Shauna is what really makes this messy. She was perfectly comfortable labeling him a “nepo baby” and treating him like dirt because of his name, but the second he used a similarly reductive label on her, she became the victim. It’s a classic case of “don’t dish it out if you can’t take it.” If you’re going to walk around an office assuming everyone’s success is unearned, you better be prepared for people to look at yours with the same skeptical lens.
However, two wrongs don’t make a right, especially when one of those wrongs involves a comment that can be seen as targeted or discriminatory. The OP might have had the moral high ground for a few seconds, but he definitely lost it the moment he brought “diversity hire” into the conversation. He could have just let her look like an idiot for her “nepo” mistake, but instead, he gave her a legitimate reason to go to HR and complain about his behavior.
The fact that Shauna called in “sick” tells us that the vibe at the office is officially ruined. Whether she’s genuinely hurt or just embarrassed, the damage is done. The OP thinks he was just defending himself against her “stupid” assumption, but he might have just tanked his own reputation as a leader. Leaders are supposed to handle conflict with a bit more grace than a middle-school lunchroom comeback, even when the other person is being a total jerk.
The OP is wondering if he’s the ahole, and honestly, this might be a “Everyone Sucks Here” situation. Shauna is an ahole for her unprofessionalism and her weirdly confident incorrectness. The OP is an ahole for using a derogatory corporate trope to shut her down. It’s a sh!t-show all around, and it’s a great reminder that if you’re going to talk bullsh!t at a work happy hour, you should probably make sure your facts are straight first.
So, NTA? Or a total ahole? The internet is split. Some think he gave her exactly what she deserved after months of mistreatment, while others think he crossed a line that can’t be uncrossed. One thing is for sure: that next staff meeting is going to be the most awkward thirty minutes of their entire lives. We hope they both have their resumes updated, because this level of bridge-burning is hard to recover from.
What would you do if a coworker called you a “nepo baby” in front of the whole team? Would you have stayed quiet and let her look foolish, or would you have hit her with a savage comeback of your own? Let us know in the comments if you think he went too far or if Shauna finally got a taste of her own medicine!
Well if you can dish it out … She started it .
.