Uber's 7-Layer Cut: Rewriting the Middle-Manager Resume

On September 2, 2026, Uber told 3,300 people they were out and told every other hiring manager in tech exactly what shape of middle manager to stop hiring. If you ran a two-person team at a company with a Director reporting to a Senior Director reporting to a VP, your resume now matches a public rubric for "cut this."

The rewrite is not cosmetic. It is a reframe of span, depth, and ownership before the next reviewer pattern-matches you to the Uber memo.

What Uber actually cut, in the language recruiters will now use

Uber eliminated about 10% of its global headcount, shrank its manager ranks by 20%, halved teams of one or two people, and removed employees "more than seven layers down from the CEO." Those four phrases are now screening vocabulary at every flat-org company your resume will land in.

The specifics, from the September 2 memo and Bloomberg's reporting:

• 3,300 jobs cut, roughly 10% of global headcount, dropping Uber below 30,000 employees from about 34,000 at year-end 2025.
• Manager ranks down 20%, with some former managers reassigned as individual contributors rather than exited.
• "Micro-teams" of 1 to 2 people cut by about 50%, named explicitly as a target.
• Employees "more than seven layers down from the CEO" eliminated as a category.
• Less than 1% of staff allowed to work remotely going forward.

CEO Dara Khosrowshahi framed it as flatness, not AI: "more layers, more coordination, more fragmented ownership, and in some cases structures that made sense when businesses were smaller but no longer serve us well at our current scale." That sentence is now a lexical blacklist. Any bullet on your resume that echoes "coordinated across," "aligned stakeholders," or "liaised with" reads as the exact overhead he just removed.

Why "managed a team of 2" is now the most dangerous bullet on your resume

A bullet that says "managed a team of 2" tells a reviewer you were running a 33% management ratio inside your own group, which is the precise bloat signal flat orgs are deleting. World-class orgs run management ratios between 12% and 18%; bloated ones sit between 25% and 35%, and Uber just drew that line in public.

Span-of-control benchmarks make the problem concrete. The modern baseline for employees per manager is 15 to 20. The traditional model, the one being cut, is 5 to 6. A two-report team is below both. Org analytics tools now flag "managers with 2 or fewer direct reports" as a layer-bloat indicator by default, and recruiters at Meta, Google, and Datadog (all of which have flattened between 2024 and 2026) have internalized the same metric.

The fix is not to inflate the headcount you managed. It is to describe scope the way a flat org measures it:

• Combine direct and dotted-line reports into one span number. "Led 2 direct reports and 7 cross-functional contributors across platform and growth" reads as a 9-person surface area, not a 2-person team.
• Name the deliverable, not the headcount. "Owned the pricing experimentation stack used by 140 PMs" is a span statement without a reporting-line number at all.
• Lead with the business metric the group moved. "Cut activation latency 38% and shipped the rewrite in two quarters" is span-of-control bullet writing without a single org-chart word.

This is grinding work to do by hand across 15 or 20 bullets. It is also the exact rewrite Refolk does from your own history: paste the job posting, get a resume back that reframes your scope in the vocabulary the posting is using, not the vocabulary your last org used.

How to erase "7+ layers from the CEO" from your resume

Depth-from-CEO is now a resume feature, not just an org fact, and most middle-manager resumes volunteer it in the first three lines. If your bullet reads "reported to Director of X, who reported to Senior Director of Y, who reported to the VP of Z," you have self-disclosed being four layers deep before the reviewer has read a verb.

Rewrite depth into altitude by naming the executive your work actually reached, not the manager you reported to:

1. Replace the reporting chain with the review audience. "Presented quarterly to the CFO and GM, Mobility" beats "reported to Senior Director reporting to VP."
2. Name the forum, not the manager. "Owned the biweekly readout to the Product Operating Committee" tells a reviewer you were in the room where decisions were made.
3. Delete middle-tier titles from your prose entirely. "Director" and "Senior Director" in your bullets anchor you two to three layers deep by implication. Replace with the function ("Finance leadership," "the GM team") or the outcome.
4. Lead the role summary with scope, not title ladder. "Owned P&L for a $42M line" sits at a different altitude than "Senior Manager reporting to a Director of Operations" even if both describe the same job.

The verbs to replace coordination verbs with

Khosrowshahi's phrase was "more coordination, more fragmented ownership." Your resume probably runs on coordination verbs because that is how middle-management work actually feels. Trade them out:

The right side is not more honest than the left. It is a different author voice: the person in the room making the call, not the person scheduling the room.

The manager-to-IC pivot is oversupplied 2 to 1

If your plan is "Engineering Manager to Staff Engineer," you are entering a market that is roughly twice as crowded on the supply side as the demand tier you are targeting. In Refolk's index of US profiles, there are about 108,000 managers at Engineering Manager, Senior Manager, and Group PM altitude, against about 51,500 Senior and Strategic ICs at the Staff and Principal tier. That is the pool Uber-style flattenings are now pushing into a smaller funnel.

Here is the comparison table reviewers will not show you, but recruiters are already using:

The practical read: a straight manager-to-IC pivot without recent technical artifacts (commits, design docs, a shipped service you personally wrote) will stall. If you have been out of the IDE for three years, say so and compete for Group PM, Director of Engineering, or Head of Platform roles where the manager pool is thinner at the top, not the bottom.

Where Uber manager alumni actually land

The realistic landing pads for Uber's cut cohort are the flat-org tech companies that have already run the same exercise, concentrated in the Bay Area. Refolk's index shows Datadog, LinkedIn, eBay, Google, Databricks, and Meta as the top current employers of US engineering managers at this altitude, and Waymo is a natural pull for anyone on the autonomy side of Uber.

A few patterns worth naming:

• Meta, Google, and Datadog have publicly flattened between 2024 and 2026, which means the manager-ratio bar is higher there than it was two years ago. Your resume has to clear the same bar Uber just drew.
• Waymo is the direct competitor Khosrowshahi named in the restructuring context ("Waymo, Tesla, and Chinese rivals scale robotaxi fleets"). Autonomy PMs and EMs leaving Uber have a short, warm commute to the exact team pressuring their old employer.
• LinkedIn and eBay run older, broader manager layers than the AI-era companies, and are more forgiving of a 2-report bullet, but still want ownership verbs in the top third of the resume.

The posting language is different enough across these companies that a single master resume will underperform. The Datadog posting asks for different span signals than the Waymo one; the Meta role wants a different review-audience phrasing than the Databricks one. Rewriting bullets per posting is the actual bottleneck for a middle-manager job search.

Three fixes to make today, before the next application goes out

Open your current resume and change these three things before you send another application. Each takes under 30 minutes and each addresses a specific signal the Uber memo made famous.

1. Delete every instance of "team of 2" or "team of 3" from your bullets. Replace with combined span (direct + dotted-line + cross-functional) or with the deliverable the small team shipped. If the team really was two people, say "two-engineer strike team that shipped X in six weeks" so the small size reads as deliberate speed, not permanent structure.
2. Rewrite your role summaries to name a skip-level, not a reporting chain. One line, at the top of each role: who the work was presented to, what decision it enabled, what the business outcome was. No "reported to."
3. Drop "Remote" from your location field if your last job was at an RTO-heavy company. With Uber down to under 1% remote, reviewers at other RTO employers will assume your departure was the remote preference, and will filter accordingly. Lead with a city. Negotiate location after the offer.

If you want to see what this looks like against a specific posting rather than in the abstract, Refolk will score your current resume against the posting and show you which bullets are reading as "layer" and which are reading as "owner" before you hit submit.

The Uber memo was not just a layoff announcement. It was the clearest public specification yet of what middle-management work looks like when it is being deleted. Rewrite before the next reviewer reads your resume with that spec in hand.

FAQ

Should I remove my Uber tenure from my resume to avoid the association?

No. Uber on your resume is a brand asset, especially for roles at Lyft, DoorDash, Instacart, Waymo, and the broader marketplace and autonomy ecosystem. What you remove is the shape of the role, not the employer. Rewrite the bullets to lead with ownership verbs and skip-level audience, drop the "team of 2" phrasing, and let the Uber logo do its own work. The association reviewers will make is "ran real scope at a hard company," not "was the layer that got cut," as long as the bullets back it up.

Is the manager-to-IC pivot worth attempting at Staff Engineer level if I have not shipped code in two years?

Usually not as a first move. The IC market at Staff and Principal is already about half the size of the manager pool it would be absorbing, and hiring loops at that tier screen hard for recent technical artifacts (commits in the last 12 months, a design doc you personally wrote, a service you own on-call for). A better first move for most middle managers is a lateral to Group PM, Director of Engineering, or Head of Platform at a company with thinner top-of-stack management, where your scope reads as strength rather than overhead.

How do I describe cross-functional work without using the word "coordinated"?

Describe the decision, not the choreography. "Chose Vendor A over Vendor B after a six-week evaluation across security and finance" is cross-functional work written as ownership. "Coordinated the vendor selection across security and finance" is the same work written as overhead. The test: can the reader name who made the call? If the answer is "the committee," rewrite until the answer is "you."

Does this change if I was a people manager in finance, legal, or operations?

The verbs and the span fix carry over directly; the benchmarks shift. Operations and finance orgs run tighter spans historically (6 to 10 reports is normal, not bloat), so a four-report bullet is less damaging there than in engineering. The depth-from-CEO fix still matters, because the review-audience framing (CFO, GC, COO) is even more legible in those functions than in tech. Rewrite scope using the deliverable and the executive audience, and the function will take care of itself.