1,600 Jobs Gone
in a Single Morning

It was a Tuesday morning. At 9 AM, 1,600 people who worked at Atlassian — the company behind the project management tools Jira, Confluence and Trello that millions of teams use every day — received an email. They had twenty minutes to find out if their job still existed.

Twenty minutes. That is not a typo.

Workers reported on social media that they received an automated message giving them a short window to click a link and discover whether they were being let go. No face-to-face meeting. No manager call. A link. A countdown. An answer.

The memo from CEO Mike Cannon-Brookes was carefully worded. He called it adaptation. He said the bar for what "great" looks like for software companies had gone up. He acknowledged it was a very tough day. He promised severance packages above the legal minimum — a $1,000 technology stipend, accelerated bonuses, at least 16 weeks of separation pay.

And then, in after-market trading, Atlassian's stock went up 2%.

That single fact tells you more about what is happening in the tech industry right now than almost anything else. And understanding why — really understanding it — is what this decode is about.

Here is the part of this story that almost nobody is talking about.

Atlassian is not a struggling company. Before the layoffs were announced, the company had just reported cloud revenue of approximately $1.07 billion — up 26% compared to the same period a year earlier. Its contracted future revenue (a number called Remaining Performance Obligations, or RPO) had grown 44%. Its AI assistant tool, Rovo, had just crossed five million monthly active users. The company reaffirmed its full-year financial guidance on the exact same day it announced the cuts.

So if the company was growing, why did 1,600 people lose their jobs?

The answer lies in a number that never made the headlines: Atlassian has been unprofitable since 2017. In the most recent quarter, it recorded a net loss of $42 million — actually slightly worse than the $38 million loss from a year before. Enormous top-line revenue growth. Persistent bottom-line loss. Investors who have been patient for almost a decade starting to run out of that patience.

On the very same day Atlassian announced the 1,600 layoffs, something else happened — and it barely made the news.

Rajeev Rajan, Atlassian's Chief Technology Officer, announced he would step down on March 31st. To understand why that matters, you need to know who Rajeev Rajan is. He was not a junior executive. He spent over two decades at Microsoft in engineering leadership roles. He then became VP of Engineering at Meta — one of the most powerful technology companies in the world. He joined Atlassian four years ago to build their R&D organisation from the ground up.

And he left without publicly saying a single word about why.

This is not just a restructuring. This is a company changing the definition of what kind of person builds its future. And Atlassian is not the only one doing it.

To truly understand what happened at Atlassian, you need one piece of context that most news articles assume you already know. You almost certainly don't. It is called the SaaSpocalypse.

Atlassian's stock had already fallen more than 84% from its all-time high reached in late 2021, during the pandemic era when every software company looked invincible. By the time the layoffs were announced, it had lost more than half of its remaining value just since January 2026.

Cannon-Brookes never used the words "SaaSpocalypse" or even "investor pressure" in his memo. He said "the bar has gone up." That is a CEO speaking to two audiences at once — to the 1,600 people losing their jobs, and to the investors he desperately needed to reassure. The stock going up after the announcement tells you which audience was more satisfied.

When a company cuts jobs and says "AI is the reason," there are usually three things happening at once. Only one of them is the story they want you to hear.

The first thing: The Pandemic Overhire Hangover. Between 2020 and 2022, every tech company hired furiously. Digital demand exploded. Zoom, Atlassian, Meta, Amazon — they all grew teams at speeds that were never sustainable. When the boom ended, they were massively overstaffed. Companies have been quietly correcting that error for three years. Saying "AI changed the math" sounds better than "we hired too many people."

The second thing: Investor Pressure. The SaaSpocalypse made this worse. Cutting headcount while announcing an AI strategy sends a signal to investors: we get it, we're adapting, we won't be obsolete. The stock going up after layoffs is the market responding: finally.

The third thing — and this is the one that is genuinely real and genuinely new: AI is actually reducing how many people certain jobs require. Not in every role. Not evenly. But in specific areas — code generation, routine QA testing, data analysis, tier-1 customer support — one person using AI tools well can now do the work that previously required a team.

Atlassian's 1,600 job cuts made headlines. But zoom out, and you realise it is a single chapter in a much larger story.

In 2025, AI was cited as the cause of nearly 55,000 layoffs in the US alone. Earlier waves of cuts focused on operational and support roles. The 2026 wave is different. It is now reaching specialised and senior roles — engineers, data scientists, product managers — as companies reorganise entire departments around AI-first ways of working.

Here is what the data says. Here is what I think it actually means.

RationalFX, the financial research firm tracking these numbers, has done the maths: if layoffs continue at their current pace through 2026, total tech job cuts could reach 264,730 by year-end — surpassing 2025's total of 245,000. That is the straight-line projection. But real life is never straight-line.

The most important pattern emerging from all of this data is one that almost no CEO is saying out loud: companies that invested in reskilling their people before restructuring retained more talent and made better cuts. Accenture was a rare exception — CEO Julie Sweet explicitly committed to retraining employees whose roles could evolve, and only exiting those who could not adapt. Most companies did not try. They hired AI, then fired humans, without ever asking whether the humans could have made the transition.

Every headline about AI layoffs focuses on the same story: AI is taking jobs. Some say it is inevitable. Some say it is overblown. Most say some version of "upskill or be left behind" before moving on to the next news cycle.

But here is the question I have not seen asked — not once — in any of the coverage of Atlassian, Block, WiseTech, or any of the other 2026 layoffs.

How many of the 1,600 Atlassian employees who lost their jobs were actually given a fair chance to adopt AI — with real tools, real training, and real time — before the company decided they were no longer needed?

Because there is a difference between "this person's role was eliminated by AI" and "this person was never given the tools to compete with AI." The first is a technological inevitability. The second is a management failure dressed up as one.

Cannon-Brookes said: "Our approach is not 'AI replaces people.' But it would be disingenuous to pretend AI doesn't change the mix of skills we need." That is an honest sentence. But it quietly skips the harder question: whose job was it to change those skills? The employee's? Or the company that paid them?