The Layoff Club

Laid off from GitHub.

GitHub cut 10% of the company in 2023, about 300 people, closed every office, and eliminated its entire India engineering team, all while Copilot became the product the parent reorganized around. A Microsoft subsidiary with its own layoff record.

At a glance

What's known about GitHub severance and layoffs

  • About 300 roles, 10% · February 2023 reduction
  • Eliminated, 142 roles · India engineering team, March 2023
  • All closed, fully remote since 2023 · Offices
  • Zero · US WARN filings, our tracker, all-time

Recent GitHub layoffs

Quiet since the 2023 restructuring

GitHub's defining round was February 2023, 10% of staff, roughly 300 roles, alongside a move to fully remote operations, followed by the elimination of its 142-person India engineering team. It hasn't appeared in US WARN data since, and Microsoft's subsequent rounds report under the parent's name.

Previous rounds

GitHub layoff history

GitHub's 2023 restructuring traded geography for concentration, 10% of the company and every office, including an entire national engineering organization, while Copilot became the strategic center. Since then its workforce moves inside Microsoft's broader cycles without separate disclosure, and its fully remote structure means even large cuts would spread below per-state notice thresholds.

The subsidiary boundary here is softer than LinkedIn's. GitHub runs its own brand and leveling but its cuts since 2023 have surfaced, when they surface at all, inside Microsoft's announced rounds, so both pages matter to a GitHub employee, this one for the unit's own history, the Microsoft page for the cycles that now carry it.

If you're affected at GitHub, your state is wherever you sit, fully remote means your unemployment filing, notice rights, and final-pay rules all follow your home state, and our state pages carry each one. Developer-platform experience remains among the most transferable in software, and the review windows on any agreement apply regardless of how quietly the cut arrived.

Previous GitHub layoff rounds

How GitHub has compared

A fully remote subsidiary is nearly invisible in layoff data, no offices means no site crosses a WARN threshold anywhere. GitHub's zero-filing record measures structure rather than job security, because a distributed workforce simply never appears in state records. It's the purest example of that blind spot we track.

GitHub layoff and severance questions

What severance does GitHub pay in layoffs?

GitHub hasn't published severance terms for the 2023 round or since. As a Microsoft subsidiary its packages follow the parent's system, individually issued. Yours is the only version that counts.

Why doesn't GitHub appear in WARN databases?

It's fully remote with no offices since 2023, so no single site ever crosses a state notice threshold. Zero filings in our tracker measures structure, not job security, and it's the clearest example of the remote-workforce blind spot in official layoff data.

Are GitHub layoffs part of Microsoft's layoffs?

Since 2023, effectively yes, GitHub cuts surface inside Microsoft's announced rounds without separate counts. The 2023 restructuring was GitHub's own. This page holds the unit's history; our Microsoft page tracks the parent's cycles.

Where do I file for unemployment after being laid off from GitHub?

In the state where you worked, not where the company is headquartered. GitHub's biggest U.S. hubs are California, Washington, Texas. Severance usually doesn't block you from filing, and benefits run from your filing date, so file the same week.

Should I sign the severance agreement right away?

First pin down how much review time you actually have. If you're 40 or older, federal law gives you 21 days to consider an agreement that waives age claims, 45 in a group layoff, and a waiver signed under a shorter deadline can be invalid. If you're under 40, no federal window applies and the deadline in your packet may be real, so confirm it in writing and ask for more time if you need it. Use whatever window you have to read the release terms, especially non-disparagement and no-lawsuit clauses, and don't stall past a real deadline, because offers can be withdrawn.

Can I collect unemployment if I got severance from GitHub?

Usually yes, though some states delay benefits until severance pay periods end, and lump sums are treated differently than salary continuation. Check your state's rules on our state benefit pages, and file immediately either way so your claim date is locked in.

What to do after being laid off from GitHub

  1. File for unemployment in the state where you worked. Benefits run from your filing date, and severance usually doesn't block you. GitHub's biggest hubs: California, Washington, Texas. Somewhere else? Every state is here.
  2. Find out in writing how long you have to review the severance agreement. At 40 or older, federal law guarantees 21 days, 45 in group layoffs. Under 40, the packet's deadline may be real, so ask for time rather than assume. Read our severance breakdown first. The clauses matter more than the number.
  3. Mind the health insurance window. Losing coverage opens a 60-day special enrollment period, and an ACA plan usually beats unsubsidized COBRA. Compare your options before the employer coverage lapses.
  4. Get your real runway number. Severance plus savings divided by reality. The calculator takes five minutes.
  5. Know which clocks are already running. Severance review windows, COBRA election, visa grace periods, and 401(k) rollovers all run on federal deadlines that started at termination. All five deadlines are here.