Skip to content
Briefings are running a touch slower this week while we rebuild the foundations.See roadmap
AI: Jobs, Power & Money
16APR

GitLab rewrites engineering around AI agents

4 min read
13:29UTC

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 Three federal surveys, one 34-to-1 gapJump to analysis ↓
EconomicDeveloping
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
Sources:GitLab (Bill Staples, CEO)
Mentions:GitLab →Bill Staples →Gartner →Boston →Marc Benioff →Meta →Amazon →Upwork →Hayden Brown →Salesforce →WARN Act →
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
TSMC and Taiwan chip supply chain
TSMC and Taiwan chip supply chain
Nvidia's 17% headcount growth to 42,000 on $81.6 billion in quarterly revenue depends on TSMC's CoWoS advanced packaging capacity constraining H100 and B200 supply, sustaining margins above 70%. The AI build-out's sole headcount-growth story runs through a Taiwan supply chain that has no parallel in downstream software.
Displaced tech workers globally
Displaced tech workers globally
CrowdStrike's SEC disclosure puts AI attribution on a material regulatory record for the first time, but Oracle's Massachusetts WARN clock expired unfiled after up to 14 workers were logged as remote despite office proximity. The legal apparatus cannot enforce what it cannot see: hybrid reclassification, GCC transfers, and hires never made.
UK workforce and policymakers
UK workforce and policymakers
ONS recorded UK vacancies at 705,000, below the pre-pandemic baseline for the first time, as payrolled employment fell 210,000 year on year with real wage growth at 0.1%. The Bank of England's AI worst case assumed 500,000 additional unemployed from a baseline above 730,000; the UK is already below that floor, and ONS still publishes no AI-exposure breakdown.
India IT workforce and graduates
India IT workforce and graduates
NASSCOM's FY2026 data shows net sector growth of 140,000, but entry-level hiring fell 20-25% as the growth concentrated in in-house GCC offices requiring mid-career specialists. Indian graduates who previously entered through TCS, Infosys and Wipro fresher programmes find that channel closing at both ends: outsourcers cutting and GCCs not hiring at the junior level.
IG Metall and European trade unions
IG Metall and European trade unions
European labour bodies see the market reward pattern, cuts on record revenue, as investor preference for short-term margin extraction over validated AI productivity. They note the EU Digital Omnibus provisional deal has dropped binding employer AI-literacy obligations at the precise moment the ILO-NASK index has quantified that 3.3% of global workers are in the highest AI exposure category.
Federal Reserve Board
Federal Reserve Board
Governor Cook told Stanford's SIEPR on 27 May that speculative-grade software bond spreads have widened on AI-disruption concern, moving AI displacement from a labour observation into the Fed's financial-stability mandate. The Fed cannot resolve structural labour transformation through rate policy, so Cook routed the concern through the one channel the Fed does control.