If you're deciding whether to apply to Dropbox, or to any company that just cut staff, don't start with the layoff headline. The earnings release and the deal filing tell you which team is getting the money and which words your resume needs to reach it.
Dropbox laid off about 200 people on Oct. 28. Eight days later it announced a $350 million cash deal for Tigris Data, an S3-compatible object storage startup that sells to AI developers.
Should I apply to a company that just had layoffs?
Yes, if the filings show the layoff paid for a new bet and wasn't plugging a cash hole. To check, put what the cut cost next to what the company spent right after it.
Here are the Dropbox layoffs of 2026 in the company's own numbers. Co-CEO Ashraf Alkarmi's memo cut about 200 of 2,113 employees (roughly 9.5%) across Engineering, Product, Design and G&A. Dropbox expects $27 million to $33 million in cash costs from the cut. On Nov. 5 it announced a definitive agreement to buy Tigris for about $350 million in cash, which appears to be its largest acquisition ever. It said it had no plans to reduce headcount as part of the deal, and it completed the purchase on Nov. 17.
| Figure | Amount | Where it comes from |
|---|---|---|
| Layoff cash cost | $27M to $33M | Company estimate |
| Tigris purchase price | ~$350M cash | SEC 8-K |
| Q3 unlevered free cash flow | $303.9M | Q3 earnings release |
| Q3 revenue growth | 0.5% year over year | Q3 earnings release |
Unlevered free cash flow is the cash a business generates from operations before interest payments. Dropbox paid for Tigris with roughly 1.15 quarters of it.
Dropbox generates about the deal price in free cash flow every quarter, so the cut was not about survival.
A company with this profile is shifting headcount from one area to another, not shrinking. So the useful question about Dropbox hiring after layoffs is which team the money went to, not whether the company is in trouble.
Why would a cash-rich company cut and buy in the same month?
Because the core product has stopped growing, and the cash it produces has to go into something that might grow. The layoff took budget away from the flat business, and the acquisition put it into the new one.
The Q3 release spells it out:
- Revenue was $637.3 million, up 0.5% year over year.
- Average revenue per paying user was $138.76, down from $139.07.
- Gross margin rose to 81% from 80% as cost of revenue fell 3.7%, mainly because infrastructure got cheaper.
Paying users are paying slightly less, and margins are growing through cost control, not pricing power. When revenue is that flat, headcount on the legacy roadmap is the first cost a board looks at. The cut landed in Engineering, Product and Design, the same functions a new product needs, so the company is choosing between skill sets rather than cutting everywhere.
Leadership is changing too. CTO Ali Dasdan steps down effective Nov. 18, the day after the Tigris deal closed.
Which Dropbox team is still being funded?
Dropbox is funding DBX Agent Cloud, the new business built around Tigris, which sells S3-compatible object storage to AI developers. According to the Q3 earnings release, it starts with standalone, S3-compatible object storage and will expand over time into filesystem and content-processing capabilities.
A few definitions, since you'll need these words on your resume:
- Object storage stores data as separate objects with metadata, in a flat namespace, accessed through an HTTP API instead of a file path.
- S3-compatible means the service speaks Amazon S3's API, so tools and code written for S3 work without changes.
- Egress fees are what a cloud provider charges to move data out of its network, for example when your compute runs somewhere other than AWS.
Ovais Tariq is Tigris's co-founder and CEO. His co-founders, Himank Chaudhary and Yevgeniy Firsov, are former Uber storage engineers. Its named customers are Railway, Runpod and Replicate, which tells you the product is aimed at developer platforms. Tigris raised a $25 million Series A in October 2025 from Spark Capital and Andreessen Horowitz, bringing total funding to $31.9 million, so Dropbox paid about 11x what investors had put in.
Storage isn't a new skill for Dropbox. By 2016 it stored more than 90% of user data on its own infrastructure as it moved away from Amazon S3, and the Q3 margin gain came from lower infrastructure costs. The company has run its own storage stack for a decade and now plans to sell storage to other companies.
A second funded area shows up in the earnings call: 1.4 million users connected Dropbox to AI tools like ChatGPT and Claude, up from 150,000 the quarter before. Integrations, connectors and AI-facing APIs are the other place headcount is likely heading.
The 73x wording gap in Refolk's index
Most people who have done object-storage work describe the tool they used, not the category it belongs to, and that gap is your opening. In Refolk's index of professional profiles, about 73 times more US profiles list "Amazon S3" as a skill than list "Object Storage."
| Skill tag in Refolk's index | Profiles |
|---|---|
| "Amazon S3," US | 61,700 |
| "Object Storage," US | 842 |
| "Object Storage," Poland | 22 |
| S3 to Object Storage ratio, US | ~73x |
| US to Poland Object Storage ratio | ~38x |
Skill tags are self-reported, so this measures how people describe themselves, not true skill supply. That's exactly the point. People tag the product they used every day. A posting for a product that competes with S3 will describe the category instead: object storage, S3 compatibility, egress, multi-region data placement. Recruiters search with the posting's words, and in Refolk's index a search for "Object Storage" returns 842 US profiles, not 61,700, even though thousands of the S3 people could do the job.
Rewrite your bullets in the product's terms
Keep the work you did and change the frame around it. Square brackets mark the places for your real numbers, and if you don't have the number, leave the claim out.
| Before (tool words) | After (DBX Agent Cloud words) |
|---|---|
| Managed S3 buckets for ML training data | Ran S3-compatible object storage for ML training data across [N] regions |
| Reduced the AWS bill | Cut cross-cloud egress spend [X]% by moving GPU-side reads closer to compute |
| Built file upload features | Built an upload and content-processing pipeline handling [N] objects per day |
| Moved data between storage providers | Migrated [N] TB to S3-compatible storage with no client code changes |
Do this for each posting. A Dropbox infrastructure role and a Dropbox connectors role need different lead bullets drawn from the same history. That translation is the work Refolk takes off your hands: paste the DBX Agent Cloud posting and get your own resume back with your real experience described in the posting's vocabulary, with no invented projects. Then run the result through an ATS resume checker to confirm "object storage" and "S3-compatible" come through the parser as plain text.
The applicant who writes "S3-compatible object storage" is speaking the deal's language. The one who writes "S3" is describing a vendor.
Egress cost is the new headline metric
Tigris's main pitch is that it charges no egress fees, so any result where you cut data-transfer costs matches the product's pricing story directly. If you have that bullet, put it near the top.
Amazon S3 users often pay egress fees when their compute runs outside AWS. That's the setup Tigris is built for: it sells to AI developers, and its named customers, Railway, Runpod and Replicate, are developer platforms. The category is contested, too. Wasabi, a competitor, raised $70 million in equity in 2026.
People who often have an egress story without knowing it:
- FinOps analysts who tracked the data-transfer line on a cloud bill and brought it down.
- Data engineers who moved pipelines to cut cross-region or cross-cloud reads.
- Platform engineers who set up caching or replication to keep traffic inside one network.
- ML infrastructure engineers who moved training data next to rented GPUs.
Write it as a baseline, the action you took, and the result: monthly transfer spend before, what you changed, and the dollar or percentage drop after. A hiring manager selling "no egress fees" will understand that bullet in a few seconds.
Where are the new infrastructure roles posting?
Some of them are in Poland, where the tagged talent pool is tiny. Dropbox postings dated Nov. 18 and 19 include an Infrastructure Software Engineer, Orchestration role in Poland, and in Refolk's index Poland has just 22 profiles tagged "Object Storage," about 38 times fewer than the US.
The US side is hiring too. A Senior Security Engineer, AI Security posting covers Dropbox's AI and agentic infrastructure, including cloud infrastructure, Kubernetes and data stores. It's remote US at $190k to $289k, which you can compare against engineering salaries in the United States. Security engineers should lead with data stores and Kubernetes, not endpoint or compliance work, because those are the systems the role says it protects.
Back to Poland: tagging yourself by category is rare everywhere, so the real pool is bigger than 22 profiles, but it is still small. For a well-targeted applicant in or near that market, the competition for these roles is lighter than the Dropbox name suggests, and the category rewrite above matters even more.
Who will read your application now?
Probably people closer to Tigris than to the legacy sync organization. The CTO leaves the day after the deal closes, and DBX Agent Cloud is built on what the Tigris team made, so its founders likely have more say over hiring for the new product than an acquired team usually gets.
That changes what you name. In a cover letter or a direct note, refer to the product's actual customers (Railway, Runpod, Replicate) and its developer-platform focus, not Dropbox's consumer sync features. One specific sentence about why S3 compatibility matters to a team running compute outside AWS does more than a paragraph about loving Dropbox since college. If you can find the hiring manager, follow the hiring manager direct note run and keep the note to the product, your one matching result, and a question.
Refolk drafts that cover letter from the same posting and gives you a fit score first. If the score shows you only match the legacy side of the business, you learn that before you apply, not after the rejection.
If you were one of the 200 and your work was on the side that lost funding, the same principle applies in reverse: bullet the capability, not the product name. "Sync conflict resolution for 10-year-old clients" ties you to the legacy product. "Consistency guarantees across distributed storage" describes work a storage business needs.
FAQ
Is Dropbox hiring after the layoffs?
Yes. Postings dated Nov. 18 and 19, right after the Tigris deal closed on Nov. 17, include an infrastructure orchestration role in Poland, and a remote US AI security role pays $190k to $289k. Total counts differ by board: Built In NYC listed 16 Dropbox openings in total, other boards showed 9 to 41, and none of those is a weekly hiring figure. Read titles and posting dates rather than trusting one number.
I've only used Amazon S3. Can I write "object storage" on my resume?
Yes. S3 is object storage, so writing the category is accurate. Keep "Amazon S3" in your skills list for keyword matching and use "S3-compatible object storage" in the bullets that describe the work. Don't claim experience with other storage systems you haven't run.
Is it risky to join a company right after a layoff?
It's riskier to join the team the layoff was taking budget away from. Dropbox's numbers show strong cash flow, a flat core business and a new product funded with about a quarter's worth of free cash flow. Aim for roles attached to that new product, and ask in the interview which team's budget the req comes from.