Atlassian Layoffs 2026: Where the Cuts Are Hitting

Atlassian cut 1,600 jobs on March 11, 2026, eliminating roughly 10 percent of its global workforce to self-fund AI and enterprise sales investments, with CTO Rajeev Rajan stepping down March 31 and most exits completing by end of June.

The CEO framing was that the mix of skills a SaaS company needs is changing. The hiring-side read is more specific. About 1,600 Jira administrators, Confluence platform engineers, Bitbucket Pipelines engineers, ITSM consultants, and Atlassian Forge developers landed in the market the same quarter every enterprise PMO is reviewing its toolchain spend and asking what to do with the $225 million severance number Atlassian disclosed in its 8-K.

Last updated: May 16, 2026

Mike Carter, KORE1. I have spent the last fifteen-plus years placing software engineers, DevOps specialists, and platform administrators into mid-market and enterprise environments. Most of those companies run their delivery on some flavor of the Atlassian stack. KORE1 collects a placement fee when you hire through our IT staffing services practice, so the angle below leans toward “this pool is underpriced and easier to land than the supply numbers suggest.” Saying that up front.

What follows is built from Atlassian’s own March 11 employee memo, the SEC 8-K filed the same day, CNBC and TechCrunch coverage, the company’s Q3 FY2026 earnings commentary, public LinkedIn movement out of Sydney, San Francisco, Bengaluru, and Amsterdam, and what the DevOps and platform desks at KORE1 have been seeing since mid-March. Atlassian’s cuts do not look like the rolling drips we covered at Snowflake or SAP. One memo. One morning. Sixteen hundred goodbyes.

What the Memo Said and What It Didn’t

The note went out on a Wednesday morning Sydney time. Every Atlassian employee received an email within twenty minutes of the company-wide announcement letting them know if their role was affected or if a consultation process was starting in their region. Speed was the design choice. So was the brevity.

Mike Cannon-Brookes, the co-CEO who has run point on Atlassian’s public AI commentary, wrote that the approach was not “AI replaces people.” His next sentence was more honest. He said it would be disingenuous to pretend AI does not change the mix of skills the company needs or the number of roles required in certain areas. Read carefully, that is an explicit admission that specific functions were targeted. Not generic belt-tightening across every team. The full memo is on the Atlassian company blog.

The same morning, Atlassian filed an 8-K disclosing total restructuring charges of $225 million to $236 million. The breakdown matters. Severance and benefits ran $169 million to $174 million. Office space and lease reductions came in at $56 million to $62 million. Most of the cost landed in the company’s Q3 FY2026 results, per CNBC’s coverage of the announcement.

One detail that surfaced in the reporting but did not get amplified: Atlassian retained its 2026 graduate intake. Every grad offer extended in the prior recruiting cycle was honored. That is not a normal layoff move. It is a signal about where the company sees its skills gap, which is junior AI-native engineers who think in agentic workflows out of the gate, not seasoned platform veterans who learned on a different paradigm.

Two notes on the table. The role mix at the top of this round was weighted toward customer-facing and operations work, not pure engineering. Several sources reported sales managers and customer success leads were hit hardest, with engineering taking a smaller and more surgical share. Second, “consultation” is the legally required process in Australia, the EU, and the UK before a role can be eliminated. The number of departures is fixed at 1,600 but the actual exit dates roll out over months, with some Atlassian employees still working through their notice period into August in jurisdictions where statutory consultation runs longest.

The CTO Reshuffle That Got Less Coverage

Rajeev Rajan ran engineering as CTO for almost four years. His successor is not one person. It is two.

Taroon Mandhana, previously head of engineering for AI and products, took the title CTO, Teamwork. Vikram Rao, who had been Atlassian’s chief trust officer, became CTO, Enterprise while retaining the Chief Trust Officer responsibilities. Splitting the CTO role across “Teamwork” and “Enterprise” is the more interesting signal in this whole story, and the timing of the split (announced the same morning as the layoffs and effective at the end of the same month) is consistent with Atlassian putting the Enterprise plane on a different operating cadence than the legacy Teamwork stack. It says the company sees its product surface as functionally bifurcated. The legacy Teamwork bundle (Jira, Confluence, Bitbucket, Trello) is one swim lane. The Enterprise plane (cross-cloud agentic AI, Rovo, large-account governance and trust) is another.

For hiring teams sourcing former Atlassian engineers, that org chart is a useful read. People who left the Teamwork side will know the legacy product, the dogfooded internal use cases, and the migration pain points of large customers who actually run on Jira Service Management or Confluence Data Center. People who left the Enterprise side will know agentic patterns, Rovo’s integration surface, and how the company sells governance to Fortune-500 risk officers. Same résumé header. Two very different skill sets.

Four Atlassian Profiles Hiring Managers Are Underestimating

Most of the displaced 1,600 do not fit the “AI engineer the market needs” cliché, and several of the cohorts that landed in this round are the ones recruiters routinely treat as PMO overhead and price accordingly, which is exactly why the comp ranges further down this post tend to settle lower than they should given the actual skill profile. Worth a second look.

1. Jira and Confluence Platform Administrators

Companies with a hundred engineers running on a shared Jira instance underestimate what an experienced platform admin actually saves them. The right hire owns project schemas, workflow design, custom field hygiene, automation rules, permission scheme cleanup, and the slow strangler-fig migration off whatever Frankenstein workflow the team built over five years. Bad admins let the instance rot into 800 custom fields and four overlapping issue types. Good admins enforce a schema and absorb 60 percent of what would otherwise be ServiceNow license and ITSM contractor spend.

The displaced Atlassian admins are at the high end of this market. They came out of an org that dogfooded its own product at production scale. Many spent years inside Atlassian’s internal platform engineering function building tooling on top of Jira and Confluence APIs for thousands of internal users. That is a different caliber of admin than the certified-on-paper version coming off a one-year engagement at a regional consultancy.

Screen for: time spent on internal tooling work as opposed to customer-facing professional services. Ask them to walk through a specific automation rule they built that replaced a manual workflow. If the answer leads with “I added a webhook to a Forge app and used a queue-based reconciliation pattern because the synchronous version would have rate-limited under load,” you have a senior. If the answer is “I configured a Jira automation rule,” they are mid-level and priced accordingly.

2. Bitbucket and Atlassian DevOps Engineers

A non-trivial slice of the displaced cohort spent years building inside Bitbucket Pipelines, the Compass developer experience platform, and the integration points between Bitbucket and Jira. Most of that work transfers cleanly. Bitbucket Pipelines and GitHub Actions are not the same product, but the YAML literacy, the build-cache reasoning, the artifact promotion patterns, and the secret-management discipline all port over. A DevOps engineer who built a 200-stage Pipelines workflow at scale will be productive in GitHub Actions or GitLab CI within two sprints.

The catch: these candidates often price themselves on Atlassian-specific certifications, which the rest of the market does not weight heavily. Help them frame their experience as platform engineering and CI/CD work first and Atlassian-stack work second. The comp expectations come into line and the hire closes. Our DevOps engineer staffing desk has been routing this exact profile into GitHub Actions and Argo CD shops since late March.

3. Jira Service Management and ITSM Specialists

JSM specialists are the most undervalued group in the pool. Most hiring managers see “Jira Service Management” on a résumé and read it as Atlassian-only. The actual skill set is ITSM as a discipline. Incident command, change management workflows, problem record hygiene, SLA design, knowledge-base structuring for AI-assisted search.

That skill set ports directly to ServiceNow, Freshservice, Halo, and TopDesk migrations. Three of our last seven ITSM placements this spring came out of Atlassian’s customer-facing JSM organization and landed in companies that are moving onto a different ITSM platform but needed someone who has actually run an enterprise support operation end-to-end. They were our cheapest senior placements of the quarter.

4. Forge App Developers and Marketplace Engineers

Atlassian’s Marketplace economy runs on Forge, the serverless platform for cloud apps. Forge developers know runtime-isolated function patterns, fine-grained permission scopes, OAuth 2.0 with PKCE, and Atlassian-specific concepts like Forge tunnels and the Forge CLI. Most of that experience generalizes. Serverless function patterns are serverless function patterns whether the runtime is Forge, AWS Lambda, Cloudflare Workers, or Vercel Functions.

The Marketplace engineer side is more specialized. These are the engineers who built integration tooling, dashboard widgets, and workflow extensions that ran inside Confluence and Jira. They scale awkwardly outside the Atlassian ecosystem unless they have a parallel track of public-cloud serverless work on their résumé. Worth a careful interview before offering.

The Salary Reality

The displaced Atlassian cohort is priced higher than the broader DevOps and platform admin market, but not by as much as some headline coverage suggests. Australia base salaries at the Sydney HQ run in AUD, which when converted lands close to U.S. mid-market comp once you account for tax differences and the absence of U.S.-style equity refresh cycles.

Sources: Levels.fyi public Atlassian comp data, Glassdoor comp ranges, ZipRecruiter postings for the equivalent target roles, and our own placement closings between mid-March and early May 2026. Two-aggregator variance was real on the senior DevOps and Forge tiers, where Levels.fyi data ran 8 to 14 percent higher than the Glassdoor median, almost entirely on the equity-grant side.

Three things worth flagging. Sydney candidates take a discount in USD-converted terms but they cost less in absolute employer dollars. Severance from Atlassian was generous (sixteen weeks base plus pro-rated benefits in most regions), which gives candidates a longer runway than the typical 90-day cliff. That changes the negotiation dynamic. Hiring managers who lead with comp-only offers will lose to teams that lead with the engineering problem to solve.

How Long This Window Stays Open

End of June 2026 is the company’s stated deadline for completing the consultation and exit process. Most candidates will start their formal search in late April through mid-June. Severance runs them through August or September in most cases. After that, the visible pool thins fast.

Where the talent is going so far, based on our routing data and public LinkedIn moves: HubSpot is hiring aggressively into platform and CRM-adjacent ITSM. GitLab is picking up Bitbucket Pipelines engineers at obvious salaries. Linear and Notion have been opportunistic on the Forge and Marketplace developer side. Asana, perhaps unsurprisingly, has been quietly picking off Jira admin and JSM specialist talent. And the consulting firms (Slalom, EY Atlas, Deloitte, and the SAP-native specialty firms cross-shopping into Jira and JSM migration work) have been hiring at the architect level.

What that means for a mid-market hiring manager: the senior platform admin and JSM specialist tiers are findable through end of June with light reach-out effort. The Senior DevOps Engineer and Solutions Architect tiers close faster because the well-known competitors are explicitly hunting them. The Forge developer pool is small to begin with, and once the obvious HubSpot, Linear, and Notion offers go out, the remainder is mostly contractors and consultancy plays. For context on the broader 2026 cycle, see our tech layoffs index.

Common Questions From Hiring Managers

These are the questions we have actually fielded from clients since the Atlassian announcement landed.

How many former Atlassian employees are actually findable right now?

About 800 to 1,100 across U.S. addressable markets through June 2026, based on LinkedIn movement and our pipeline.

That number gets smaller fast. Sydney represents roughly 35 percent of the cuts and most of that talent is constrained by U.S. visa availability, which means the headline 1,600 number tells you something very different from the number actually accessible to a hiring manager running U.S.-payroll-only requisitions. Bengaluru is another 25 to 30 percent, similarly geography-bound. The U.S.-located cohort (San Francisco, Austin, Mountain View, NYC) is closer to 500 to 700 people, with another couple hundred remote-eligible workers spread across smaller domestic markets. That is what is realistically hireable inside U.S. payroll without sponsorship.

Should we hire former Atlassian engineers for non-Atlassian stacks?

For DevOps, platform admin, and ITSM roles, almost always yes. The skill set is portable.

The exception is at the very senior architect tier where someone built their entire career on a single Atlassian product line. A 15-year Confluence-only architect is a specific shape of hire that may not translate to a Notion-and-Linear shop, and the comp expectations may not adjust quickly. For everyone below the principal level, the transition is straightforward and most of the productivity ramp clears inside the first 60 days. Forge developers need an extra interview round on language and runtime generalization. Senior DevOps engineers and platform admins port across stacks the way most senior infrastructure people do.

What does a senior Jira admin actually save a 200-engineer org?

Six figures, usually. Sometimes north of $200K against the alternative of leaving the instance to drift.

A bad shared Jira environment burns engineering hours in three predictable ways. Workflow friction, where engineers spend 30 minutes a day arguing with the issue tracker. Reporting unreliability, where the PMO runs manual spreadsheet pulls because the dashboards are wrong. License bloat, where teams pay for premium tiers because nobody cleans up automation rules that ran amok. One senior admin who owns the instance closes all three. Conservative estimate against a 200-engineer org: 1 to 2 percent of total engineering capacity recovered, which at fully-loaded comp lands well into six figures of effective value annually. We have closed that argument with four CFOs this year.

Are visas a problem for hiring from the Sydney layoffs?

Yes. The math is not favorable on most candidates.

H-1B sponsorship is the realistic path for senior engineers and most of Atlassian’s Australian talent does not have a U.S.-cap-exempt history. O-1A is occasionally viable for the senior architect tier with the right credentials. The faster route for most hiring managers is to either staff a candidate from Sydney into a remote contractor role billed through a global payroll provider, or to wait for the candidate to relocate via a secondary path (often a TN visa for Canadian-citizen Atlassians who lived in Sydney, or an internal transfer through a U.S.-presence company first). Plan on three to nine months of timeline if you want the Sydney pool. The U.S.-resident pool is faster.

Is this an AI-washing story or a real AI shift?

Both, in different proportions for different parts of the org.

The customer success, support, and operations cuts are the more honest “AI displacement” portion. Rovo workflows, agentic ticket routing, and AI-assisted documentation generation absorbed real headcount in those areas, and the productivity numbers Atlassian disclosed on its earnings call (5 million Rovo MAU, cloud revenue growth at 25 percent-plus) support the case that the AI deployment is generating measurable lift. The sales and management cuts read more as a SaaS growth-model adjustment dressed in AI clothing. Atlassian’s revenue base outgrew its sales coverage model and the company is rebuilding around enterprise sales rigor, which is a more conventional reason to thin out the mid-tier ops layer than the “AI changed our skill mix” framing suggests. Both stories are true at the same time. The proportions just differ by function. TechCrunch made the AI-washing case the day after the memo.

If You Have an Open Req

If any of the four profiles above maps to an open req on your desk, we can move quickly. Most of our active Atlassian-displaced candidates have completed initial screens, references are in process, and we can introduce three to five qualified resumes inside a week. Talk to our team for the shortlist.

We staff direct-hire engineering roles and contract and contract-to-hire DevOps engagements across the same talent pool. The hiring window for this cohort closes faster than most layoff cycles. End of June is the planning anchor.