GitLab Cuts 14% of Staff in AI Pivot Despite Record 264 Million Revenue

GitLab is eliminating 350 roles — approximately 14% of its global workforce — and exiting operations in 22 countries, a restructuring that TechCrunch reported on June 3 is expected to cost between $30 million and $35 million in one‑time charges. The cuts were detailed in an SEC filing dated June 1 and are part of a plan to be "substantially complete" by the end of fiscal 2027.

The striking part: GitLab is not in trouble. Its Q1 FY2027 revenue hit $264.2 million, up 23% year‑over‑year, with gross margins of 88% and non‑GAAP net income of $39 million. As Metaintro noted, "When a business growing 23 percent a year still trims 14 percent of its staff, the message to tech workers is that financial health and job security are no longer the same thing."

CEO Bill Staples framed the restructuring around what he calls the "agentic era" — a world where AI agents, not just human developers, are pushing code through pipelines at machine scale. In prepared remarks for the earnings call,,¹ Staples said: "Agents work at machine scale, and they're pushing competitors to the brink. This quarter we began a generational rebuild of git to support the scale and features required for 100x growth. This is a scale requirement that didn't exist before and has become a real pain point for every team on their agentic journey."

Staples also noted that GitHub has struggled with AI‑powered submissions affecting uptime — signaling that this is not a GitLab‑specific problem but a structural challenge for every platform that manages code. Agentic AI is stressing infrastructure in ways original architectures were never designed to handle.

The restructuring involves more than headcount reductions. GitLab is exiting 22 countries, reducing its geographic footprint by roughly 37%, and flattening management layers. As ² detailed, the most exposed roles are international sales, support, and operations in smaller markets, along with routine engineering and QA positions that AI can increasingly handle.

Where is the money going? According to TechCrunch, GitLab is partnering with an unspecified AI lab to rebuild its infrastructure. The investments target three specific areas:

GitLab's cuts are not happening in isolation. TechCrunch noted that the tech industry has already cut more than 100,000 jobs in 2026, on track to outpace both 2024 and 2025. The list is long: Intuit cut 3,000, Amazon cut 16,000, Block halved its workforce at 4,000, Cisco cut roughly 4,000, Cloudflare eliminated 1,100 roles that AI made obsolete, and Microsoft offered buyouts to up to 7% of its U.S. employees.

The common thread, ² pointed to an emerging pattern: companies report record revenues while simultaneously shrinking headcount, with AI cited as both the reason for growth and the justification for cuts. GitLab fits this pattern precisely — growing 23% year‑over‑year while trimming 14% of staff.

For the broader developer ecosystem, GitLab's pivot carries several signals. First, git itself is being rebuilt. The version control system that underpins virtually all modern software development was not designed for AI agents submitting code at machine speed. Staples' mention of a "generational rebuild of git" is significant — it suggests the infrastructure layer of software development is about to change in ways that affect every developer, regardless of which platform they use.

Second, the reallocation is toward AI‑native features, not away from them. GitLab is not cutting costs to preserve margins — it is redirecting resources toward its Duo Agent Platform, which reached general availability in January 2026 and competes directly with GitHub Copilot. The bet is that fewer people working on the right priorities will beat more people spread across legacy ones.

Third, job security in tech is decoupling from company performance. As ² put it, "The job is not disappearing so much as moving up the stack, toward judgment, architecture, and the ability to direct AI rather than compete with it." For developers, the message is clear: the most stable roles are those that make AI more productive, not those that AI can replace.