Atlassian’s announcement that it will cut roughly 1, 600 roles and its dispute with Professionals Australia over consultation form the two poles of this story. The comparison asks whether Atlassian’s stated need to reshape skills for artificial intelligence aligns with the union’s claim that workers were made redundant without proper consultation.
Atlassian and Mike Cannon-Brookes: scale, rationale and support measures
Atlassian confirmed it is cutting about 10% of its workforce, roughly 1, 600 positions, as part of a restructure intended to invest more in artificial intelligence and enterprise sales. it will replace its chief technology officer and noted that more than 900 of the affected roles were in software research and development. The firm employed 13, 813 full-time staff in June 2025, and the announced geographic distribution included about 640 affected employees in North America, 480 in Australia and 250 in India. Co-founder Mike Cannon-Brookes wrote that the move was “the right decision for Atlassian” while acknowledging the human cost and adding that “Our approach is not ‘AI replaces people’. “
Professionals Australia and Paul Inglis: consultation, timelines and worker claims
Professionals Australia said impacted employees were told on Thursday and that a consultation process would run until 19 March ET, with final termination expected on 2 April ET. Paul Inglis, a director at Professionals Australia, said workers had been made redundant without being consulted or given any sign a restructure would affect their jobs, and he argued that experienced professionals deserved “respect, transparency and proper consultation. ” The union requested an urgent meeting to discuss Atlassian’s introduction of AI technology and its direct connection to the redundancies, and hundreds of Australian workers had joined the union to seek a say in how AI is used at work.
Atlassian Layoffs 1600 Jobs Australia: where company statements and union claims align and diverge
On scale and allocation, both sides acknowledge the basics: about 1, 600 roles will go, with 480 of those positions in Australia and more than 900 tied to research and development. On the question of motive, Atlassian frames the cuts as a strategic shift to change the mix of skills needed for AI and to “self-fund further investment in AI and enterprise sales, ” while Professionals Australia frames the same change as directly connected to redundancies and as lacking adequate prior consultation. On employee support, Atlassian set out minimum separation terms that include 16 weeks’ pay, extended healthcare plans, early pro rata bonuses and a US$1, 000 technology payment after equipment return; the union’s critique focuses on process and notice rather than the level of the severance package.
Analysis: Applying the same evaluative criteria— factual accounting of scale, explanation for the cuts, and procedural fairness—shows partial agreement and clear divergence. Both sides agree on scale. Where they diverge is explanation and process: the company emphasizes strategic necessity for AI investment, while the union emphasizes that the manner and timing of employee notification fell short of proper consultation.
That divergence is illustrated by concrete timeline details. Employees were told on Thursday; a consultation window was set to run until 19 March ET with final terminations expected on 2 April ET. Cannon-Brookes acknowledged the impact on staff and extended a brief operational concession by leaving internal chat functions open six hours longer than usual for farewells. Professionals Australia says the redundancies came without prior consultation, and it has sought urgent talks about the link between AI introduction and job losses.
Finding: The comparison establishes that Atlassian’s strategic rationale explains why the company prioritized cuts and refocusing toward AI, while Professionals Australia’s account better explains the immediate shortcomings in consultation and worker notice. Analysis: the public facts—numbers of roles affected, the specific R& D impact, the geographic breakdown and the formal consultation timetable—support both elements of that dual conclusion.
The next confirmed milestone to test this finding is the end of the consultation period on 19 March ET and the final termination date on 2 April ET. If Atlassian maintains the stated separation packages and follows the consultation timetable through 2 April ET, the comparison suggests the company will have completed its strategic pivot while still facing scrutiny over whether consultation met workers’ expectations.
