Dropbox Is Buying Tigris for $350M. 'Magic Pocket' Finds 54 Wrong People
Dropbox cut about 200 roles, lost its CTO, and agreed to buy Tigris. Here is how to source its storage engineers when name and project searches both fail.
If you hire distributed storage engineers, Dropbox's in-house storage team may be open to a move right now. The hard part is finding them: a company-name search can't pick them out from everyone else at Dropbox, and the obvious fix (searching the internal system name) doesn't work either.
Here's why they may be open. Dropbox cut about 200 roles on Oct 28. Its CTO left on Nov 18. In between, it agreed to pay about $350M for Tigris Data, an S3-compatible storage startup.
What did Dropbox actually do in October and November 2026?
In about three weeks, Dropbox cut roughly 9% of its staff, lost its CTO, and agreed to buy a storage startup for about $350M in cash. Put simply, it let engineers go and agreed to buy a storage team in the same month.
Here's the timeline:
- Oct 28: Dropbox announced it would cut about 9% of its global workforce, roughly 200 roles across Engineering, Product, Design and G&A. It put cash costs at $27M to $33M, mostly severance. For most affected staff, Oct 28 was the last day.
- Nov 3: Dropbox signed the definitive agreement to buy Tigris Data for about $350M in cash.
- Nov 5: Dropbox announced the deal. TechCrunch says it appears to be Dropbox's largest acquisition to date.
- Nov 18: CTO Ali Dasdan stepped down. He gets a $515,000 pro rata bonus and a lump sum of about $1.3M.
Some context. Dropbox had 2,113 full-time employees as of Dec 31. Q3 2026 revenue was $637.3M, up 0.5% year over year, at a 27.5% GAAP operating margin. Co-founder Drew Houston stepped down as CEO in May. The SEC filing treats the Tigris deal as pending, with close expected in Q4 2026. Coverage ties the deal to DBX Agent Cloud, which has no GA date yet. Dropbox says it has no plans to cut headcount as part of the deal.
The flat revenue line explains everything else. When the core business barely grows, a company protects margin by cutting costs and buys growth from outside. Infra engineers know which side of that ledger they usually sit on.
Why don't "Dropbox" or "Magic Pocket" searches find the storage team?
Headlines hold a title and an employer, not the name of an internal system. A "Dropbox" search can't pick the storage team out of a company of about 2,000 people. In Refolk's index, a headline search for "Magic Pocket" returns 54 profiles worldwide, and Dropbox isn't among the top 10 employers.
I covered the leadership side of this in Dropbox's CTO exit and its infrastructure engineers. The sourcing problem is simpler than it looks. The brand is too broad a filter, and the project name is in the wrong field.
Most of the "Magic Pocket" hits are noise. The top "employer" is an unrelated company called Magic Pockets (5 profiles). Next comes Magil Construction (3). Magic Pocket itself is very real, though. It's Dropbox's in-house, exabyte-scale immutable blob store. It started as a small team in summer 2013, and Dropbox is still publishing engineering posts about it this year.
Internal project names belong in the longer text: experience descriptions, conference abstracts, engineering blog bylines. An engineer who spent years on Magic Pocket writes "Staff Engineer, Dropbox" in the headline and saves the system name for the third bullet of their experience. If your tool only matches headlines, the name you know best works against you.
Why does searching "object storage" miss them too?
Dropbox runs one of the largest object stores in the world. Even so, in Refolk's index it isn't a top-10 employer for "object storage" among US profiles. The market's term for the work isn't the term the team uses for it internally.
The US search returns 221 profiles. The top employers are IBM (6), Apple (4), Scality (2), Microsoft (2) and Object First (2). Most of these companies sell storage, so their people use the market's word for it.
Inside Dropbox the same work goes by blob storage or block storage. So a search for "S3-compatible" pulls vendor engineers at IBM, Scality and NetApp, not the people who left AWS to build their own store. Tigris is S3-compatible, so the market's label now fits what Dropbox is buying. It still doesn't fit the vocabulary of the people who built the store Dropbox already runs.
What happens when you stack storage keywords?
The pool collapses. Four storage terms plus a Senior filter took 221 US profiles down to 4, a drop of about 98%, and none of the 4 work at Dropbox.
| Query (headline keywords) | Scope | Profiles |
|---|---|---|
| "object storage" | US, all seniority | 221 |
| "object storage S3 distributed storage" | US, Senior only | 4 |
| "Magic Pocket" | Global | 54 (Dropbox not in top 10) |
| Dropbox layoff | Global | ~200 roles (SEC and press) |
| Tigris price per Series A dollar | n/a | ~14x ($350M / $25M) |
The first three rows come from Refolk's index (headline keyword match). The layoff row comes from press and SEC filings. The last row is derived from public figures.
The 4 who survive the filters work at IBM (CephaaS), Dell, NetApp and Seagate (Lyve Cloud). None of them are the people you were looking for.
This is the headline problem again, only worse. Senior storage engineers tend to write short headlines. Each keyword you AND together drops everyone who didn't type that exact word, so the people with the most experience go first. The fix is to search on one strong signal, then filter on what's in the experience text.
A hard-to-fill infra search usually goes like this. A recruiter rewrites Boolean strings for weeks and gets back vendor engineers. An agency quotes a fee on a role it can't scope. The hiring manager starts asking whether the person exists at all. For a niche like exabyte blob storage, that loop can stall the search entirely.
Where do Dropbox storage engineers actually leave a trail?
They show up wherever the internal vocabulary appears: experience descriptions, dropbox.tech bylines, conference talks, and the terms of the system itself. Search those places, not the headline.
- Experience descriptions. Use the system's vocabulary: "Magic Pocket," "immutable blob storage," "erasure coding," "SMR," "exabyte." One of these in a Dropbox experience entry is worth more than four in a headline.
- dropbox.tech bylines. Posts carry either a person's name or a team name, such as "Magic Pocket Hardware Engineering Teams." The 2016 post "Pocket Watch" was written by an engineer who has since left Dropbox. Old bylines tell you who was on the team years ago and where they went later.
- Conference talks and podcasts. Storage engineers give talks on durability, repair and hardware efficiency. Speaker lists often name people whose profiles never mention the system.
- Former teammates. Someone who left Dropbox storage years ago is a lead to whoever is still there. Tracing a proven team's diaspora is how you turn one byline into a located list.
Weigh the evidence, too. "Erasure coding" in a self-written bullet is a claim. A dropbox.tech byline on a Magic Pocket post is proof. The skill-evidence reference for claimed, practiced, and proven lays out how to grade each kind.
Searching experience text and bylines together is slow by hand, and Refolk closes exactly that gap. You describe the engineer in plain English and get back a ranked shortlist. Each name comes with the evidence that matched, not just a headline keyword hit.
Why would Dropbox storage engineers take a call now?
About a week after cutting Engineering, Dropbox agreed to pay roughly 14x Tigris's $25M Series A for an outside storage team to run a new business. Any in-house infra engineer can fairly ask whether their work is the strategy or just a cost to keep down.
Look at what Dropbox is buying. Ovais Tariq (CEO), Himank Chaudhary (CTO) and Yevgeniy Firsov (Chief Architect) founded Tigris in Nov 2021 after building Uber's storage platform (Docstore, Herb, DBEvents). Spark Capital led its Series A. Tigris reports more than 1B requests a day, 20 PB stored and 10B objects, and a separate report puts it at 4,000+ customers.
That's a serious business. It's also a fraction of the exabyte-scale store Dropbox already runs.
Dropbox runs an exabyte blob store in house, then agreed to pay $350M for a team storing 20 petabytes.
The reorg after close will show who runs DBX Agent Cloud. If it's the Tigris founders, the Magic Pocket veterans keep the old store running while the new product gets the attention. Engineers who see their work that way take recruiters' calls. Dasdan's exit adds to the pull. He's a well-known infrastructure leader, and wherever he goes next could take people with him.
So pitch scope, not sympathy. "I saw the layoffs" is what everyone else will open with. "You'd own the storage layer, not maintain it next to an acquired team" is the line that gets a reply.
When should you reach out to Dropbox storage engineers?
For most of them, Q1 2027. Laid-off engineers have months of runway, and employed engineers are waiting to see who runs DBX Agent Cloud after the Tigris deal closes.
The timing depends on which group someone is in:
- Laid off on Oct 28. Severance is 16 weeks of pay plus one week per year of service, which works out to roughly 4 to 6 months of runway. They aren't desperate and won't take a lowball. Contact them now, but expect a deliberate process.
- Still employed, storage org. The deal is expected to close in Q4 2026. The reorg after close will show who reports to whom. Q1 2027 is when that picture settles and people start acting on it.
- Close to Dasdan. Watch where he lands. His next move could take some of his former reports with him.
Most of the restructuring cash costs land in Q4 2026, with the rest in 2027. The timing fits: the company works through the cuts this quarter, and people make their decisions in the next one. Before you make an offer, check it against current engineering salaries in the United States. An engineer with 16 weeks of severance in the bank will hold out for a market-rate number.
Which adjacent pools should you search alongside Dropbox?
Search the companies that already lead object-storage headlines in Refolk's index, plus the Tigris team itself. These pools deal with the same problems as Dropbox (durability, repair, cost per byte) and are much easier to find.
- IBM Cloud Object Storage. IBM leads the US "object storage" search with 6 profiles, and one of the 4 senior survivors works on CephaaS.
- Scality, NetApp StorageGRID, Object First. Vendor engineers who use the market's vocabulary and show up cleanly in search.
- Seagate Lyve Cloud. Home to another of the 4 senior survivors.
- Storj. Also among the top employers in Refolk's index for these storage searches.
- Percona Live and Percona podcasts. The Tigris founders have spoken there, which makes it a good place to find storage-database engineers.
- Tigris after close. Early hires at an acquired startup sometimes leave once the deal closes. The acquired-startup talent window covers how to time and tier that slate.
FAQ
Did Dropbox lay off storage engineers specifically?
Dropbox said the roughly 200 cuts spanned Engineering, Product, Design and G&A. It hasn't said which engineering teams were hit. Don't assume the Magic Pocket team lost people. Do assume the team reads the Tigris deal as a signal about its own future. That matters more for outreach than any layoff list.
Has the Dropbox Tigris acquisition closed?
The SEC filing calls it pending, with close expected in Q4 2026, though some outlets have reported it as done. The definitive agreement was signed Nov 3 and announced Nov 5 for about $350M in cash. Dropbox says it has no plans to cut headcount as part of the deal.
How much severance did laid-off Dropbox employees get?
Severance is 16 weeks of pay plus one week per year of service, and most affected staff had Oct 28 as their last day. Dropbox estimates $27M to $33M in cash costs, mostly severance. That gives laid-off engineers roughly 4 to 6 months of runway, so expect them to compare offers rather than take the first one.
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.