# Dropbox's CTO Exits Nov 18. Only 18 Profiles Say 'Dropbox Infrastructure'

_Dropbox cut 200 roles and its CTO leaves Nov 18 with no successor. Here is how to find the senior infrastructure engineers who stayed, beyond a title search._

- Canonical URL: https://www.refolk.ai/blog/dropbox-cto-exit-infrastructure-engineers-recruiting
- Published: 2026-11-17
- Reading time: 8 min
- Keywords: Dropbox layoffs 2026, Dropbox CTO Ali Dasdan, hire Dropbox engineers, recruiting engineers after executive departure, Dropbox infrastructure engineers

Dropbox's Oct 28 8-K cut about 200 roles and said CTO Ali Dasdan steps down on Nov 18, 2026. It named no successor. Every recruiter is already messaging the 200 who were cut. The better call is to the senior infrastructure and platform people who stayed and are about to lose their executive sponsor, with nobody yet named to replace him.

## What did Dropbox announce on Oct 28?

Dropbox cut about 9% of its global workforce, roughly 200 roles across Engineering, Product, Design and G&A, and said CTO Ali Dasdan would step down effective Nov 18, 2026. The filing named no successor.

Here's what the filing and the coverage say:

- **Stated reason:** to "align the Company's investments and team structure with its top product and growth priorities."
- **Cost:** restructuring charges estimated at $27M to $33M, mostly severance.
- **Headcount:** the base was 2,113 employees, so about 1,913 remain.
- **Dasdan's exit package:** a $515,000 pro-rated bonus plus a lump sum of about $1.3M.
- **Who signed the memo:** co-CEO Ashraf Alkarmi. (Reports on Drew Houston's status conflict. Dropbox's own blog says Alkarmi became co-CEO and Houston moves to executive chairman after a transition.)
- **Successor status:** an executive-moves newsletter dated Nov 11 lists the Dropbox CTO seat as "Search Underway?" As of Nov 17, I found no named replacement.

When a company announces a departure without naming a successor, the org chart below that role usually hasn't been settled. That gap is the opening.

## Why are the survivors a better target than the 200 who left?

The people cut on Oct 28 already have recruiters in their inbox. The senior infrastructure and platform engineers who stayed lose their top technical executive on Nov 18, and nobody has been named to own their roadmap after that.

Look at why Dasdan was there. Dropbox hired him in March 2025 from the ZoomInfo CTO role, where he "oversaw all of engineering, platform, infrastructure, data, enterprise, and security." His job was to drive the platform transformation behind Dash. Fortune's Oct 7 profile noted that Dropbox was his fifth CTO role in 15 years, and that fewer than 40% of engineering, product and design staff used AI tools when he arrived.

So the 2026 infrastructure roadmap (Riviera, Nova, the Magic Pocket efficiency work, infra efficiency for AI demand) was set under the AI-transformation mandate of an executive who leaves after about 20 months. Nobody owns that mandate now. And the engineers on those projects have watched Dropbox restructure before:

1. **Oct 2024:** 528 people laid off, about 20% of staff.
2. **Q2 2026:** restructuring costs booked for a reorganization "to unify the Company's product organization."
3. **Oct 2026:** about 200 roles cut (9%), plus the CTO exit.

That's three rounds in about two years. For a senior engineer inside the CTO org, "wait and see" is no longer a cheap stance. When you're recruiting engineers after an executive departure, the best window is the gap between the announcement and the new org chart.

> The 200 who were cut are already in every recruiter's inbox. The 1,900 who stayed are not.

## Why does a "Dropbox" title search mostly find alumni?

For many people, "Dropbox" in a headline marks where they used to work, not where they work now. In Refolk's index of professional profiles, 818 US profiles at senior to director level mention Dropbox in their headline. In a sample of the top 25, only 10 (40%) work there now.

The US results are diluted by founders, VCs and product people who have moved on. Meanwhile most of the senior infrastructure staff still inside don't put the company in their headline at all.

Narrow it to infrastructure and the pool collapses:

> **2.2%** Share of US senior "Dropbox" headlines that also say "infrastructure"
>
> 18 of 818 profiles in Refolk's index, and only 9 of those 18 currently work at Dropbox.

The other nine of those 18 have moved on to Google, Meta, LinkedIn, Palo Alto Networks, Marqeta and other companies. If you want to hire Dropbox engineers from the infrastructure org, a title search gives you nine current names at a company of about 1,900.

| Slice (senior to director) | Total profiles | Currently at Dropbox (sample) | Dominant titles |
|---|---|---|---|
| US, headline "Dropbox" | 818 | 10 of 25 (40%) | Execs, PMs, founders (alumni-heavy) |
| US, headline "Dropbox infrastructure" | 18 | 9 of 18 (50%) | Sr SWE, Directors, Head of Observability Infra |
| Poland, headline "Dropbox" | 27 | 22 of 25 (88%) | Sr SWE (11), Sr Infra SWE (2), Network Eng |
| US infra share of US Dropbox headlines | 2.2% (18/818) | n/a | n/a |

*Source: Refolk's index, keyword match on headlines, run Nov 17, 2026. "Currently at Dropbox" shares come from samples of top results, not full totals.*

## Who are the 18, and why do managers carry more risk?

The US "Dropbox infrastructure" slice has a lot of director-level platform titles. In a reorg, the layers above ICs are usually the first to be consolidated.

Titles in that slice of Refolk's index include:

- Head of Engineering, Observability Infrastructure
- Senior Director, Platform Foundation
- Director, Physical Infrastructure
- VP of Engineering
- Senior Director of Engineering

These are the managers who lose their sponsor. After Nov 18 they report to whoever ends up with the CTO's scope, and as of Nov 17 nobody knows who that is. Dropbox has already shown what it does with overlapping structures: the 2026 product-org unification merged them. A director running Platform Foundation can read that pattern as well as you can.

With this group, pitch scope, not comp. A director whose remit might shrink is comparing a bigger, defined remit somewhere else with an unknown one at home. Lead with the org they'd own.

> **Infrastructure engineering roles open now** - [see the open roles](https://www.refolk.ai/jobs/search?q=infrastructure)
>
> Live postings with infrastructure in the title, across employers.

## Why is Poland the cleaner pool for Dropbox infrastructure engineers?

In Poland, a Dropbox headline search maps almost directly to the current team. In Refolk's index, 27 senior profiles in Poland mention Dropbox, and 22 of the 25 sampled are current employees.

> **88%** Sampled senior Polish "Dropbox" profiles still at Dropbox
>
> Compared with 40% in the US, where alumni and founders dilute the results.

The US pool is about 30 times larger (818 vs 27), but most of it is noise. The Polish pool is small and almost all signal:

- **Titles:** 11 Senior Software Engineers, 2 Senior Infrastructure Software Engineers, and Senior Network Engineers working in automation and observability.
- **Cities:** Kraków, Warsaw, Gdańsk and Wrocław.
- **Leadership:** one profile titled "Poland Site Lead."

If you hire in the EU or hire remote, this is close to a ready-made list of the senior IC infrastructure and network engineers. The site lead is worth one direct, careful conversation of their own.

## How do you find the infrastructure engineers who don't say "Dropbox"?

Search their work, not their employer. The senior infrastructure people still inside Dropbox show up in tech blog bylines and conference talks, not in headline keyword matches.

The infrastructure team kept publishing right up to the cut. 2026 posts on dropbox.tech include:

- **Monorepo size reduction** (Mar 25)
- **Magic Pocket storage efficiency** (Apr 2)
- **Nova**, an internal coding-agent platform (May 21)
- **Riviera**, the content-processing platform (Jul 20)
- **Infra efficiency for AI demand** (Aug 18)

Every one of those posts has authors, and the authors are the people who own the systems. Facundo Agriel is the clearest example. He's the engineering manager who presented Magic Pocket at QCon, and InfoQ covered it as exabyte-scale storage that replaced S3 and runs at 99.99% availability. You find him through the talk and the write-up, not through a "Dropbox" title filter.

A workable sourcing sequence:

1. **Pull 2026 bylines** from dropbox.tech/infrastructure and the all-stories feed. Note which system each author owns.
2. **Cross-reference conference talks.** QCon abstracts and InfoQ coverage name speakers and their teams.
3. **Confirm current employment** on the professional profile before you write. Half the US "Dropbox infrastructure" headlines belong to people who already left.

Doing this by hand means a tab per source for every name and a spreadsheet to reconcile them. [Refolk](/) removes that step. You describe the person in plain English (the system they built, the city, the seniority) and get a ranked shortlist, whatever their headline says.

> **Example search:** "Senior infrastructure engineers who wrote or presented on Dropbox's Magic Pocket, Riviera, or Nova systems in 2026 and still work at Dropbox" - [run it on Refolk](https://www.refolk.ai/s/mscfcb400a)
>
> A ranked list of named engineers with their blog posts and talks linked, and current employer confirmed.

## What should the first message to a Dropbox engineer say?

Name the specific system they built and the specific uncertainty after Nov 18. A generic "saw the Dropbox layoffs 2026 news, thought of you" won't stand out.

The numbers explain why. About 1,913 people remain company-wide, and only a small share of them work in infrastructure. This isn't a volume campaign. You're writing to a few dozen named people, and each message has to show you know their work.

What to put in it:

- **The artifact.** "Your April post on Magic Pocket storage efficiency" beats "your Dropbox experience."
- **The mandate question, stated neutrally.** Something like: "Riviera and Nova were set up under the Dash platform push. Curious how that roadmap looks after Nov 18." Don't speculate about their job security.
- **A defined scope.** The headcount, the system and the reporting line they'd have. A reorg can't promise them that.
- **A low-cost next step.** A 20-minute call about the system, not an application link.

What to leave out:

- Any reference to Dasdan's severance numbers or internal politics.
- Claims about who's leaving next.
- Generic AI-transformation pitches. They've just lived through one.

Timing matters more than polish. The best window is between Dasdan's exit and the announcement of the new structure. After that, people either have a new sponsor or have already decided.

## FAQ

### Is it too early to approach Dropbox engineers after the Oct 28 layoffs?

No. The cut was announced Oct 28, but for the people who stayed, the CTO exit on Nov 18 is the event that matters. Until a new technical leader or org structure is announced, senior infrastructure staff know the least about their future and have the most reason to take a call. Send a specific, work-based message, not a layoff-condolence note.

### Who replaces Ali Dasdan as Dropbox CTO?

As of Nov 17, 2026, nobody has been named. The Oct 28 8-K announced Dasdan's departure effective Nov 18 without naming a successor, and a Nov 11 executive-moves newsletter listed the role as "Search Underway?" Until someone is named, the CTO org has no technical executive at the top.

### How many Dropbox infrastructure engineers can a recruiter realistically find?

Fewer than a title search suggests. In Refolk's index, only 18 US senior-to-director profiles mention "Dropbox infrastructure" in their headline, and just 9 of those currently work there. In Poland, 22 of 25 sampled senior Dropbox profiles are current employees. You can find the rest of the infrastructure org through dropbox.tech bylines and conference talks such as the QCon Magic Pocket session.

---

_From the Refolk blog. More posts: https://www.refolk.ai/blog/index.md_
