Tag: 인스타그램

  • Meta’s 60% Cut in 90 Days — The Reversal Reuters Traced Through Zuckerberg

    Meta’s 60% Cut in 90 Days — The Reversal Reuters Traced Through Zuckerberg

    Key Summary

    • According to Reuters, Meta drew up an internal plan around January 2025 to reduce its existing team size by up to 60%.
    • The means were layoffs and workforce reassignment, premised on the assumption that AI would keep the productivity of a smaller team at the previous level.
    • HR projected the plan’s effect, though the original reporting did not disclose the specific figures.

    Analysis

    Table of Contents

    In January 2025, the Meta 60% cut plan written into internal documents was scrapped in less than 90 days. Under the premise that AI would fill the resulting gaps, layoffs and workforce reassignment were pushed forward simultaneously. Ultimately, CEO Mark Zuckerberg himself reversed this attempt, as reported by Reuters.

    Before diving in, one point is worth flagging. The assumption that “AI preserves productivity” is not grand philosophy; it is something teams that have already adopted AI coding tools feel to some degree. Where Meta went wrong was drawing a straight line from that assumption to a “60% cut” number.

    Meta 60% Cut: The Plan That Began in January 2025

    According to Reuters’ reporting, Meta drew up an internal plan around January 2025 to shrink its existing engineering organization by as much as 60%. The means were two-pronged: layoffs and workforce reassignment. HR projected the effects, and the premise was explicit — that AI tools would keep a smaller team’s productivity at the prior level.

    What stands out at this point is the weight of the “premise.” A 60% cut should have been a destination, not a starting point. Meta should have first measured the productivity AI could actually preserve, then decided the size of the cut. Meta reversed that order.

    The Background of the Reversal and the Lingering Aftermath

    Zuckerberg ultimately reversed the plan. But the reversal did not return teams to their prior state. The company was left carrying the aftermath of crushed morale and a “mercenary” organizational culture. Three groups — teams that had been told layoffs were coming, teams slated for reassignment, and the teams that remained — were now operating side by side inside the same company.

    The word “mercenarization” may sound like an exaggeration. Yet in any organization where the perception “I could be cut tomorrow” has taken hold, asking people to commit to long-term investment is nearly impossible. Codebase improvements, technical debt cleanup, onboarding new hires — these tasks generate no immediate revenue, so they are the first to be neglected.

    What the Instagram Zero-Authentication Flaw Revealed

    Gergely of The Pragmatic Engineer newsletter pulled in Instagram’s “zero-authentication password reset” flaw as a symbolic case for this situation. His analysis was that simply asking an AI bot to change an email on the account was enough to take over any account, including that of former U.S. President Barack Obama. On the surface it looks like a technical bug, but in this writer’s view it is a warning shot of quality degradation produced by the collapse of the workforce structure.

    When there are not enough people responsible for maintenance, security flows inevitably collapse in this way. AI can generate code, but it cannot stand in for accountability. Someone has to hold “what zero authentication means” and “how this path is used” in their head. The Pragmatic Engineer’s analysis of the Meta 60% cut pinpoints exactly this issue.

    Implications for Workforce Reshuffling at Other Big Tech Companies

    Once the Meta 60% cut attempt became public, similar discussions at Amazon, Google, and Microsoft came under scrutiny. Microsoft publicly referenced its AI tool usage in 2024, hinting at a workforce reshuffle. Amazon is on a similar trajectory. The Meta episode is a warning that the simple equation “AI = labor replacement” does not operate cleanly in practice.

    It is time to question how far executive confidence in AI actually holds. Three Questions on GPT-6 and Astra — How Far Does OpenAI’s Confidence in Declaring an “AGI Era” Really Go? offered a similar lens.

    Category Meta’s Approach An Alternative Approach
    Order of cut decisions AI assumption → 60% cut Measure AI productivity first → gradual cut
    HR projection Project effect after the cut Grounded in pre-pilot results
    Team operations Run sacrifice, waiting, and remaining groups in parallel Hold size constant + adopt tools
    Quality control Assume natural decline with fewer people Pair with automated code review and testing
    Cost of reversal Trust costs not accounted for Estimate reversal costs in advance

    As the table shows, the core difference is the order. Does AI adoption come first, or does the cut? Once the order flips, the team’s reaction changes completely.

    The Balance Practitioners Should Watch

    The most meaningful takeaway from this episode, from a practitioner’s perspective, is that organizations need to define what AI cannot replace before defining what it can. Code generation, test case writing, document drafts — replaceable. System design judgment, security path review, user trust accountability — hard to replace.

    The Meta 60% cut case was ultimately a problem of accountability structure, not numbers. Before introducing a tool, redraw who owns the responsibility. Skip that order, and the failure surfaces as a security flaw like the one on Instagram.

    Key Issues at a Glance

    1. The gap between the cut premise and actual measurement. Meta set 60% on the premise alone that “AI will preserve productivity.” Actual measurement data should have come first.

    2. Cost of reversal. A cut that has been announced once leaves trust costs behind even when reversed. These costs do not show up in HR metrics.

    3. Limits of automating security and trust paths. Authentication, payment, and personal-data flows can be supplemented by AI, but accountability must remain with people.

    4. Other big tech’s recalibration. The Meta case is directly referenced in workforce reshuffle discussions at Amazon, Google, and Microsoft.

    What to Do Right Now

    • Draft a written list for each team of “decisions AI can replace” versus “decisions people must own.”
    • If cuts are on the table, demand at least three months of pilot results. A cut without a pilot is a bet.
    • Explicitly define new roles for the remaining staff (AI tool operations, prompt curation, quality ownership).
    • Assign an owner at the single-line-of-code level for every authentication, payment, and personal-data flow.
    • Audit weekly whether the decision structure still allows reversal. A cut that has been announced once leaves the organization with a recovery bill.

    Frequently Asked Questions

    Was the Meta 60% cut actually carried out?

    No. Zuckerberg personally reversed the plan at the planning stage. However, personnel anxiety had already spread across the organization in the process.

    Can AI really replace the work of one engineer?

    Partially, yes. Boilerplate code, test automation, and document drafts are tasks AI can handle. System architecture decisions, security review, and user trust accountability still need a person in charge.

    Are other big tech companies trying something similar to Meta?

    Meta is the only company to publicly cite a figure in the 60% range. However, there have been multiple instances in which Amazon, Google, and Microsoft hinted at workforce reshuffles under the banner of AI tool usage.

    Is the Instagram zero-authentication flaw causally linked to the Meta 60% cut?

    The Pragmatic Engineer analyzed the flaw as a signal of the organizational turmoil created by Meta’s 60% cut attempt. It is hard to assert a direct causal link, but the timing does overlap.

    Source Material

    This article was written after reviewing the following original source: The Pragmatic Engineer — The Pulse: Meta wanted to reduce teams by 60% because of AI