RefolkCandidates
10 min read

Uber Cut "Manager of 2" in Half: The Small-Span Resume Fix

Uber's September 2026 cuts halved teams of 1-2 reports. Here's how small-span managers rewrite their resume for a 4.2x larger senior IC market.

On September 2, 2026, Uber told 3,300 people they were done, roughly 10% of the company. Buried in the memo was the line every middle manager should have screenshotted: teams with one or two reports were cut by nearly half, and anyone sitting seven layers from Dara Khosrowshahi got trimmed by 20%. If your current title says "Manager" and your team fits in a two-top at a diner, your resume needs surgery this week.

Why "Manager of 2" flipped from promotion to red flag

Small-span manager roles are being deleted on purpose across tech, and recruiters have been trained to read the pattern. Uber's own language named "more layers, more coordination, more fragmented ownership" as the problem, and Khosrowshahi's fix was to halve micro-teams of one to two reports and cut mid-hierarchy employees by 20%. That is not an Uber quirk. Around 41% of employees told Korn Ferry their companies trimmed management layers last year, and Live Data Technologies clocked manager headcount down 6.1% between May 2022 and May 2025.

The pattern in 2026 memos is remarkably consistent:

  • Uber (Sept 2, 2026): 3,300 cuts, micro-teams halved, seven-layers-deep cut 20%.
  • GitLab (June 3, 2026): 350 workers gone (14%), flattened to five layers below CEO and COO, floated "one-person teams" combining eng, design, and product.
  • Coinbase: Brian Armstrong hard-capped management at five layers below the CEO.
  • Cloudflare: After ~20% cuts, Matthew Prince labeled the departed "measurers" (middle management, finance, legal, internal audit, revenue rec).
  • Amazon (Oct 2025): ~14,000 corporate cuts, framed by Andy Jassy as removing layers, not cost.

When five of the loudest engineering cultures on earth publish the same restructure playbook in twelve months, a resume line reading "Engineering Manager, 2 reports" is not neutral. It maps directly onto the layer everyone is deleting.

41%
of employees say their company trimmed management layers last year

Korn Ferry surveyed 15,000 professionals worldwide. Middle management is now the default cost center.

The 4.2x rule: where the actual jobs live now

The IC market is 4.2 times larger than the entry-manager market, so a small-span manager rewriting toward senior IC is moving into a bigger pond, not settling. In Refolk's index of U.S. tech professionals, roughly 229,800 people currently hold a Senior, Staff, or Principal IC engineering title. Only about 54,300 hold an entry-level Engineering Manager title. The layer above that, Director of Engineering and senior EM, is a mere 21,200 seats, meaning the promotion funnel from small-span manager to Director is a 2.6-to-1 squeeze at the exact layer being cut first.

SegmentCountNote
Senior / Staff / Principal ICs229,823Refolk's index of U.S. tech titles
Engineering Managers (entry-level manager)54,311Refolk's index
Director of Engineering / Senior EM21,178Refolk's index
Senior ICs per entry manager4.23xDerived, 229,823 / 54,311
Entry managers per Director slot above2.56xDerived, the promotion bottleneck
Manager headcount change, May 2022 to May 2025-6.1%Live Data Technologies via WSJ

The mechanism matters. Companies did not decide managers were bad people. They decided the layer between a Director and a Staff engineer stopped paying for itself once tooling, AI code review, and async docs took over the coordination work a small-span manager used to do. That is why Uber, GitLab, and Coinbase all landed on the same number of layers (five below the CEO) within a few months of each other. If your role's job was to be a human coordination protocol for two people, the market has replaced you with Slack, Linear, and a Cursor subscription.

The player-coach reframe, done as math

The player-coach resume works because it moves you into the senior IC market that is 4.2x larger than the manager market you are leaving. Player-coach is a role where you ship your own individual work (code, designs, analyses, campaigns) while also mentoring one to three teammates. It is the honest description of most small-span manager jobs anyway; the difference is which noun you lead with.

Take a real line and rewrite it three ways:

Original (2024 register): Engineering Manager, Payments (2 reports). Managed team roadmap and quarterly planning.

Weak rewrite (still manager-first): Engineering Manager, Payments. Led team of 2, delivered Q3 roadmap, ran 1:1s and performance reviews.

Strong rewrite (IC-first player-coach): Tech Lead, Payments. Shipped idempotency layer processing $180M/quarter; mentored 2 engineers through their Staff promotions; owned on-call for 4 services.

The strong version leads with a system you shipped and a dollar figure you owned. The mentorship is a parenthetical, not the headline. This is exactly the rewrite work Refolk does automatically when you paste a Staff Engineer posting: it pulls the systems and outcomes out of your history, moves them to the front of every bullet, and demotes the org chart language a 2026 hiring manager reads as "will be cut in the next reorg."

What to strip

  • Report counts under 4 in the title line. Put them in a bullet, or omit.
  • "Managed" as the lead verb. Replace with the verb of the work: shipped, wrote, designed, ran, migrated.
  • Layer signals: "reported to Director who reported to VP" and org-chart trivia. Describe scope by outcome and cross-functional partners.
  • Ceremony work: "ran weekly team standup" reads as measurer, not maker.

What to add

  • One dollar or user figure per role. Revenue owned, cost saved, users served, latency cut.
  • One system or artifact you personally shipped. Not "the team shipped."
  • One cross-functional radius: how many teams consumed your work, not how many people reported to you.
  • Mentorship as a verb, not a title: "mentored 2 engineers through Staff promotion" beats "managed 2 direct reports."
A resume line reading "Manager, 2 reports" now maps onto the exact layer every 2026 memo names as the cut.

The Uber precedent gives you cover for "Manager to IC"

You can honestly name the industry pattern in your cover letter, because Uber has already trained hiring managers to read a voluntary IC pivot as strategic, not a demotion. Uber's own memo said management ranks would shrink 20% and some of those affected would move into IC roles inside the company rather than leave. When Uber is producing its own wave of Manager-to-IC transitions on the record, your framing writes itself.

The cover letter move: name the pattern in one sentence, then pivot to the work. Something like: "Uber, GitLab, and Coinbase have all flattened to five layers this year, and the strongest work I've done in the last two years has been hands-on system design, not coordination. I'm optimizing for the IC track this cycle." That is a sentence a hiring manager can forward to their skip-level without embarrassment.

The five traps that mark you as a "measurer"

The word Cloudflare's Matthew Prince used, "measurer," is the exact signal to scrub from your resume, because it names the layer of middle management, finance ops, and internal audit that 2026 restructures are targeting first. Five specific resume patterns leak measurer energy:

  1. Meeting cadence as an accomplishment. "Ran weekly team standup and biweekly retro." Delete. A hiring manager cannot tell if you shipped anything.
  2. Process artifacts as deliverables. "Introduced RACI matrix across 3 teams." Only include if it saved measurable time or shipped a product; otherwise it reads as coordination theater.
  3. Report count over 1 and under 4 in the headline. The exact micro-team size Uber halved. Move it to a bullet or omit.
  4. Deep-hierarchy tells. Listing your manager's manager, or describing your team as "one of 14 pods in the platform org." That is Uber's "seven layers from the CEO" resume, self-selecting into the cut pattern.
  5. "Owned team roadmap" without a shipped outcome. Roadmaps are inputs. Ship dates, latency numbers, and revenue are outputs. Lead with outputs.

Replace each with a maker verb and a number. "Ran standup" becomes "shipped v2 auth in 6 weeks with 2 engineers." "Owned roadmap" becomes "shipped 11 of 12 committed features; cut p95 latency 340ms to 90ms."

When to keep the manager title and target the 21,200 Director slots

Keep the manager title only if you can credibly stretch to Director of Engineering, because the entry-manager layer is a 2.6-to-1 funnel into a shrinking 21,200-seat market. Director roles survived the 2026 flattening better than mid-manager roles because someone still has to run a five-layer org. If your last role had 8+ reports across 2+ teams, a budget you owned, and cross-functional partners named in your calendar, the Director rewrite is real.

The Director resume looks different from both the small-span manager and the player-coach:

  • Headline scope in headcount and budget: "Led 14-person platform org, $4M infra budget."
  • Business outcomes, not systems: "Cut cloud spend 22% while doubling deploy frequency."
  • Named cross-functional partners at Director level: "Partnered with Director of Security, Head of Data on GDPR migration."
  • Hiring receipts: "Hired 6, promoted 3 to Senior, 1 to Staff."

If your reality is 2 reports and no budget, do not fake the Director rewrite. The player-coach path into the 229,800-seat senior IC pool is a bigger and safer market. Refolk scores how well your history actually fits each posting before you apply, which is the check that keeps you from wasting three weeks aiming at Director reqs a recruiter will reject on the first screen.

The pipeline pitch, for the interviews you do get

The strongest thing a small-span manager can say in an interview right now is that they are pre-built leadership pipeline the market is quietly running out of. Companies eliminating middle managers in 2026 are dismantling the apparatus that produces senior leaders in 2028. You have already done the reps: hired, fired, coached, run reviews. You are offering to IC now and re-scale later, on their timeline.

That is a narrative a smart hiring manager can defend to their VP, because it is true and because the alternative (hiring a pure Staff IC and hoping they grow into leadership in three years) is more expensive and slower. Say it out loud in the closing minute of the final round: "I've done the manager reps. I want to build for two years, then scale a team again when you need it." That is the sentence that turns a Manager-to-IC pivot into a hire.

FAQ

Should I remove my manager title entirely from my resume?

No, but reframe it. Keep the title accurate (lying is not the fix) and change the noun order. "Engineering Manager / Tech Lead" reads honestly for a 2-report role and lets an ATS match on both queries. Then rewrite every bullet under it to lead with a system, a number, or a shipped artifact, not with report count or ceremony. If the role was 90% IC work and 10% coordination (which most 2-report manager jobs actually are), "Tech Lead" is the truer title anyway.

What if I never coded and I was purely a people manager of a small team?

The player-coach reframe still works if you shift the "player" verb to your function: campaigns launched, analyses shipped, contracts closed, hires made. A marketing manager with 2 reports rewrites as "Senior Marketing Lead, ran ABM program that sourced $2.1M pipeline; mentored 2." An ops manager rewrites as "Senior Ops Lead, shipped billing migration cutting 14 hours/week; mentored 2." The pattern is: individual output first, mentorship second, report count buried or gone.

How honest do I have to be about my report count in interviews?

Total honesty at the phone screen, because it will come out in reference checks and it is a small industry. The framing move is not to hide the number, it is to change what the interviewer measures you by. When asked "how big was your team," answer "I had 2 direct reports and 6 cross-functional partners I shipped with weekly, including PM, design, and data." You are redirecting from headcount to impact radius, which is the metric flat orgs actually hire on.

Is this a permanent shift or will manager roles come back?

The layer is not coming back at the same ratio. Even if the economy recovers, the tooling that killed middle management (AI code review, better project software, async-first docs) is not getting worse. Live Data's 6.1% manager-headcount drop from 2022 to 2025 is the floor, not the bottom. Bet your resume on the IC track for the next two years, and re-scale into leadership when a company you want to work at is genuinely growing headcount, not just backfilling a flattened chart.

Put this to work

Paste your career in once. Every application after that is written for you.

Drop a resume or a LinkedIn URL. I rank the live openings against it, rewrite the resume and write a cover letter for the best of them, and fill in the employer's form when you press the button. You read, you decide what goes out.

  1. 01Drop your resume

    A PDF or a LinkedIn URL. About a minute, once.

  2. 02I rank the openings

    Every weekday morning, the live catalog scored against your history. Up to 20 worth your time, not two hundred links.

  3. 03Each one is written up

    Resume rewritten for the posting, a cover letter, a fit score. Press send, or let me fill in the form.

  • New matches ranked and written before you are up.
  • Every bullet stays inside what your history supports. Nothing invented.
  • Queued, submitted, interviewing, offer: one screen, not a spreadsheet.

500 free credits on sign-up. No card. Nothing is sent until you say so.

Keep reading