Dropbox's WARN Lists 57 of 200 Cuts. Find the Rest by Byline, Not City

If you plan to hire ex-Dropbox engineers, the California WARN filing most recruiters will pull up lists 57 roles out of about 200 cut on October 28. It shows you roughly a quarter of the people and nothing about where the rest live.

Alkarmi's memo put the cut at 9% of the company, across Engineering, Product, Design and G&A, and the same day Dropbox disclosed that CTO Ali Dasdan would leave on November 18. This piece covers where the other roughly 143 are, how to find them through the systems they built, and when a message will actually land.

Why does Dropbox's WARN notice show only 57 of 200 cuts?

The Dropbox WARN notice for San Francisco covers one building, 50 Hawthorne St, and Dropbox has been "Virtual First" since 2020, so most affected employees were never attached to that site. A WARN notice is a legally required layoff disclosure filed with the state for a specific work location, not for a company's whole workforce.

The filing went to California EDD on October 28 and covers 57 permanent cuts effective November 18. Dropbox kept its HQ address while most of its people moved to home offices across the US, Poland and Canada. The law counts layoffs by site, so a remote engineer in Austin or Warsaw doesn't show up in any San Francisco filing. That's how the law is written, not a mistake in the filing.

Dropbox's 10-K gives the base: 2,113 full-time employees as of December 31, 2025, with 1,612 in the US and 501 outside it.

Here is a labeled assumption, not a reported figure. If the cuts followed headcount (76% US), about 153 would be US-based. That would put roughly 96 US employees outside the San Francisco filing, plus around 47 abroad.

~143

The same week, Front cut 53 jobs in San Francisco, and California WARN filings show nearly 14,500 Bay Area tech cuts so far in 2026. In those totals, Front's 53 and Dropbox's 57 look like similar-sized events. They aren't: Dropbox's real footprint is mostly outside the state.

Where are Dropbox's engineers actually located?

Most of them are outside the Bay Area. In Refolk's index of professional profiles, only 4 of 14 sampled US Dropbox engineers by region were in the Bay Area, and outside the US, Poland had more than Canada.

In Refolk's index, 394 US-based engineering profiles (software engineer, senior, staff, engineering manager) mention Dropbox in their headline. In a sample of 25, 17 still work at Dropbox. The other 8 have moved to Meta (3), Databricks, Apple, Google, Microsoft and Material Security. That list is your competition: those companies have already hired from this pool once.

Here's where the US sample sits by region:

• Bay Area (4 of 14): San Francisco, Sunnyvale, Belmont
• Everywhere else (10 of 14): Seattle, New York, DC-Baltimore, Atlanta, Portland, Dallas, Austin

4 of 14

Outside the US, Refolk's index shows 79 matching engineering profiles across Canada, Poland, Ireland, the UK and Mexico, and 24 of 25 sampled still list Dropbox as their current employer. The country breakdown:

1. Poland: Warsaw, Kraków, Poznań, Gdańsk
2. Canada: Vancouver, Ottawa, Mississauga, Saskatoon
3. Mexico: Monterrey

Why Poland is the pocket nobody is working

Polish leavers are hard to see and few recruiters contact them. Alkarmi's memo says "International packages will reflect local practices," and Poland's statutory notice periods may keep people on payroll for longer. Someone still on payroll usually doesn't update their LinkedIn, so they look employed to anyone filtering for "open to work." A San Francisco WARN search won't surface them at all.

If you can hire in the EU or hire remote contractors there, start with Warsaw and Kraków.

Why does a title search for "Magic Pocket" return nothing?

Dropbox engineers write "Software Engineer at Dropbox" in their headlines, not the name of the system they worked on. In Refolk's index, a search for Rust plus sync, storage or distributed systems among senior US profiles returned zero matches.

Two terms worth defining:

• Magic Pocket is Dropbox's custom block storage system, which holds data at exabyte scale. A small group rewrote its storage engine in Rust while the rest of the team kept writing Go.
• Nucleus is Dropbox's desktop sync engine. It was rewritten in Rust over four years and shipped to all users in March 2020.

If you need Rust sync engine engineers, LinkedIn keyword boxes won't find these people, because the evidence of what they built isn't on LinkedIn.

Where the system-level signal actually lives

Look for the people who wrote about the work, not the people whose title matches:

• dropbox.tech bylines. Sujay Jayakar wrote the Nucleus rewrite post, in which he said "betting on Rust was one of the best decisions we made." A byline on a system post proves real involvement in a way a job title can't.
• Magic Pocket write-ups. James Cowling wrote "Inside the Magic Pocket." Check each author's co-authors and the people they thank.
• GitHub. Look at contributors to Dropbox's public org and to the Rust crates that came out of sync and storage work. Commit history shows who kept a codebase running and who touched it once.
• Conference talks. Storage, Rust and systems conference speaker lists name the engineers Dropbox trusted to present the work.
• Alumni companies. Convex was founded by former Magic Pocket and Nucleus leads. It shows a common path for Dropbox's storage and Rust people: they leave to found startups.

A byline on dropbox.tech is a better hiring signal than any title Dropbox ever printed on a badge.

The catch is that this is slow by hand. You read the engineering blog archive, cross-reference each author's GitHub handle, confirm what country they live in now, and repeat that across five countries. Meta and Databricks have already hired from this pool and won't wait for you to finish.

That joining work (byline to GitHub to current profile) is what Refolk does. You describe the engineer in plain English, for example someone who worked on Dropbox storage in Rust and now lives in Poland, and Refolk searches GitHub, LinkedIn and the open web and returns a ranked shortlist. You don't need the person to have typed "Magic Pocket" into their headline.

Which Dropbox teams should you target first?

Go after engineers from deprioritized products first and Dash engineers last. Dash, Dropbox's AI search product, is where the company is investing now, so people on it are the most likely to have kept their jobs and the hardest to pull away.

This is Dropbox's third cut since 2023:

Together that's about 1,200 roles. Engineers on deprioritized products are the likeliest to have been cut this time, so the October 2026 round probably hit teams outside the AI push hardest. A practical priority order:

1. Engineers on deprioritized product lines. They're the most likely to have been cut and to be job hunting now.
2. Nucleus and Magic Pocket veterans. Some will be in the cut and some won't. Either way, their skills are scarce and easy to verify.
3. Dash engineers. Approach them later, and only with a strong reason to move (see the CTO section below).

When should you reach out to laid-off Dropbox engineers?

Contact visa holders right away. Most others can take their time. Dropbox's severance is 16 weeks of pay starting October 28, which runs to about February 17, 2027, plus one more week for each completed year.

The rest of the package also lowers urgency: Q4 equity vesting, a prorated bonus, six months of COBRA subsidy for US staff, and they keep their laptops. For most people, October 28 was the last day. An engineer with five or more years at Dropbox is paid into March. A cold message saying "urgent, we move fast" means little to someone with four months of salary in the bank. Pitch the work instead.

The dates that matter

• Oct 28: Announcement and last working day for most. WARN filed.
• Nov 5: Q3 earnings. The 8-K says revenue and margin will meet or beat guidance.
• Nov 18: SF WARN cuts take effect. CTO Ali Dasdan leaves.
• Late December: The likely end of the H-1B grace period for affected visa holders.
• ~Feb 17, 2027: Base severance ends for people with the least tenure.

Visa holders are the exception

The standard H-1B grace period is up to 60 days, which puts the deadline around late December for someone whose employment ended October 28. That figure comes from general immigration rules, not from Dropbox's memo, and each person's situation differs, so check with your immigration counsel before you build a timeline on it. Dropbox is offering immigration support, but a new sponsor is still the real fix. If you can sponsor or transfer an H-1B, say so in the first line of your message. Most of their inbox won't.

Why does the CTO's November 18 exit create a second pool?

Engineers who kept their jobs but report up through a technical leadership chain that's about to change are worth approaching between earnings on November 5 and November 18. That's especially true after three rounds of cuts that showed what Dropbox's retention promises are worth.

Dasdan became CTO in March 2025 after coming from Atlassian. His 8-K exit terms include a $515K prorated bonus and a lump sum of about $1.3M. Restructuring costs are $27 to 33M in cash, mostly booked in Q4 2026, and the company is cutting while profitable. That second point is what remaining staff will think about. Cuts made during a good quarter suggest more cuts can come in any quarter.

This group is passive. They aren't looking, they aren't in any filing, and they won't mark themselves open to work. Many of them are the same Nucleus, Magic Pocket and Dash engineers you found through bylines above, just a few weeks later. Build the list now and send messages after November 5.

What should the first message say?

Name the system they built and the specific problem you'd hire them to solve. Leave out urgency unless they have a visa deadline.

A message that gets answered usually includes:

• The system, by name. "Your work on the Magic Pocket storage engine" shows you did the reading. "Your Dropbox experience" doesn't.
• Sponsorship status, first line, for visa holders. Say it plainly.
• Remote policy. These people have worked Virtual First for six years. A message that implies an office move gets dismissed quickly.
• A start date that respects their severance. "Whenever suits you, including after February" is a real advantage when competitors are pushing for this month.
• No layoff sympathy paragraph. One line at most. They've heard it all week.

FAQ

How many people did Dropbox lay off in 2026?

Dropbox announced about 200 cuts on October 28, 2026, roughly 9% of its 2,113 full-time employees, across Engineering, Product, Design and G&A. It's the company's third round since 2023, after about 500 in April 2023 and 528 in October 2024. Only 57 of the 2026 cuts appear in the San Francisco WARN filing.

What severance did laid-off Dropbox employees get?

Dropbox is paying 16 weeks of pay starting October 28, plus one week per completed year of service, along with Q4 equity vesting, a prorated bonus, immigration support for visa holders and six months of COBRA subsidy for US staff. Departing employees also keep their laptops. The memo says international packages will reflect local practices, so terms in Poland or Canada may differ.

How do I find ex-Dropbox Rust sync engine engineers?

Don't search job titles. In Refolk's index, a search for Rust plus sync or storage among senior US profiles returned zero matches. Start from dropbox.tech bylines on Nucleus and Magic Pocket, contributors to Dropbox's public GitHub repos and Rust crates, and conference speaker lists. Then match each person to their current profile.

When is the best time to contact laid-off Dropbox engineers?

Message visa holders first, since the standard H-1B grace period of up to 60 days points to late December. Check that against each person's case. Everyone else has severance running to at least mid-February 2027, so lead with interesting work rather than urgency. For engineers still at Dropbox, the window between Q3 earnings on November 5 and the CTO's exit on November 18 is a good time to start the conversation.