When a team cannot hire a senior engineer, they extract senior-level work from junior engineers. The juniors produce systems held together by rubber bands and chewing gum — tightly coupled, unmaintainable, and understood only by their creators. This locks each junior to the systems they built, stacking permanent responsibilities onto people who cannot handle more, preventing them from growing into the senior engineers the team actually needs. The organization destroys its own capacity to produce the thing it most desperately lacks.
Simple Picture
ELI5: you need a bridge and can only afford a student architect. The student builds something that works but is so idiosyncratic that only they understand it. Now you cannot fire them, cannot reassign them, and cannot hire anyone new to maintain it. The student is trapped maintaining their own bad bridge forever, never learning to build a good one. Meanwhile, you build more bad bridges with more students. Eventually one collapses and you call an expensive consultant to save the project — then repeat the entire cycle.
The Overtaxing Loop
The feedback loop has four stages:
-
Extraction — Junior engineers are given work above their skill level because no senior is available. The systems they produce are tightly coupled and opaque.
-
Lock-in — The creator becomes the only person qualified to maintain or change their system. This stacks a permanent responsibility that prevents them from being freed for other work.
-
Fragility — With 10-20 systems built this way, interconnected by people who each understand only their own piece, the entire project becomes a single point of failure for every engineer. If any one of them leaves, their systems become unmaintainable.
-
Collapse — A critical issue surfaces too late for internal resolution. An emergency consultant (the firefighter) is called at enormous cost. After the fire, the team hires new junior engineers and the cycle restarts.
This is the dead-sea-effect in manufacturing mode: the Dead Sea Effect describes how good people evaporate from a dysfunctional organization. The firefighter trap describes how the organization prevents good people from being produced in the first place — the juniors who could grow into seniors are instead locked into maintenance roles on bad systems, and when they burn out and leave, they take all institutional knowledge with them.
The expert-beginner enters at stage 2: a junior locked to their own systems has no exposure to better approaches. Their plateau becomes the standard, and anyone suggesting a different architecture is threatening the fragile equilibrium that keeps the project alive.
The Missing Senior
A single senior engineer prevents cascading failures that cost orders of magnitude more than their salary. One consulting client had a source control misconfiguration — temporary cache files tracked and distributed to the team. Any senior engineer would have fixed this on sight. Without one, the cache files caused the game engine to skip audio generation, breaking all audio. The audio subcontractor reported everything working. Months of finger-pointing, potential lawsuits, and hostile work culture followed — all from a trivial configuration error.
The cost of not having the role always exceeds the cost of paying for it. The organization that says “we can’t find a senior, our team can handle it” is betting the entire project on the assumption that no trivial issue will cascade — a bet that fails almost every time.
All Your Subordinates Are Lying to You
The firefighter’s first discovery on any engagement: within nanoseconds of arrival, every engineer is telling them everything that is wrong — with management, the company, and the development process. Not because the firefighter has a trustworthy face, but because the engineers have been trying to communicate these problems for months and management has either ignored, deprioritized, or actively punished the feedback.
This is voice atrophy made concrete. The engineers use voice. Management converts their reports into zero action. The engineers learn that voice is futile and switch to “clock in, clock out, it’s not my problem.” Buckingham’s insight applies: you can tell if an engineer is healthy by whether they are comfortable giving constructive feedback. When feedback produces zero action, the enthusiastic company-first worker converts into the disengaged clock-puncher — not from laziness but from rational despair.
One client’s producer had no engineering knowledge and kept assigning tickets to the wrong specialists — network engineers getting gameplay fixes, gameplay engineers getting rendering tasks. Every engineer had raised this. Every report was ignored. One network engineer spent three months learning animation graphs because that was what their ticket said. The engineers found a way to improve themselves without improving the company — the most rational response to voice that goes unheard.
When the firefighter laid this out to upper management, their first question was: “Who is giving up this information?” They wanted to punish the feedback rather than fix the problem. The firefighter was dismissed. A month later, the engineering team went from seven to two. A month after that, zero. The company hired all new juniors and the cycle began again.
The pattern scales beyond engineering. When mediocre leaders gain power without vision, charisma, or technical skill, they play it safe and play politics — and since they know they are inadequate, they claim credit and avoid blame. The result: an explosion of bureaucracy (career frameworks with 18 levels, quarterly assessments, OKRs, KPIs, DORA, SAFe) and meetings that fill every calendar. Hiring degrades further — people are hired based on whether they represent no threat, so any trace of greatness guarantees rejection. The ideal hire becomes a mindless all-rounder who semi-competently does whatever they are told. Talent evaporates, the fealty system solidifies, CYA culture becomes the only visible form of productivity, and the company drifts into irrelevance.
Common Misread
The dimwit take is “just hire better engineers — the problem is talent.”
The midwit take is “this is about technical debt — just refactor more.”
The better take is that the firefighter trap is an organizational feedback failure, not a technical one. The systems are bad because the people who built them were set up to fail. The people failed because no one senior enough to prevent it was present. And the senior wasn’t present because management settled for less or ignored the need entirely — then fired the juniors for not being senior. The bottleneck is not engineering skill. It is the organizational capacity to hear and act on feedback from the people closest to the work.
Main Payoff
Bad leaders reward arsonists for putting out the fires they started. Meetings are bugs — not features — masking trust issues, unclear goals, and missing communication channels. A leader must be technical enough to appreciate the problems that didn’t happen, but the system rewards visible rescue over invisible prevention.
The firefighter trap explains why the same companies call the same consultants for the same emergencies year after year. The emergency is never the problem. The emergency is a symptom of a feedback loop that destroys the conditions under which the problem could be prevented. Breaking the loop requires two things the organization is structurally resistant to: listening to juniors and investing in growth before the fire starts. Weaponized code review compounds the problem: even when juniors do produce work, the approval gate can destroy their velocity and morale through patterns that look like quality control. The paradox is that the companies most in need of this investment are the ones least able to make it — because all their budget is going to firefighters.
References:
- Michael Allar, Confessions of an Unreal Engine 4 Engineering Firefighter