News

GitLab cuts 350 jobs as AI agents reshape engineering teams

GitLab laid off 350 employees, about 14 percent of its workforce, and exited 22 countries as part of a restructuring it announced alongside first-quarter results on June 3. The DevOps platform company also flattened management layers, according to TechCrunch's reporting, and expects to take $30 million to $35 million in restructuring charges.

The cuts landed in the same week the company posted growth. Revenue rose 23 percent year over year to $264 million for the quarter, with gross margins of 88 percent, figures confirmed in GitLab's Q1 fiscal 2027 results and restructuring filing. This is not a company in distress trimming to survive. It is a profitable, expanding software business reorganizing on purpose.

CEO Bill Staples tied the move directly to artificial intelligence. "Agents work at machine scale, and they're pushing competitors to the brink," he said, adding that the quarter marked the start of a "generational rebuild" of git to support what he described as 100x growth, according to TechCrunch's reporting. In other words, the headcount coming out is paired with infrastructure investment going in. GitLab is shifting people and money toward serving automated, agent-driven developer workflows rather than scaling the old way.

That framing matters because it breaks the usual story. For most of the past two years, tech layoffs read as a correction after over-hiring or as a response to falling demand. GitLab's announcement is something different: a growing company with strong margins choosing to restructure around how AI agents now consume engineering infrastructure. Exiting 22 countries and flattening management suggests the reorganization is structural, not seasonal.

What this means for job seekers

For software, platform and DevOps engineers, the lesson is uncomfortable but useful. A layoff at a profitable, 23-percent-growth company tells you that headcount cuts are no longer a reliable signal of a company in trouble. Reviewing how this round was framed, the displaced roles appear to be the ones a leaner, agent-oriented org chart no longer needs, while investment flows toward infrastructure built for machine-scale automation. Job security in 2026 is tracking less with employer health and more with whether your skills sit on the side of that shift the company is funding.

The skills that look durable cluster around the new workload. Agent orchestration, API design for automated systems, and AI governance — the discipline of keeping machine-scale tooling safe and auditable — are the capabilities companies are building out, not cutting. Engineers who can show they have moved up the stack from writing code by hand toward designing and supervising the systems that generate and deploy it are positioning for the roles that survive these reorganizations. If you are mapping your next move, our guide to the best remote software engineering jobs in 2026 and our walkthrough of how to job search in the AI era both lean into where hiring is actually concentrating.

The practical takeaway: do not read a strong earnings report as a guarantee your team is safe, and do not read a layoff as proof a company is failing. Both can be true at once. The engineers who treat this period as a prompt to retool — toward orchestration, automation design and governance — will have an easier time than those waiting for the old hiring patterns to return.