Dropbox Cut 200 Virtual First Staff. Search Kraków and Monterrey, Not SF

Dropbox cut about 200 roles on October 28, 2026, and for most of the people affected, that was also their last day. If your first move was a search for "Dropbox" plus "San Francisco," you found only a small share of them. Dropbox has been Virtual First since 2021. Its engineers, PMs and designers live in Austin, Kraków, Warsaw and Monterrey, plus plenty of home metros that never mention SF.

What did Dropbox announce on October 28, 2026?

Dropbox said it would cut approximately 9% of its global workforce, about 200 roles, across Engineering, Product, Design and G&A. Most affected employees left the same day.

The 9% figure appears in the SEC Form 8-K, the company blog post and Reuters. Some coverage said 6%, and one outlet said around 190 people. Reuters put Dropbox's full-time headcount at 2,113 as of December 31. Since 200 of 2,113 is about 9.5%, "about 200" is the safe way to describe it.

What a recruiter needs to know about the Dropbox layoffs of October 2026:

• Severance: 16 weeks of pay plus one week for each completed year of service. International packages follow local practice and law.
• Visa holders: affected employees on visas get immigration support.
• Equipment: departing staff keep their laptops, mobile devices and desktop peripherals.
• Cost: $27 million to $33 million, mostly severance and benefits.
• Leadership: CTO Ali Dasdan leaves November 18 with a $515,000 pro rata bonus and a lump sum of about $1.3 million. He became CTO in March 2025, after serving as CTO at ZoomInfo and running engineering for Confluence Cloud at Atlassian.
• Context: CEO Ashraf Alkarmi announced the cuts. Drew Houston moved to executive chairman after 19 years as CEO.

9%

The company is not in trouble. It expects third-quarter revenue and adjusted operating margin to meet or beat its earlier forecast, and it reports earnings on November 5. This is also its second big cut in two years. In October 2024 it let go approximately 20% of staff, or 528 people. Some of the people leaving now got through that round. They have severance, and they won't take the first offer they get.

Why does a "San Francisco" filter miss most of them?

Dropbox hires by country and pay zone, not by office. A location filter for San Francisco catches only the minority who happen to live there.

Dropbox puts US roles into pay zones: if you live within 100 miles (straight-line radius) of a listed metro, you're in that metro's zone. An engineer who lives in Austin has no reason to put "San Francisco" on a profile. Outside the US, postings use remote labels like these:

• Remote - Canada: Select locations
• Remote - Mexico
• Remote - Poland
• Remote - Germany (for example, Machine Learning Engineer, Dash)

Profiles tend to show the person's home metro instead. In Refolk's index, only 7 of 25 sampled US Dropbox-linked engineers, PMs and designers list a Bay Area location (San Francisco, SF Bay Area or Sunnyvale). That's 28%. Austin, New York and DC-Baltimore together account for 8, one more than the whole Bay Area.

A Virtual First company's layoff list is a map of home addresses, not a map of offices.

Where do Dropbox's engineers, PMs and designers actually live?

Most are in the US, but Poland has its own cluster, and every sampled profile in it still lists Dropbox as the current employer. Mexico barely shows up in keyword search, even though Dropbox hires there.

I ran this against Refolk's index: "Dropbox" in the headline, plus a title containing Software Engineer, Engineer, Product Manager or Designer.

What the table tells you:

• The US has about 8x as many matches as Poland.
• Poland is about 11% of the three-country total (33 of 299).
• About 72% of sampled US profiles list somewhere other than the Bay Area.
• In the Polish sample, Kraków and Warsaw together make up 60%.

One caveat. The location counts come from a 25-profile sample per country, not the full set. Treat them as a sense of proportion, not a census.

Why is Dropbox Poland worth sourcing first?

Dropbox Poland is a backend infrastructure hub, not a support office. Its postings cluster around Metadata Services, Smart Storage Management, Payments and Data Observability.

The Polish operation is new. Dropbox opened a Polish entity and started hiring there for the first time in August 2022. The first teams were Content Security, Platform Infrastructure, Product Growth, Quality Engineering and HelloSign (now Dropbox Sign). Recent postings carry the same focus:

• Infrastructure Software Engineer, Metadata Services, Poland (posted September 24, 2026)
• Staff Fullstack Software Engineer, Smart Storage Management, Remote - Poland
• Backend Product Software Engineer, Payments, Remote - Poland

A warning applies to every team name in this article. Dropbox has not said which teams were cut. Postings show where people work, not who was laid off. Use team names to find the right people, then confirm their status in conversation.

Dropbox's own posted ranges give you a pay benchmark for remote software engineers in Poland:

• Full Stack Product Software Engineer: 212,500 to 287,500 PLN
• Network Engineer: 225,300 to 304,800 PLN

Those ranges set the bar. Anyone you approach knows their old band, and an offer below it will need a strong case on scope.

Senior infrastructure engineers in Kraków and Warsaw are hard to hire in a normal month, and the ones who have run metadata and storage systems at Dropbox rarely reach the open market. Some of them may be available right now, in a pool of 33 visible profiles that your competitors can find as easily as you can.

Why does a keyword search find only one Dropbox engineer in Mexico?

Mexico is nearly invisible to company-name search. Refolk's index has exactly 1 Dropbox-linked match there (in Monterrey), yet Dropbox posts Mexico roles in API Platform, Identity & Auth, Network and Product Management.

The gap likely has two causes:

1. Spanish-language titles. "Ingeniero de Software" doesn't match a search for "Software Engineer."
2. Headlines without the employer. A headline that names a stack or specialty instead of a company never matches "Dropbox."

So to source engineers in Mexico who worked remotely for Dropbox, search on what they did, not on what their headline says. Look for API Platform, identity and authentication, or network infrastructure work, check the experience history for Dropbox, and run titles in both English and Spanish. Doing that by hand across LinkedIn and GitHub is slow. Refolk closes exactly that gap: you describe the person in plain English, and it matches on team, stack and history instead of on whether the headline says "Dropbox."

Why does "current employer: Dropbox" still work?

For the next few weeks, a search for current Dropbox employees still includes most of the laid-off group. People update their profiles slowly, and most exits happened on October 28 itself.

25 of 25

This window won't last. As people update their profiles, the group spreads out into "ex-Dropbox," new employers, or vague "open to new opportunities" headlines. Until then, the current-employer filter is a ready-made list. It just mixes the people who stayed with the people who left. Look for these signals to tell them apart:

• An "Open to work" badge or banner added since October 28
• A headline change that drops "at Dropbox" or adds "previously"
• An end date added to the Dropbox role
• A public post about the layoff, often with a team name in it
• New personal GitHub activity after a quiet stretch

Reach out to people showing those signals first. Write to the rest carefully, because some of them still work at Dropbox and would rather not get a "sorry about your layoff" message.

When will laid-off Dropbox engineers accept offers?

Later than you'd think. The severance formula gives a four-year employee about 20 weeks of pay, so many won't feel any pressure to sign until around March 2027.

The formula is 16 weeks plus one week per completed year, so runway grows with tenure:

These dates apply to US packages. In Poland, Mexico and Canada, terms follow local law, so ask instead of assuming. Visa holders are the exception to "no rush." Immigration support helps, but their deadlines run on a different clock, so they may decide faster.

What this means in practice: get in touch now, while you're one of a few recruiters in their inbox, and sell the role, the team and the problem to solve. Exploding offers rarely work on someone with five months of pay in the bank. A start date timed to their runway often will.

How do you build the search, step by step?

Search by country, team and remote location string, in that order, and use the company name to confirm a match rather than to find people. Here is the sequence I'd run to hire laid-off Dropbox engineers this month.

1. Split by country. Run the US, Poland, Mexico and Canada as separate searches. Don't add a city filter in the US.
2. Search on posting labels. Use Remote - Poland, Remote - Mexico and Remote - Canada: Select locations as location or keyword strings.
3. Add team names. Use the table below.
4. Run titles in two languages for Mexico. Pair "Software Engineer" with "Ingeniero de Software."
5. Filter on current employer, then on signals. Use the checklist from the section above.
6. Check GitHub. Infrastructure engineers often have public repos even when their LinkedIn is thin.

FAQ

How many people did Dropbox lay off in October 2026?

About 200, or roughly 9% of its global workforce, across Engineering, Product, Design and G&A. The 8-K, the company blog post and Reuters all use the 9% figure. Against the 2,113 full-time employees Reuters reported as of December 31, 200 works out to about 9.5%. Some outlets reported 6% or around 190 people, so "about 200" is the safest number to quote.

Where are laid-off Dropbox engineers located?

Dropbox hires in the US, Poland, Mexico and Canada, and has posted roles in Germany and Denmark too. In Refolk's index, only 28% of sampled US profiles list a Bay Area location, and Poland has a cluster of 33 engineers and PMs, 60% of the sample in Kraków and Warsaw. Mexico is underrepresented in keyword search, so search by team and remote location string there.

What do Dropbox engineers in Poland earn?

Dropbox's posted ranges are 212,500 to 287,500 PLN for a Full Stack Product Software Engineer and 225,300 to 304,800 PLN for a Network Engineer. Use those as the floor for any offer. These engineers know their old band, and Dropbox Poland's work leans toward hard-to-hire backend infrastructure.

Should I wait until their severance runs out?

No. Contact them now and set the start date for later. US packages run 16 weeks plus one week per year of service, so a four-year employee has pay into about mid-March 2027. Showing up early with a flexible start date beats showing up in February with a deadline.