If you managed people and just lost your job in a restructuring, your next role will probably sit in a flatter org that wants one person to build things and lead people at the same time. A resume that opens with "managed a team of 8" answers a question those companies no longer ask.
PepsiCo North America is the latest example. CEO Ram Krishnan's Nov 9 memo announcing about 1,000 job cuts says the company has "opportunities to simplify our structures, clarify accountability and make decisions faster."
What PepsiCo's memo actually tells laid-off managers
PepsiCo's memo points to a structural cut aimed at unclear accountability, and the hiring that follows rewards managers who owned outcomes, not managers who routed work. None of the coverage quotes the memo using the phrase "management layers," so the delayering is an inference. But "simplify structures," "clarify accountability," and "decide faster" are the standard language of it. Delayering means removing levels of management between the front line and the top, so a decision passes through fewer hands.
Krishnan also wrote that PepsiCo needs "to be faster, more connected, and more capable, while continuing to invest in growth." Bloomberg quoted the memo saying too much of how the company works "remains complex and fragmented." The business backdrop: North American beverage volume shrank 2% in the third quarter, and convenient foods volume was flat. The company had roughly 306,000 employees globally at the end of last year, about 125,000 of them in the U.S.
When a company says accountability is unclear, it means too many people stand between a decision and the person who owns it. A manager whose main value was routing work (status meetings, handoffs, escalations) is exactly the layer being cut. So your resume has to show that you owned work, not that you passed it along.
Why middle managers are the ones getting cut
Middle managers are getting cut because every management layer adds a stop between a question and its answer, and companies are now removing layers at scale. In Korn Ferry's survey, 41% of employees globally and 44% in the U.S. say their organization has eliminated managerial levels. Bloomberg and Live Data Technologies data show middle managers made up roughly a third of white-collar layoffs in 2023, up from about 20% in 2018.
The big names have been doing this for a while:
- Citi: under CEO Jane Fraser, management layers went from 13 to eight, and financial performance clearly improved afterward.
- Uber: under Dara Khosrowshahi, fewer layers and larger teams.
- Bayer: average span of control is now 14 and still rising, and some managers carry 90 direct reports.
Take a layer out and decisions move faster, which is the same promise as "make decisions faster" in Krishnan's memo.
There's an opening here for you, though. Korn Ferry also found that 37% of employees say the lack of managers leaves them feeling directionless. Companies still need direction. They want it from people who also do the work. That's the player-coach: a manager who carries real individual work while leading a small team.
Boeing's cut is not PepsiCo's, and the resume fix is different
Boeing cut for production volume and PepsiCo cut for structure, so the proof each laid-off manager needs is different. If the cut was structural, prove you removed coordination overhead. If demand fell, prove your results held up when it did.
Boeing announced its cut the same day as PepsiCo. Commercial Airplanes CEO Stephanie Pope said, "Adjusting our production schedules and reducing aircraft output puts us in an overstaffed position." That works out to about 2,500 jobs, based on the 50,500 people the division employed at the end of 2025. That's a volume cut. It isn't delayering.
| Cut type | Example | What the next hiring manager worries about | What to bullet |
|---|---|---|---|
| Structural (delayering) | PepsiCo North America | Were you a coordination layer? | Handoffs you removed, decisions you owned |
| Volume (overstaffing) | Boeing Commercial Airplanes | Do your results depend on growth? | Output or margin you held while demand fell |
Mixing these up costs you. A Boeing manager who writes "streamlined team structure" is answering a question nobody asked. A PepsiCo manager who leads with "grew output during expansion" is underlining the exact worry a flat org has about managers who rode volume.
Manager to IC is the bigger market, not a step down
In Refolk's index of professional profiles, there are about 2.7 U.S. Staff or Principal Engineer profiles for every Engineering Manager. A manager who repositions as a senior individual contributor with leadership range is moving into a larger pool, not stepping down.
From Refolk's index of current titles: 116,391 senior IC profiles against 43,151 EMs.
| Segment (US) | Profiles |
|---|---|
| Engineering Manager titles | 43,151 |
| Staff / Principal (Software) Engineer titles | 116,391 |
| Senior IC per EM (derived) | ~2.7x |
| "Player-coach" in headline (all functions) | 5,280 |
| Player-coach headlines as % of EM count (rough, spans all functions) | ~12% |
The mechanism matters more than the ratio. Staff and Principal titles are defined by how far your technical influence reaches, not by how many people report to you. That's exactly the trait flat orgs pay for. A manager-to-individual-contributor resume should lead with technical scope ("designed the event pipeline three teams now build on") and treat leadership as range ("mentored two engineers into tech-lead roles"), not as the headline.
I don't have index numbers outside engineering, but the logic carries. A marketing manager can apply for principal or lead roles. An analytics manager can target staff analyst seats. In both cases, scope beats headcount.
In practice, this means keeping two versions of your history: one framed for manager reqs and one for senior IC reqs, each reworded for every posting. That's the tedious part Refolk handles for you. Paste the posting, and you get your own resume back, rewritten around whichever version of you the job is asking for.
How to show span of control on a resume without inflating it
State your real headcount, then add the context headcount leaves out: budget, number of teams, and how far your influence reached across functions. Span of control is the number of people who report directly to one manager.
Gallup's January 2026 data shows the average span of control rose from 10.9 to 12.1 between 2024 and 2025. That average is misleading. 37% of managers have fewer than five reports, and the 13% who manage 25 or more pull the average up.
The widely quoted 12.1 average is pulled up by the 13% of managers running teams of 25 or more.
So if you had six reports, you were a typical manager, not a small one. Don't pad the number to match a skewed average. Add these instead:
- Direct and indirect reports, separated. "6 direct, 14 total through two team leads."
- Budget or revenue owned. A dollar figure says more about scope than a headcount does.
- Teams you coordinated without authority. "Aligned roadmap across product, finance, and supply chain."
- Decisions you owned outright. Pricing calls, vendor selection, hiring bar, launch go/no-go.
A line like "Led 6 analysts; owned the $4M promo budget and the weekly forecast call for three regions" shows reach without claiming a big team you didn't have. (Use your own numbers. That one is illustrative.)
The player-coach math: pick one shape, not both at maximum
If you claim a huge team and heavy hands-on output in the same role, readers won't believe it, because the span research says one person can't do both at full scale. Pick the shape that matches what you actually did.
McKinsey's guidance puts a player-coach doing complex individual work at roughly 3 to 5 reports. One of Gallup's conditions for large teams to work is a manager who spends less than 40% of their time on individual work. So "Led 15 people and personally shipped the core service" makes an experienced reader doubt one half of the sentence, and possibly both.
The two credible shapes:
- Wide span, backed by systems. You ran a big team because you built the machinery: team leads, operating rhythms, dashboards, a hiring loop. Your bullets name the systems. "Ran a 14-person org through two leads; built the weekly metrics review that cut escalations to me by half." (Swap in your real numbers.)
- Narrow span, heavy hands-on work. You led 3 to 5 people and did serious individual work yourself. Your bullets name the artifacts. "Wrote the churn model; coached 4 analysts to own and extend it."
A flat org is not hiring the person who routed the work. It is hiring the person who owned it.
Most laid-off middle managers fit the second shape better than they realize. If you spent Tuesday afternoons fixing the forecast spreadsheet because nobody else could, that belongs on the page. It isn't something to hide.
Skip the "player-coach" label and show the behavior
Below VP level, leave "player-coach" out of your headline and write bullets that show the behavior instead. In Refolk's index, 5,280 U.S. profiles use the phrase in their headline, and in a 25-profile sample the most common titles were CEO, CTO, CMO, VP, and Head of Growth, not frontline managers. On a mid-level resume, the phrase can read as executive self-branding.
The sample is small, so treat it as a direction, not a share. The direction is still useful. A recruiter scanning a manager's resume sees "player-coach" next to a director title and thinks "founder energy." Next to a first-line manager title, they think "buzzword."
The pattern that works has three parts:
- What you built yourself. A model, a process, a codebase, a campaign, a contract.
- Who you handed it to. A number of people and what they now own.
- What happened. The result, ideally one that held up after you stepped back.
"Built the pricing model; trained 4 analysts to run it; quoting time fell from days to hours" is a player-coach resume without the label. Flat orgs are looking for that kind of proof. Korn Ferry's 37% "directionless" figure is a real problem those companies need solved, and this bullet shows you solve it while still doing the work.
A five-step rewrite for the laid-off manager job search
Rebuild each role around what you built, add reach second, then tailor each application to whether the posting is a pure manager, player-coach, or senior IC seat. Here's the order:
- Diagnose the cut. Structural (PepsiCo-style) or volume (Boeing-style). This decides which proof leads your top role.
- List your artifacts. For your last two roles, write down everything you personally made: documents, models, systems, deals, launches. This becomes the first half of most bullets.
- Add span with context. Real headcount, direct versus indirect, budget, teams coordinated. No rounding up to Gallup's 12.1.
- Choose a shape per posting. A posting that asks for 3 to 5 reports plus hands-on work gets the narrow-span version. A senior IC posting gets technical scope first and leadership as range.
- Check fit before you send. Some "manager" postings in flat orgs are really staff IC roles with one report, and some are pure people management. Applying with the wrong shape wastes the application.
The other drain is volume without response. PepsiCo and Boeing announced their cuts on the same day, so experienced people from both are in the market at once. Polished, senior applications still disappear into applicant systems with no reply, and every silent week makes you second-guess a resume that may be fine.
Whatever channel you use, the resume underneath has to do the same work: show what you built, show how far your reach went, and leave headcount as supporting detail.
FAQ
Will a manager to individual contributor resume look like a demotion?
Not if it leads with scope. In Refolk's index, there are about 2.7 U.S. Staff or Principal Engineer profiles for every Engineering Manager, so senior IC is the larger market, and those titles are judged on reach, not reports. Frame your management years as leadership range inside a senior technical role ("mentored two engineers into tech leads") and lead each role with what you designed or built.
How do I show span of control on a resume if I only had four reports?
State the four, then add context. Gallup puts the median span at five to six, and 37% of managers have fewer than five reports, so four is normal. Add budget owned, teams you coordinated across, and decisions you owned outright. For a player-coach role, four reports plus serious hands-on work fits McKinsey's 3 to 5 guidance exactly.
Should I put "player-coach" in my resume or LinkedIn headline?
Usually not, unless you're a VP or above. Refolk's index has 5,280 U.S. profiles using the phrase, and in a 25-profile sample of them the most common titles were CEO, CTO, CMO, VP, and Head of Growth. Mid-level managers come across better with a concrete bullet that shows the behavior: what you built, who you handed it to, and the result.
How do I know if my layoff was a delayering?
Read the language. PepsiCo's memo talks about simplifying structures and clarifying accountability, which signals a structural cut. Boeing's Stephanie Pope talked about reduced aircraft output leaving the division overstaffed, which is a volume cut. Structural cuts call for bullets about the coordination overhead you removed. Volume cuts call for results that held up when demand fell.