Crunchbase's WARN Notice Is a Sourcing Brief. 12 of 20 Hits Are Couchbase
Crunchbase's California WARN notice lists 67 San Francisco roles ending Jan 17. How to read it as a sourcing brief and find the builders, not the tool users.
Crunchbase's California WARN notice covers 67 jobs at its San Francisco headquarters with a last day of Jan 17, 2027, and the press coverage named the roles, so recruiters effectively got a free hiring brief. The trouble starts when you search for these people: most profiles that mention "Crunchbase" belong to people who use the product, and a surprising share belong to a different company altogether.
What the Crunchbase WARN notice tells a recruiter
Crunchbase's WARN notice tells a recruiter who is leaving, roughly what they do, and the date they become available: Jan 17, 2027. According to the SF Chronicle, the 67 cuts include the vice president of finance, several senior engineering positions, a senior sales manager, senior data analysts and a senior content marketing manager, all at the Market Street office.
The scale matters as much as the titles. One company profile puts Crunchbase at about 260 employees, and third-party estimates range from 183 to 245. So the cut is somewhere between a quarter and well over a third of the company:
| Headcount estimate | 67 cuts as a share |
|---|---|
| 260 | about 26% |
| 245 | about 27% |
| 183 | about 37% |
This is also the second time. In July 2023 Crunchbase filed for 63 permanent layoffs at 564 Market St., effective Sept 4, 2023. Across the two filings that comes to 130 San Francisco roles. A company that has cut this deep twice has lost a lot of institutional knowledge, and that knowledge is now on the market.
Why California WARN notices list job titles
California WARN notices list job titles because the law requires it. The federal WARN rules require "the job titles of positions to be affected, and the number of affected employees in each job classification," and California's EDD says written notices must include job titles and the number affected per title.
WARN notice sourcing means reading those legally required filings as hiring briefs: who is leaving, in which roles, and when.
One caveat before you build a process around it. The EDD's public summary log shows counts, not the title breakdown. The titles live in the notice itself, and in the Crunchbase case they reached the public through the Chronicle's coverage. So California WARN notice job titles are always required, but they are not always one click away.
Where to watch for the next one:
- CA EDD WARN log: the official source, with counts but not titles.
- Trackers that republish it: jsilvermanlaw.com and layoffiq.com.
- Local tech press: the SF Chronicle is where the Crunchbase title list surfaced.
Why the 60-day window is the whole game
The 60 days between a WARN notice and the last day are when affected employees are still paid, open to calls, and not yet flooded by other recruiters. For Crunchbase that gap is exactly 60 days, from Nov 18, 2026 to Jan 17, 2027, close to the statewide median of 61 days across every notice on file.
Here is why it works. During the notice period, people are still at their desks and usually haven't updated their profiles, flagged themselves as open to work, or posted the "I was impacted" message that sets off a wave of recruiter messages. A specific message in late November reaches someone who has time to think and is still weighing options.
After Jan 17 the window closes fast, and these people are competing with everyone else on the list. In San Francisco County, 49 employers have WARN notices on file, covering 6,220 workers. Intel filed for 57 Santa Clara County cuts the same week as Crunchbase. A senior engineer who leaves in January lands in a crowded pool. The same engineer reached in November is a private conversation.
The keyword trap: most "Crunchbase" engineers work at Couchbase
A text search for "Crunchbase" plus engineering titles mostly returns people who have never worked there. In Refolk's index of US professional profiles, 20 have "Crunchbase" in the headline alongside an engineering or data title. Twelve of those 20 work at Couchbase. Four work at American Express. Only 2 work at Crunchbase.
The cause is mundane. Couchbase and Crunchbase are one letter apart, and Couchbase employs a lot of Senior Software Engineers. Fifteen of the 20 matches carry exactly that title. Any search that tolerates small spelling differences will pull Couchbase people into a Crunchbase search. If your sequencing tool auto-enrolls whatever comes back, most of your outreach goes to people who were never laid off and will be confused by your "sorry to hear about the layoffs" opener.
The fix is structural. Filter on current or former employer as a structured field, not on text anywhere in the profile.
Why the tool-user pool is the wrong pool
Most people who list Crunchbase on their profile use it to prospect. They didn't build it. In Refolk's index, 225 US profiles list "Crunchbase" as a skill, and the top titles are Account Executive, Revenue Operations Lead, Director of FP&A and Investor. Of 25 sampled, only 2 currently work at Crunchbase.
| Pool (US, Refolk's index) | Total | Actually at Crunchbase | Main noise or skew |
|---|---|---|---|
| "Crunchbase" listed as a skill | 225 | 2 of 25 sampled (8%) | Sales, RevOps, finance users |
| Headline "Crunchbase" + eng/data title | 20 | 2 of 20 (10%) | 12 of 20 at Couchbase (60%) |
| "Entity Resolution" skill | 214 | 0 in top employers | Senior data leaders, 1 of 25 in Bay Area |
| WARN notice (CA EDD) | 67 roles | 67 | n/a |
That's what goes wrong when you treat a product name as a skill. Crunchbase is a tool sellers and investors use to prospect, so it shows up in their skills sections. The 67 people in the notice are a different population, and a skill search can't find them because builders rarely list their own employer's product as a skill.
This is where plain keyword search breaks down and a described search helps. With Refolk you describe the person ("worked at Crunchbase, engineering or data role, San Francisco") and get back people matched on employment history, rather than on a word that happens to appear in a skills list.
How to tell a Crunchbase builder from a Crunchbase user
A Crunchbase builder has Crunchbase in their work history in a technical or data role. A user has it in their skills or summary next to a quota or a portfolio. Once you know which signals to check, telling them apart takes seconds.
Signals that point to a builder:
- Employer field, not skills field. Crunchbase appears as a past or current employer, with dates.
- Title matches the WARN list. Senior engineering, senior data analyst, or the finance, sales and marketing roles the Chronicle named.
- Data-pipeline skills. Entity resolution, record linkage, deduplication, ingestion, ETL. Entity resolution is the work of deciding whether two records describe the same company or person, a central problem in any company database.
- San Francisco location. The notice covers the HQ, so Bay Area profiles are your first pass.
- Code or writing trails. Public repos, talks or posts about company-data matching, crawling or data quality.
Signals that point to a user:
- Crunchbase sits next to other prospecting and research tools in a skills list.
- The title is Account Executive, Revenue Operations, FP&A, or investor.
- The current employer is anyone other than Crunchbase (or is Couchbase).
Builders rarely list their own employer's product as a skill. The people selling with it do.
Entity resolution talent is scarce, and data vendors will bid
People who can do entity resolution at production scale are rare, senior, and mostly outside the Bay Area. In Refolk's index, only 214 US profiles list "Entity Resolution" as a skill. The top employers are Senzing, 6sense, Recorded Future and NVIDIA, and the titles skew toward Head of Data, VP Data and AI, and CTO.
That's why the Crunchbase notice stands out. A batch of San Francisco engineers who spent years matching messy company records is unusual, and the obvious competing buyers are B2B data companies like Senzing and 6sense that already employ much of this talent. If you hire for a data product, a fraud team, or a go-to-market data platform, you know how thin this search usually is: a handful of profiles, most of them in the wrong city or too senior to move.
A Crunchbase engineer may not list "entity resolution" anywhere, though. Some will describe the work in product terms, like "company profiles," "funding data" or "data quality." Search on the work as well as the label: engineers who built company-data matching or deduplication pipelines, not only people who typed the term of art.
Who probably got cut, and what to ask them
The Crunchbase cuts may follow the company's 2025 pivot, so ask candidates which system they maintained instead of assuming. To be clear, this is an inference. The notice lists titles, not teams.
The background: in February 2025 Crunchbase relaunched as an AI predictions engine. CEO Jager McConnell said "the historical data industry as we know it is dead." Megh Gautam, the Chief Product Officer, was named alongside the relaunch, and Forbes wrote that the pivot "involved tough moments, layoffs, skepticism, and big existential questions." The predictions draw on data users never see, such as when company profiles are edited, who edits them and what they change.
If historical data is the part the CEO called dead, and this is the second SF cut in roughly three years, engineers on legacy ingestion and profile-curation pipelines may have been more exposed than those on the predictions team. Either group is valuable, but for different hires.
Questions that sort them quickly:
- Which pipeline did you own: ingestion, matching, profile curation, or predictions?
- How did you resolve duplicate companies across sources, and at what volume?
- Did you work with profile-edit and contributor-activity signals?
- What did the 2025 relaunch change about your day-to-day?
A 60-day outreach plan for the Crunchbase layoffs
For the Crunchbase layoffs, build the list in the first week, reach out in the second, and have offers moving before Jan 17. Here is how that maps onto the calendar:
- Week of Nov 18: build the list. Pull everyone with Crunchbase as a current employer in San Francisco, then cut out Couchbase and the skills-only matches. Map each person to a WARN title.
- Late November: first message. Keep it short and specific. Name the system they likely worked on and the problem your team has. Don't open with condolences: most of the company is not on the list.
- Early December: technical conversation. Bring in a hiring manager who knows data pipelines. Use the questions above.
- Mid-December: move fast. Holiday slowdowns stretch out every process. A candidate with an offer before the break won't be looking in January.
- Before Jan 17: close. After the last day, they join the pool of 6,220 SF County workers on WARN notices, and your head start is gone.
That is the whole method for recruiting laid-off engineers from a WARN notice: reach them while they are still on payroll, separate the builders from the noise, and get a real offer in front of them before the last day.
FAQ
Are job titles always included in a California WARN notice?
Yes, they are required. Federal WARN rules and California's EDD both require written notices to list affected job titles and the number of employees in each. But the EDD's public summary log shows only counts, so the title breakdown has to come from the notice itself or from press coverage. For Crunchbase, the list surfaced through the SF Chronicle.
Why does searching "Crunchbase" return so many wrong people?
Two reasons. Most profiles that mention Crunchbase belong to salespeople, RevOps staff and investors who use it as a tool: 225 US profiles list it as a skill in Refolk's index, and only 2 of 25 sampled work there. And among engineering headline matches, 12 of 20 work at Couchbase, a company whose name is one letter away. Filter on employer history, not keywords.
When should I contact people named in a WARN notice?
Contact them during the notice period, not after it. Crunchbase's window runs 60 days, from Nov 18, 2026 to Jan 17, 2027. Before the last day, candidates are still on payroll and hearing from far fewer recruiters. After it, they're competing with the 6,220 workers on WARN notices in San Francisco County alone.
The data behind this
Try it on the search you came here for
Stop building boolean strings. Just describe the person.
Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.
01Describe them
One plain sentence. Role, city, stack, stage, whatever matters to you.
02I read the web live
GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.
03You read the shortlist
Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.
- Staff backend engineers in NYC who shipped Rust in production
- Series A fintechs in SF under 50 people, growing headcount this year
- Maintainers of fast-growing Rust web frameworks on GitHub
- No boolean, no filters, no seat to buy. One box.
- Read at search time, so a profile updated yesterday counts today.
- Every step visible as it runs, every name with its reason.
500 free credits on sign-up. No card, no demo call. See real searches.