1APR

GitLab rewrites engineering around AI agents

4 min read

12:41UTC

GitLab CEO Bill Staples published 'GitLab Act 2' on 11 May 2026, cutting the company's country footprint by up to 30% and breaking R&D into approximately 60 smaller teams on the explicit premise that AI agents will plan, code, review, deploy, and repair software.

← Back to Trump declares victory and withdrawal Jump to analysis ↓

ConflictDeveloping

Key takeaway

GitLab's Act 2 makes the CEO-signed case that AI agents replace engineering co-ordination, dissolving the management layer that connected them.

GitLab CEO Bill Staples published "GitLab Act 2" on Monday 11 May 2026, announcing a restructuring that cuts the company's country footprint by up to 30%, removes up to three management layers from some functions, and breaks R&D into approximately 60 smaller Teams, nearly doubling the number of independent Teams. The explicit justification in Staples's own words: "Software will be built by machines, directed by people. Agents will plan, code, review, deploy, and repair."

The 60-team structure concentrates individual-contributor output while stripping out the managers who previously co-ordinated across functions. In practice, individual engineers report into smaller pods with no manager between them and the AI tools they use to build product. A voluntary separation window closes 18 May; full restructuring completes by 1 June 2026. Financial impact lands on the 2 June earnings call, making it the first public headcount figure for the new structure.

GitLab did not arrive at this thesis alone. Salesforce CEO Marc Benioff applied the same structural argument to customer support: AI agents replaced roughly half the team, and no new engineers were hired in its fiscal year ending January 2026. Meta applied it to engineering titles in April, replacing conventional engineering roles with AI-native designations. GitLab has now applied the thesis to engineering structure itself: not which roles exist, but how many engineers it takes to ship product. That progression from support functions to engineering titles to engineering organisation is what makes the May cluster a pattern rather than separate decisions by unrelated companies.

The voluntary separation window that closes 18 May avoids the immediate WARN Act filing that a simultaneous termination event would trigger. GitLab operates across dozens of countries with no single US site large enough to meet the WARN threshold in any single jurisdiction. Both structural facts sit alongside the public manifesto, which is arguably the most candid CEO-signed statement on AI displacement to appear from a major DevOps company in 2026.

Deep Analysis

In plain English

GitLab makes software that other software companies use to build their products. Think of it as the tool companies use to organise engineers, review code, and push updates. On 11 May 2026, GitLab's chief executive published a document saying the company itself would restructure around the assumption that AI would do most of the engineering work going forward. His argument: AI agents can now plan what to build, write the code, check it, push it to production, and fix problems. Humans direct the process rather than perform it. So GitLab is cutting the number of countries it employs engineers in, removing manager layers, and splitting its engineering organisation into roughly 60 small, autonomous Teams. Why this matters beyond GitLab: GitLab is not a frontier AI lab predicting the future. It is a practical software tools company declaring that the future is already here in its own operations. When the company that makes the tools other engineers use restructures itself around AI-built software, it is saying something about where the whole software industry is heading.

Deep Analysis

Root Causes

GitLab's restructuring has two structural drivers that the fact does not name.

First, the GitLab product roadmap and the GitLab engineering structure have converged onto the same thesis. GitLab sells DevOps tooling including CI/CD pipelines, code review, and deployment orchestration. Its Act 2 document argues that AI agents will perform these functions.

If that thesis is correct for GitLab's customers, it must also be correct for GitLab's own engineering. The restructuring is therefore not a cost response to a revenue miss; it is the company applying its own product roadmap to itself.

Second, capital market pressure from the Harvard Business Review finding that only 2% of organisations announcing AI-related cuts have implemented AI that actually accounts for them creates a verification problem for companies that claim AI productivity gains.

GitLab, as a software tool company, has unusually direct access to internal metrics that can demonstrate AI productivity gains to investors. The 2 June earnings call is the first public test of whether those metrics materialise as disclosed.

What could happen next?

Precedent
GitLab's 60-team R&D structure becomes the reference architecture investors ask other mid-cap DevOps companies to justify not adopting.
Short term · 0.75
Consequence
The 2 June earnings call is the first public test of whether declared AI productivity gains translate to financial disclosure; a miss would undermine the entire CEO manifesto genre.
Immediate · 0.8
Risk
Removing co-ordination layers without a proven AI substitute creates integration risk that surfaces only after the voluntary separation window closes 18 May.
Short term · 0.7

Source Landscape

This story draws on neutral-leaning sources

Primary parallel: AT&T's 1996 restructuring into Lucent Technologies, NCR, and the rump AT&T broke a single 300,000-person engineering organisation into smaller, faster-moving units on the thesis that the internet era required a different operating model than the voice telephony era.

The structural logic was identical: concentrated individual-contributor output, fewer co-ordination layers, independent Teams. The results split: Lucent thrived in its first four years before losing $54 billion in the 2001-2002 correction; NCR returned to independence but never recovered its pre-split scale.

Counter-parallel: Amazon's own two-pizza team doctrine, which Upwork CEO Hayden Brown declared dead in the same fortnight, was also a structural response to a technology transition: Jeff Bezos introduced it in 2002 on the thesis that small Teams with full ownership produced better internet-era software than large integrated ones.

Amazon's team-sizing rule held for 22 years before an AI-era CEO publicly declared it obsolete. GitLab's 60-team architecture may be accelerating toward the same revision cycle, only faster.

GitLab has not disclosed the headcount number or financial cost of Act 2. The 30% country footprint reduction and three management layer removal are structural metrics, not salary figures. The earnings call on 2 June 2026 is the first point at which quarterly financial disclosure will produce a headcount number.

The economic read that is available before that disclosure: the 60-team structure, if it holds, means GitLab is restructuring its cost base around individual-contributor salaries (the Teams) and AI tool licences (the substrate) rather than management-layer salaries and co-ordination costs.

At $70,000-$120,000 average US engineering management compensation, removing three management layers from a company with 8,000 employees represents a structural labour cost reduction independent of any headcount cut. The voluntary separation window closing 18 May is the cleaner financial signal: how many senior engineers accept departure versus stay determines whether Act 2 is a genuine capability redesign or a managed departure.

Consensus view: Gartner Research Vice President Philip Walsh assessed in April 2026 that the 'AI-native pod' architecture GitLab describes reduces co-ordination overhead by removing manager layers, but only functions when the underlying AI toolchain is reliable enough to replace planning conversations. GitLab's own product is the toolchain in question, making it simultaneously the hypothesis and the test subject.

Counter-view: Boston Consulting Group's Henderson Institute argues that the two-to-three management layer removal targets precisely the function that keeps AI tool output coherent across Teams: the mid-level engineering manager who integrates AI output from multiple contributors, catches hallucinations, and manages scope. Removing that layer without a substitute mechanism transfers integration risk to individual contributors who have no organisational authority to resolve conflicts.

Key tension: Whether the 60-team R&D structure produces faster software delivery or fragmented output depends entirely on whether AI agents can replace the co-ordination function that the removed management layers previously performed, a capability no published benchmark yet measures at production scale.

Sources:GitLab (Bill Staples, CEO)

Mentions:GitLab →Bill Staples →Gartner →Boston →Marc Benioff →Meta →Amazon →Upwork →Hayden Brown →Salesforce →WARN Act →Harvard Business Review →Boston Consulting Group →

First Reported In

Update #9 · GitLab signs the manifesto, Brussels backs out

GitLab (Bill Staples, CEO)· 15 May 2026

Read original →

Causes and effects

Caused by

Salesforce halves support staff using AI

Salesforce's AI agent customer support replacement established the same structural thesis GitLab now applies to engineering itself

Occurred 29 Mar 2026

Read story →

Meta codes its own org chart

Meta's engineering title replacement with AI-native roles in April preceded GitLab applying the thesis to engineering structure itself

Occurred 19 Apr 2026

Read story →

This Event

GitLab rewrites engineering around AI agents

GitLab's restructuring applies the AI-replacement thesis directly to engineering structure, rather than headcount alone, making it the most operationally specific CEO manifesto in the 2026 tech restructuring cycle.

Different Perspectives

Wang Yi

China's foreign minister and Djibouti's issued a joint communique on 21 October saying the war should not reach the Horn of Africa and stressing free navigation through Bab al-Mandeb. The text names neither Iran nor the Houthis, and Djibouti hosts China's only overseas military base, opposite the Yemeni coast.

Ministry of External Affairs

India's foreign ministry called the attacks on Saudi civilian and energy sites "unacceptable" on 22 October and said they must stop at once. An Indian died at Dammam, Indians were injured there and at Shaybah, and about 4,000 Umrah pilgrims remain stranded by one MP's count.

Iraq

Iraq closed the al-Sheeb crossing with Iran to travellers and trucks from 21 October and said other crossings would close gradually. Unlike September's closure, which ended on a staged timetable, this one has none, and Iran's interior ministry said it received no notice.

Abdel Fattah el-Sisi

Egypt's president said on 21 October that Cairo's support would "defend Saudi territory, and does not include an attack on Yemen". Araghchi warned that Egyptian involvement would further complicate the situation, and Cairo's limit matches the one Ankara set on 8 October against attacking another state's soil.

UK Ministry of Defence

The MoD said on 20 October that RAF Typhoons over Saudi Arabia will not strike the Houthis, but extended tanker support to Saudi operations including against Houthi targets in Yemen. The tanker line sets no limit on strikes, so British aircraft may now refuel Saudi jets on bombing runs.

Turkey

Ankara sent the Mecca Joint Defence Agreement to parliament around 20 October, and its published text treats an attack on one party as an attack on all. Article 16 brings it into force only on the last ratification, so the 5 October invocation in Riyadh could not yet bind Turkey.

Written with AI from Lowdown's published reporting. Not individually reviewed by an editor. Editorial standards.