Dropbox Cut 200. Its CTO Leaves Nov 18. Pitch the 1,900 Who Stayed

Dropbox cut about 200 people on Oct 28, 2026, and the same SEC filing said CTO Ali Dasdan leaves on Nov 18. Most recruiters will go after the laid-off list. The better pool is the roughly 1,900 engineers and managers who kept their jobs and are about to lose the executive who backed their work.

What happened in the Dropbox layoffs 2026

Dropbox cut about 9% of its global workforce, roughly 200 of its 2,113 employees. The same 8-K said Chief Technology Officer Ali Dasdan steps down effective Nov 18, 2026.

The details that matter for sourcing:

• Size: about 200 roles, which leaves roughly 1,913 people in place.
• Cost: $27 million to $33 million in cash, mostly severance and benefits.
• Severance: 16 weeks of pay plus one week per year of service, Q4 equity vesting, six months of COBRA subsidy, and immigration support for visa holders.
• CTO exit: Dasdan gets a pro rata bonus of $515,000 and a lump sum of about $1.3 million. He has been CTO only since March 2025, after serving as Head of Engineering for Confluence Cloud at Atlassian.
• Motive: co-CEO Ashraf Alkarmi's memo called the business "profitable" with "real momentum this year," and it did not mention AI.

That last point changes how you read the cut. This isn't a company short of cash. It's a reprioritization, so specific projects and teams lose priority while the company keeps going. A reprioritization unsettles the people who stay more than a cash crunch would, because nobody knows yet which roadmaps survive.

Why the 200 who were cut can afford to wait

The severance package pays the laid-off group for months, so the strongest of them have no reason to take the first offer. Pitching them in November means competing with a paid break.

Severance runway is the stretch of time a laid-off employee keeps getting paid without working. Counting from Oct 28, Dropbox's package runs:

• Base case: 16 weeks, ending around Feb 17, 2027.
• Five-year employee: 21 weeks, ending around Mar 24, 2027.
• On top of that: Q4 vesting and six months of COBRA, so the health insurance worry is gone too.

16 weeks

Expect the strong engineers who were cut to take the holidays off and interview in the new year. You can still reach them, but you'll be one inbox among many, and the leverage sits with them. The people who stayed get no cushion, and their org chart is about to change.

Why the engineers who stayed are more likely to move

The engineers and managers who stayed are losing their technical sponsor in the fourth senior leadership change in about a year. Every change like that reopens questions about roadmaps, headcount and promotions.

A technical sponsor is the senior leader who argues for a team's headcount, roadmap and promotions in meetings the team never attends. When that person leaves, every commitment they made is up for renegotiation. Here is how Dropbox's leadership has changed since late 2025:

• December 16, 2025: CFO Regan resigns.
• May 26, 2026: Ashraf Alkarmi becomes co-CEO, and co-founder Drew Houston is set to become executive chairman after a transition.
• Recently: Michael Torres, formerly of Alphabet and Amazon, is named chief product officer.
• November 18, 2026: CTO Ali Dasdan leaves after about 20 months.

Layoffs have also become routine. Dropbox cut around 500 people about two years ago, and now another 200. The memo said the company would avoid piling the same workload onto the people who remain. In practice that means projects get cancelled rather than squeezed. An engineer whose project was cancelled in November isn't fired, but they no longer have a reason to stay.

The engineers worth calling were not cut. Their sponsor was.

The Dropbox WARN notice shows only 3 in 10 of the cuts

California's WARN filing covers 57 positions at Dropbox's headquarters at 50 Hawthorne Street in San Francisco. That's about 28.5% of the roughly 200 roles cut, so around 143 of them never appear in it.

The filing lists Nov 18 as the effective date, the same day Dasdan leaves. Anyone affected outside that one San Francisco notice is invisible to a recruiter working from WARN data.

28.5%

That creates two blind spots for anyone sourcing from WARN databases:

• It's a San Francisco list. Refolk's index shows Dropbox engineers in Washington DC, New York, Austin, Portland and Dallas, plus a Warsaw and Vancouver base. None of them show up in a California filing.
• It leaves out everyone who stayed. WARN only covers people who were cut. The roughly 1,900 people facing the CTO change aren't in any filing.

To build a list that covers both groups, search by employer and role instead of by filing. In Refolk you describe the person in plain English, for example "current Dropbox engineering managers in Greater Seattle," and get a ranked shortlist. It doesn't matter which office they used to badge into.

How many Dropbox engineers can you actually reach?

Refolk's index holds 487 Dropbox-linked engineering profiles across the US, Poland, Canada and Ireland. Sampling suggests around 390 of them still work at Dropbox. These are headline keyword matches, so treat them as floors. Plenty of engineers never put their employer in their headline.

Two things in this data shape the plan.

First, the people already gone are going somewhere specific. Among US ICs who list Dropbox in their headline but work somewhere else now, Meta is the most common current employer (3 of 25 sampled). Meta and Databricks are the most common current employers of ex-Dropbox engineers and managers across the index. Assume both are already sourcing this pool, and write your pitch so it doesn't read like theirs.

Second, the share still at Dropbox goes up as you move from US ICs to managers to international staff. The manager and international segments have the highest share still in place, so they're the least picked over.

Dropbox's engineering managers are the short list worth calling

With about nine US ICs for every manager, only about 34 identifiable US engineering managers still work at Dropbox. They're the people most exposed to the CTO's exit. At that size you can work through the list by hand, one person at a time, without running a campaign.

The index matched 41 US profiles titled Engineering Manager, Senior EM or Director of Engineering, and 21 of the 25 sampled still work at Dropbox. They cluster in two places:

• Greater Seattle: 6 of 25 sampled, or 8 counting Redmond and Snohomish.
• SF Bay Area: 11 of 25 sampled.

Here's why managers move first. When a CTO leaves mid-reorg, each manager's headcount, roadmap and promotion cases get renegotiated with whoever replaces him. Until that person is named, nobody can make those commitments. Managers whose influence ran through the CTO's office have more to lose than those whose ties run through product.

Power also looks likely to shift toward Seattle and product. Alkarmi is Seattle-based and came from Core Products. Torres is a new CPO. The CTO seat will be empty. An engineering director in the Bay Area who was close to Dasdan now reports into a structure that didn't exist six months ago.

The pitch to a Dropbox manager writes itself, and it's specific: your sponsor is leaving, and here's a role where your sponsor is named, has been in the seat a while, and has already agreed to the headcount. Put the hiring manager's name in the first message. Vague promises about growth won't land with someone who just lost the person who made those promises.

Warsaw and Vancouver are the pool WARN never shows

Dropbox's non-US engineers don't appear in any US filing. Refolk's index finds 77 engineering profiles across Poland, Canada and Ireland, and 24 of the 25 sampled still work at Dropbox.

They cluster in a few cities:

• Warsaw: 4 of 25 sampled.
• Vancouver: 4 of 25 sampled.
• Also present: Kraków, Poznań and Gdańsk.

The 96% current share is the highest of any segment, so few recruiters have pulled from this group yet. The CTO exit on Nov 18 isn't limited to the US org, so the same sponsorship questions likely apply here. The difference is that US recruiters scraping WARN data won't find them. If your client hires in Poland or Canada, or will hire remotely there, this is the least crowded part of the Dropbox pool.

How to recruit engineers after a CTO departure

Contact the people who stayed between Nov 18 and January, and pitch sponsorship and scope instead of bringing up the layoff. The playbook works for any company that loses its CTO during a reorg, and Dropbox is a clean example:

1. Build the list by employer. Start from current Dropbox ICs and managers, not WARN data. That covers the roughly 143 cut roles outside the California notice and everyone who stayed.
2. Start with managers. About 34 US EMs and directors is a list one recruiter can work in a week. Seattle and the SF Bay Area first.
3. Time the first message for the week after Nov 18. Once the CTO's last day has passed, the reorg stops being a rumor. Follow up in early January, when a replacement structure is either clear or still missing.
4. Lead with who they'd report to. Name the hiring manager, their tenure, and the headcount they've already secured. That answers the question a Dropbox engineer is asking right now.
5. Ask about the project. "What happened to the thing you were building?" opens a better conversation than "Sorry about the layoffs," especially since this person wasn't laid off.
6. Assume Meta and Databricks got there first. Say clearly what your role offers that a big-company transfer doesn't: scope, a stable sponsor, a shorter path to staff.

Run the same search again in January. Headlines change slowly, but some people will have dropped "Dropbox" or added a new employer by then, and that tells you who has already moved and who's still deciding.

FAQ

When is the best time to hire Dropbox engineers after the 2026 layoff?

For people who stayed, the window opens on Nov 18, 2026, when Ali Dasdan's departure takes effect, and runs into January while the reorg settles. For people who were cut, severance runs to roughly Feb 17, 2027 at minimum and into late March for longer-tenured staff, so many will interview seriously only in the new year.

Does the Dropbox WARN notice list everyone affected?

No. The California WARN notice covers 57 positions at the San Francisco headquarters, about 28.5% of the roughly 200 cuts. Around 143 affected roles sit outside it, and the notice says nothing about the roughly 1,900 employees who stayed.

Who replaces Dropbox CTO Ali Dasdan?

The departure announcement leaves the CTO seat empty after Nov 18. Until someone is named, engineering managers can't get firm commitments on headcount or roadmaps, and that's what makes them open to outside offers right now.

Is Dropbox in financial trouble?

Co-CEO Ashraf Alkarmi's memo described the business as profitable with real momentum and a two-year strategy for growth, and it didn't mention AI. Treat the cut as a reprioritization. That matters for your pitch: these engineers aren't fleeing a sinking company, so offer them a clearer role and a named sponsor rather than job security alone.