Skip to content
TrustList
Business news

Snyk’s accounts show it cut about 203 jobs, about a fifth of its staff: what customers of the security vendor should check

Editorial

By TrustList Editorial

A UK Companies House filing by Snyk, the developer-security vendor, states a reduction in force of about 203 employees, about 20% of its global workforce, more than double the earlier press figure. What customers should ask their account team.

About Snyk’s accounts show it cut about 203 jobs, about a fifth of its staff: what customers of the security vendor should check

Snyk’s accounts show it cut about 203 jobs, about a fifth of its staff: what customers of the security vendor should check

2 October 2026 — Snyk, whose tools scan code, open-source dependencies, containers and infrastructure configuration for security flaws, cut considerably more jobs this year than was first reported. Tech.eu reported on 1 October 2026 that Snyk's latest UK accounts, filed at Companies House, state that it "announced a reduction in force involving approximately 203 employees, representing approximately 20 per cent of the group's total current global workforce". Press reports in June had put the cuts at about 90.

Not yet independently verified. This rests on Tech.eu’s report of the filing; we did not open the filing itself, and Snyk has made no statement that we read. Tech.eu reports that the cuts fell mainly on staff in the United States and Israel. We will update this when it can be confirmed, and remove this note.

What the filing shows

According to Tech.eu, quoting the accounts:

  • About 203 roles, roughly 20% of the global workforce, were cut.
  • The company had about 990 employees at the end of 2025.
  • The cost of the reduction was put at up to $13.8 million.

This is our weekly round-up's kind of story told late: the cut happened in June, but its real size only became public through the accounts. Our Friday round-up covers this week's US notices.

Why customers should care

Developer-security tools sit in the build pipeline of thousands of companies: when they slow down, so do releases. A cut of a fifth of the staff reaches support, customer success and the research teams that maintain vulnerability databases and scanning rules, which is where customers notice it first, as slower responses, fewer new rules or features that stop moving.

What to check with the vendor

  • Named contacts: is your account manager and customer-success contact unchanged?
  • Support terms: are response times and the support region in your contract still met?
  • Roadmap commitments: features or integrations promised during a purchase or renewal should be confirmed again in writing.
  • Coverage: ask how vulnerability research and rule updates are staffed for the languages and ecosystems you depend on.
  • Renewal: if renewal falls in the next two quarters, use it to ask these questions with leverage.

Sources

Categories & features