Atlassian Cut 1,600 Jobs to Pay for AI. Is That the New Normal?

The memo is becoming familiar: "We're cutting jobs to invest in AI." Atlassian just sent it to 1,600 people.

What Happened

On Wednesday, Atlassian — the Australian software company behind Jira and Confluence — announced it would eliminate 10% of its global workforce, roughly 1,600 employees. CEO Mike Cannon-Brookes framed it plainly in a blog post: "We are doing this to self-fund further investment in AI and enterprise sales, while strengthening our financial profile."

Employees learned their fate via email. The restructuring will cost between $225 million and $236 million in charges and is expected to wrap up by the end of June 2026.

This isn't a company in freefall. Atlassian's year-over-year revenue growth has actually accelerated for three consecutive quarters. Its AI feature, Rovo, reached 5 million monthly users as of February. The cuts aren't a distress signal — they're a strategic reallocation. That distinction matters.

The Context: A Stock Down 84% From Its Peak

To understand why Atlassian is moving this aggressively, look at the stock chart. Shares have lost more than half their value this year alone and are down 84% from their 2021 peak. That peak, incidentally, came during the pandemic boom when remote work tools were considered indispensable infrastructure. Atlassian was a Covid-era darling.

Then generative AI arrived. Tools like Anthropic's Claude don't just compete with collaboration software — they threaten to absorb its core functions. Why pay for a separate project management layer when an AI assistant can search, summarize, assign, and track tasks in a single prompt? Investors have been pricing in that existential question for months, and the broad software selloff has been brutal.

Atlassian isn't alone. In February, Block's Jack Dorsey announced 4,000 layoffs, explicitly citing a push to put "intelligence" at the center of its operations. The pattern is becoming a playbook.

Sponsored

Advertise with Us

[email protected]

Sponsored

Two Ways to Read This

There are genuinely two defensible interpretations of what Atlassian is doing, and they lead to very different conclusions.

The optimistic read:Atlassian is making a hard but rational bet. The software landscape is being redrawn, and companies that don't build AI into their core products fast enough will be disrupted out of existence. Cutting 1,600 jobs now to secure the company's future — and the remaining ~14,400 jobs — is painful but responsible leadership. Revenue growth is accelerating. Rovo is gaining users. The fundamentals support the pivot.

The skeptical read: This is a financial engineering move dressed in AI language. Layoffs boost margins, reassure investors, and lift share prices in the short term. The "AI investment" framing provides cover for what is essentially a cost-cutting exercise. And if the AI tools Atlassian builds eventually reduce headcount further, the cycle repeats — just with fewer people at each turn.

Both readings can be simultaneously true.

Who Wins, Who Loses

The 1,600 employees losing their jobs are the most immediate losers, notified by email with no apparent prior warning. For context, Atlassian already cut 500 employees (5%) in 2023. This is the second significant reduction in three years at a company whose revenue is growing — a combination that would have seemed contradictory a decade ago.

Shareholders may benefit in the near term. Restructuring announcements in the tech sector have repeatedly triggered stock rebounds, as markets reward cost discipline even when the human cost is high.

For enterprise customers using Jira and Confluence, the immediate question is product continuity and support quality. Fewer engineers and customer-facing staff could mean slower development cycles or degraded service — risks worth monitoring.

For the broader tech labor market, each announcement like this recalibrates expectations. Software engineers, product managers, and project coordinators are watching their job descriptions quietly overlap with AI capabilities. The question is no longer abstract.