Turn a manager-return ask into a promotion case

You get a message that sounds like a compliment: the company wants to know if you would run a team again. If you have already absorbed the coordination work after a flatter reorg, the instinct is to say yes. Pause. The question is whether the organization is ready to reopen a rung, not whether you are willing to do more.

Meta has reportedly walked back part of its flatter-team push by asking certain Applied AI individual contributors to take on management duties again. About 7,000 retained Meta staff were placed across four designated AI efforts, with Applied AI the biggest. On September 11, Meta started soliciting interest from Applied AI individual contributors about leading teams once more. The process was opt-in, with no reassignment. A number of Applied AI individual contributors now being asked to return to management had earlier occupied managerial roles before their transfer into the unit.

Meta's preference for fewer managers traces to CEO Mark Zuckerberg's 2023 Year of Efficiency message, in which he said a flatter structure might move faster. In May 2026, Meta cut about 10% of its workforce, roughly 8,000 employees, and scrapped plans to fill 6,000 open positions.

The opt-in is a probe, not a promotion

A company that has flattened a team and then asks a contributor to run it again is testing whether the org chart can be repaired without a formal level. It is also testing whether you will accept the work before the terms. Ask what the company is actually offering before you say yes.

Before you write anything, find out who makes promotion decisions, who owns the org chart, and who controls the budget. A promotion case that skips those people is a nice story, not a plan. You need to know whether the ask will be handled by your manager, a skip-level, a people team, or a finance partner. The answer changes the shape of the case. The human part is simple: you may be tired, proud, and unsure at once. That does not make the ask bad. It makes the terms important.

Build the rung-back case before you answer

Answer the opt-in with a short memo rather than enthusiasm. The memo should show that the coordination work is real, durable, and attached to a level the company can fund.

• Is the coordination work durable? List the recurring work you already do: staffing, planning, escalation, cross-team dependencies, performance conversations, and hiring support. Include dates, frequency, and the people affected. When the work disappears after a manager returns, treat it as a gap you filled, not a promotion case.
• Is the span documented? Count the people, projects, or workstreams that depend on you, and how often. A useful table covers direct reports, dotted-line owners, stakeholders, and the cadence of coordination. A span of control measures the human and technical complexity you are carrying, rather than a title.
• Is there headcount or dual track? Ask whether the company is reopening a manager headcount, creating a dual-track senior IC role, or simply asking you to absorb a manager's work without a level change. A named path is a manager requisition, a senior IC promotion, or a written scope change with compensation. Do not accept a vague answer as headcount; that is how a promotion case becomes a temporary scope trap.
• What title or scope are you asking for? Name the level you are asking for, the scope it covers, and the date you expect it to be effective. A clear ask is a manager role with a direct span, or a senior IC role with coordination scope and a corresponding level. When the company cannot name the rung, treat the arrangement as borrowing, rather than promotion.
• What evidence shows the org needs the rung? Show why the organization needs the rung, not just why you want it. Point to repeated escalations, missed deadlines from unclear ownership, hiring gaps, or a project that stalled because no one owned the seam. The evidence should point to a structural need, rather than personal ambition.

Make the ask concrete enough to survive a budget meeting

A promotion case succeeds when it sounds like a staffing decision rather than a favor. Put the level, the scope, and the funding path in the same sentence. If you are asking for a manager role, name the direct span and the reporting line. If you are asking for a senior IC role, name the coordination scope and the level that matches it.

Keep the conversation on the job. You are showing that the organization has already created a job and is asking you to formalize it, rather than proving you are ready for more. If the company wants the work but lacks the rung, say so plainly. You can still do the work, but the title should exist in the org chart, not only in a chat thread.