Atlassian’s “Rich Jerk” Case Tests Limits of NLRA Protected Workplace Speech

A pending NLRB case involving software company Atlassian could clarify whether can you be fired for criticizing the CEO.

In 2023, an engineer was terminated from Atlassian after a heated company-wide “ask me anything” meeting about a major “re-leveling” plan that would cut headcount and demote employees. Leadership had framed the restructuring as affecting only a handful of employees. When workers pushed back, the CEO — joining the meeting from the headquarters of an NBA team he co-owns — “angrily interjected” to confront employees who were complaining.

The engineer posted in an internal Slack channel dubbed “Outrage Notification”: “What’s up Outragers, just dialing in from my NBA team’s headquarters to yell at the people whose careers I’ve just pummeled.”

She was fired shortly afterward. Atlassian’s stated reason: she “engaged in acrimonious communications and ad hominem attacks against teammates and colleagues.”

The NLRB’s position: this kind of speech is protected concerted activity, and “employees are allowed to do so in ways their bosses might not like.” The NLRB also leaned on Atlassian’s own “Open Company, No Bullshit” core value, which the company has publicly touted.

Atlassian’s counter: “Just because it was a CEO doesn’t excuse the conduct. It was an irrelevant personal attack and insult directed at a colleague, essentially calling him a ‘rich jerk.'” The company argues protected concerted activity does not shield “abusive or gratuitously insulting” conduct.

This case is interesting on multiple levels:

1. The new NLRB is going to have to apply Lion Elastomers (the context-driven framework for evaluating allegedly abusive conduct during protected activity) — or replace it. How the case is decided will signal where the Board is going on this question.

2. The “culture of transparency” angle matters. Companies that publicly tout their openness and willingness to take criticism are creating an interpretive context that supports protected-activity findings.

3. The pretext analysis matters too. Was the engineer fired for what she said about restructuring (protected) or for the specific insult of the CEO (potentially not)?

4. If the ALJ rules against Atlassian and the case is appealed to federal court, this could become a significant precedent on the boundary between protected criticism and unprotected abuse.

For employers, the prudent takeaway: even employees who criticize executives sharply in internal channels generally cannot be fired for that criticism if the underlying speech is about working conditions.

Where should the line sit between protected dissent and termination-worthy insubordination?