HN Debrief

Ask HN: Are most corporate SWE jobs performative?

  • Programming
  • Management
  • Startups
  • Economics

The post came from a familiar big-company complaint: a few strong engineers seem to move the product forward while everyone else optimizes for optics, and managers appear to spend their weeks in 1:1s that do little for delivery. Most of the comments agreed that this is a real pattern in large companies, but they framed it less as fake engineering and more as what happens when organizations get big enough that coordination, compliance, risk management, and internal signaling become their own full-time workload. Several people pointed to classic bureaucracy dynamics like Pournelle’s Iron Law, Parkinson’s Law, Price’s Law, and the Pareto principle to explain why a minority often drives visible output while overhead expands around them.

If you run or join a larger engineering org, treat recurring meetings and process as tools with a clear job, not defaults. The failure mode is not just bureaucracy, but communication getting routed through rituals instead of solving problems directly.

Discussion mood

Cynical but not nihilistic. Most people accepted that large companies accumulate bureaucracy, promo gaming, and empty rituals, yet many were firm that coordination and 1:1s are necessary at scale when used well.

Key insights

  1. 01

    Good 1:1s are employee-controlled

    The useful version gives the report a reserved slot to ask for feedback, career clarity, prioritization help, or air concerns that are too small for their own meeting. The bad version turns into a weekly status recital or a forced search for conversation topics. A few managers said the cleanest fix is to let reports set the agenda and even cancel when there is nothing to discuss, which makes the meeting a safety valve instead of a ritual.

    If you keep 1:1s, make them optional in cadence and report-led in agenda. Ban status updates from them and measure them by problems resolved, not by whether the full time block was used.

      Attribution:
    • wrxd #1
    • Esophagus4 #1
    • garciasn #1 #2
    • Aurornis #1
  2. 02

    Recurring syncs can become communication queues

    Several firsthand accounts described cultures where 1:1s stopped being a management tool and became the official channel for nearly everything. Once managers were booked wall to wall, people were told to save urgent issues for Thursday, then wait for another manager’s Tuesday sync, then another person’s Friday slot. That turns each organizational hop into a delay line, which explains why big companies can feel glacial even when everyone is busy.

    Watch for calendar saturation as an operating risk, not a personal annoyance. If issues wait for standing meetings to move, you need fewer recurring syncs and more ad hoc decision-making paths.

      Attribution:
    • Aurornis #1 #2 #3
    • icedchai #1
  3. 03

    Managers use 1:1s to surface hidden problems

    The strongest defense of 1:1s was practical, not sentimental. People often will not raise blockers, interpersonal friction, burnout, or negative feedback in public channels. Managers argued that regular private conversations are where the actionable facts show up early enough to coach someone, unblock a team, or prevent review-time surprises. Written chat is lower bandwidth and less psychologically safe for many people, especially when the topic is sensitive.

    If you manage engineers, keep a private channel for issues that will not appear in standups or Slack. Use it for feedback close to the event and for removing friction, not for collecting updates you could read elsewhere.

      Attribution:
    • mercutio2 #1
    • DanHulton #1
    • KaiserPro #1
    • dieselgate #1
    • habinero #1
    • lovich #1
  4. 04

    Promotion systems reward visible novelty over durable value

    A recurring explanation for performative work was that reviews often favor promotable narratives, new initiatives, and apparent scope over maintenance or quiet effectiveness. People cited examples from Google and Amazon where novelty, reorgs, and impact theater were easier to convert into advancement than keeping an existing product healthy. Once that is how careers move, engineers and managers rationally optimize for demos, cross-team visibility, and roadmap drama.

    Audit your promotion criteria for maintenance, reliability, and boring execution. If only new surface area earns advancement, you are directly funding performative work.

      Attribution:
    • ActionHank #1
    • dilyevsky #1
    • theodpHN #1
    • cmrdporcupine #1
    • goodmattg #1
    • brailsafe #1
  5. 05

    Bureaucracy grows from real needs, then serves itself

    The comments did not treat overhead as pure delusion. Launch rules, compliance checks, legal review, redundancy, staffing buffers, and administration all start as responses to real failures and scale pressures. The problem is that these layers harden into self-preserving systems. Once an org is safe, rich, or insulated from feedback, the people optimizing for the machinery itself can outcompete the people focused on the original mission.

    When you add process, set an expiration date or success condition for it. Otherwise every control becomes permanent and eventually hires more controls around itself.

      Attribution:
    • cjbgkagh #1 #2
    • saulpw #1
    • zerobees #1
  6. 06

    Engineers often misread invisible work

    A sharp pushback was that developers are bad at judging value outside their own lane. Coordination, stakeholder management, legal and operational prep, and even some maintenance tasks can look like nothing from a distance because they produce fewer obvious artifacts than code. That does not mean all of it is valuable, but assuming everyone not shipping code is dead weight is its own kind of blindness and often leads strong engineers to become bad managers.

    Be careful using your own coding throughput as the baseline for team value. Before calling work performative, ask what risk it removes or what dependency it carries for other teams.

      Attribution:
    • quadrifoliate #1
    • red-iron-pine #1
    • bluGill #1
    • analog31 #1
    • chinabison #1

Against the grain

  1. 01

    Some big tech teams are still impact-driven

    A minority argued that the FAANG picture is too broad. On some teams, reviews still come down to measurable business impact and moved KPIs, not pure posturing. The more useful refinement was that producing value and demonstrating value are only loosely coupled, so the real problem is not every large company but any system where storytelling outruns evidence.

    Do not overgeneralize from one bloated org to all large companies. Ask how impact is actually evaluated on a given team and how tightly that maps to business outcomes.

      Attribution:
    • aloe_falsa #1
    • nicoburns #1
  2. 02

    Obsessing over output can be performative too

    One dissenting view said the cult of visible productivity is itself a trap. Constant rockstar behavior burns people out, creates brittle systems, and mistakes short-term motion for durable value. From that angle, some apparent slack and steadiness are not corruption but the price of preserving stability over time.

    Do not replace bureaucracy theater with heroics theater. Design teams for sustainable delivery, not for a handful of people to look indispensable every week.

      Attribution:
    • sublinear #1
  3. 03

    Rockstar engineering theater is equally fake

    A commenter on a CTO-led innovation team said demo culture can be just as performative as middle-management ritual. Wide but shallow prototypes, AI mockups, and disruption talk create the appearance of progress while the hard part, boring business logic and operations, remains undone. That flips the original complaint on its head by showing that IC-led innovation work can also be kayfabe.

    Be skeptical of prototype-heavy teams that rarely own the last 80 percent of implementation. Reward the people who turn demos into maintained systems, not just the people who present them.

      Attribution:
    • hdndjsbbs #1

In plain english

FAANG ↩
A nickname for major US tech companies, originally Facebook, Amazon, Apple, Netflix, and Google.
IC ↩
Individual contributor, an employee who does not primarily manage other people.
Kayfabe ↩
A wrestling term used here to mean a staged performance that everyone treats as real.
Pareto principle ↩
The 80/20 rule, the idea that roughly 80 percent of effects often come from 20 percent of causes.
Parkinson’s Law ↩
The idea that bureaucratic work and administrative structures tend to expand regardless of the actual amount of useful work to be done.
Pournelle’s Iron Law ↩
A saying that in bureaucracies, people focused on preserving the organization often gain power over people focused on its mission.
Price’s Law ↩
A rule of thumb that a small fraction of participants often produces a disproportionately large share of the output.
Slack ↩
A workplace messaging tool often used for team communication.

Reference links

Management and bureaucracy concepts

1:1 meeting guidance

Books and essays on work culture

Big tech culture and promotion systems

Twitter post-layoff references