Verified company layoff record

Crunchbase layoffs

Every confirmed reduction signal we track for Crunchbase—separated from our candidate-focused interpretation and connected to the company’s wider outlook.

Current work outlook32/100CautionOpen full company profile ↗
1verified reduction report
1market represented
Nov 19, 2026latest tracked event
1total company signals

Verified timeline

What happened at Crunchbase

Ordered by the date reported by the source—not by when Flags added the analysis.

01
United StatesHigh confidence

Crunchbase WARN notice schedules 67 San Francisco layoffs

Confirmed reporting

A California WARN record published on November 18 lists 67 permanent layoffs at Crunchbase in San Francisco County, with separations scheduled for January 17, 2027. The entry provides the required 60-day interval between the notice and the planned employment action. The data is reproduced from the public WARN report maintained by California's Employment Development Department. The filing establishes the planned number, location, permanent status and effective date, but it does not explain Crunchbase's business rationale or identify the affected job titles in the public summary. Crunchbase had not provided a detailed public announcement linked to the record at the time of review. A WARN filing is advance notice of a planned action and can later be amended or withdrawn, so the 67-person figure should be understood as the employer's filed plan rather than proof that every separation has already occurred. No severance terms, internal-transfer options, remaining headcount or implications for particular products were disclosed in the available record.

Candidate interpretation

For Crunchbase employees, the filing creates a clear timetable: the planned San Francisco layoffs are scheduled to take effect on January 17, 2027, rather than immediately. That notice period may provide time to clarify eligibility for severance, benefits continuation, internal openings and state rapid-response services. Because the public entry does not list functions, candidates cannot determine whether data engineering, software development, sales, research or corporate teams are affected. Anyone interviewing should ask whether the role is inside the San Francisco employment site covered by the notice, whether the requisition was approved after November 18 and how the organization will change once 67 positions leave. Existing employees should request the company-issued WARN notice and role-specific information rather than relying only on the public aggregate. The filing is a strong, official risk signal, but it does not establish a companywide shutdown or layoffs outside the named location. Until Crunchbase publishes further context, product-roadmap and workload implications remain interpretation rather than confirmed fact.