Atlassian, the Australian software company behind Jira and Confluence, announced on March 11, 2026 that it is cutting approximately 10% of its global workforce — around 1,600 employees — to redirect resources toward artificial intelligence and enterprise sales.

The company expects to incur restructuring charges of between $225 million and $236 million, including $169 to $174 million in cash severance and $56 to $62 million in office consolidation costs. More than 900 of the roles eliminated were in software research and development.

CEO Mike Cannon-Brookes framed the decision directly: “We are doing this to self-fund further investment in AI and enterprise sales, while strengthening our financial profile.”

On the same day, Atlassian announced that CTO Rajeev Rajan, who held the role for nearly four years, would step down on March 31. He is being replaced by two AI-focused leaders: Taroon Mandhana as CTO for Teamwork, and Vikram Rao as CTO for Enterprise and Chief Trust Officer. The dual-CTO structure signals that AI capability and enterprise trust are now the two central technology priorities at the company.

What Is Actually Happening Here

The Atlassian announcement is one in a pattern that is accelerating through enterprise software. Block (formerly Square) made a similar move earlier this year. The logic in each case is the same: AI tooling changes what kinds of engineers and what mix of skills a software company needs. Roles built around manual coding processes, certain categories of R&D work, and operational overhead are being reduced. The capital freed up is being redirected toward AI infrastructure, model integration, and enterprise go-to-market.

This is not a story about AI destroying jobs in some abstract future sense. It is a story about a specific class of jobs — particularly those in software development that involve routine or repeatable work — being repriced and in some cases eliminated by companies that can now do that work differently.

The replacement of a single CTO with two domain-specific leaders is also significant. It tells you that “technology leadership” at an enterprise software company in 2026 has split into at least two fundamentally different jobs: one focused on building AI-native product capability, and one focused on the trust, compliance, and enterprise relationship work that enterprise customers require. Those two things are genuinely different skill sets, and Atlassian’s structure reflects that.

What This Means for Business

If you run a business that uses tools like Jira or Confluence, the short-term impact is minimal. These products are not going anywhere, and Atlassian is investing in them, not retreating from them.

The more important signal is structural. Atlassian is telling you something about where value is going to sit in software organisations over the next several years. The work that AI can handle is being handed to AI. The work that requires human judgment, enterprise relationships, and trust is being preserved and elevated.

That same logic applies to every business, not just software companies.

If your team still has significant headcount doing work that is routine, repetitive, or pattern-based — generating reports, triaging requests, managing standard workflows, handling inbound enquiries — that work is at the same inflection point Atlassian’s R&D organisation just hit. Not because AI will force you to cut people, but because the businesses that redeploy that time and cost toward higher-value work will start to outcompete the ones that don’t.

The businesses moving fast on this aren’t cutting teams. They’re redirecting them. The people who were spending 40% of their week on administrative work are now spending that time on the things that actually need human judgment. This is exactly the distinction we draw between AI automation and an AI workforce — and why AI won’t replace your team so much as change what it spends its time on.

The Atlassian story is not about AI replacing software engineers at scale. It is about a company with the financial resources and technical leadership to be early doing what every organisation will face in some version over the next two to three years: deciding which work needs humans and which work can now run without them.

That decision is coming for every business. The question is whether it happens on your terms or someone else’s.

---

The practical next step is the free Working With Claude field guide. Thirty-two pages covering the ecosystem, Claude Code, and how to govern a rollout properly. Get your copy.