Your Best Engineer Is Invisible to You

Your most reliable engineer is going to quit, and the reason is that he was good at his job in a way your company has no way to see.

He runs your infrastructure. For nine months nothing has gone down. No 2 a.m. pages, no status-page incidents, no furious email from your biggest account about an outage during their demo. The integrations hold. The deployments land. When a competitor's site fell over during a traffic spike in March, yours stayed up; three of your customers even mentioned it on calls that week.

He's the reason. You have never once had to think about the thing he thinks about all day, which is the entire point of having him.

Here's the problem sitting underneath that calm. Walk through your last company all-hands in your head. You celebrated the feature that shipped. You celebrated the logo that closed. You celebrated the redesign everyone could see on the screen. Every win you named was a thing somebody could point at. The nine months of nothing-went-wrong got named by no one, because an absence of disasters doesn't demo. Your reward system runs on visible output, and the most load-bearing work in your building leaves no mark on a screen.

That engineer feels it. He shipped a database migration four days early last week, the kind of move that takes down a less careful team for a weekend. He woke up the next morning to a task list flooded with new tickets, all in the clipped tone of someone who's behind, every one of them asking him to add estimates and pick up slack on a feature running late.

Not one line about the migration.

He sat with his coffee and ran the math that every overlooked person eventually runs. The work holding this place together is the work nobody here can see.

“So why am I killing myself to do it well?”

That's the piece this week. The reward system you built can only count what it can see, and the people doing your most load-bearing work are invisible to it.

Click on this ad to make your momma proud.

Many engineers feel stalled because the role itself has not evolved. The work looks the same, but the market has moved.

Senior engineering in 2026 demands ownership, faster judgment, and comfort with ambiguity. If your role is not pushing you there, it may be holding you back.

Last cohort, 15 hiring partners sent 31 representatives to evaluate challengers through 246 live interviews. Gauntlet offers a reset. Apply now.

Cohort 6 starts July 6

_{Must be a US citizen to qualify.}

Stay with the geometry for a second, because it explains more than one engineer.

Every company runs on a scoreboard, formal or not. Yours is the set of things you praise, promote, and bring up in the board deck. At a growth-stage company, that scoreboard formed by accident the same way your culture did, out of whatever was easy to point at when you were 10 people trying to survive. Closed deals. Shipped features. The demo that made an investor lean in. All of it nameable in a sentence, all of it easy to put on a slide.

Now sort your team by how visible their best work is. That tells a different story

The sales rep lives at the top; a closed deal announces itself. The engineer shipping a flashy front-end feature sits up there too. Down at the bottom are the people whose finest day looks like an ordinary one from the outside. The infra engineer whose reward for a perfect quarter is that you never learned his job exists. The support lead who turned three furious churns into renewals over the weekend, which shows up in your numbers as nothing happening. The operations person who renegotiated a vendor contract and took $40,000 off your annual spend you'll never trace back to her.

Their work shares one cruel property. You can see it only when it's gone. You notice infrastructure the day it fails. You notice the support lead the week she's on vacation and two accounts walk out the door. Linda Babcock and her co-authors gave this category a name in their book The No Club: non-promotable tasks, the work that's essential to the organization and invisible unless it goes badly. Their research found these tasks pile onto the people least likely to get credit for them, and that the credit gap runs in a straight line to who burns out and who leaves.

The engineer Tanya Reilly described in her essay "Being Glue" is the same animal. The person who holds the team together, unblocks everyone, catches the thing about to break, then sits in the promotion meeting while a manager explains they haven't done enough visible technical work to move up. Reilly's point has been passed around engineering teams for years because it keeps being true: the glue work counts, and a system that can't see it will grind down the person doing it.

You didn't choose any of this on purpose. Nobody sits down and decides to undervalue the people keeping the lights on. The scoreboard decided it for you, back when you were too small to need one and built it out of whatever was loud.

Here is where the invisible problem sends you a visible bill.

Workhuman and Gallup tracked employees from 2022 to 2024, and the number that should stop you is this: people who don't feel adequately recognized are twice as likely to say they'll quit within the year, and well-recognized employees were 45% less likely to have left after two years. The researchers estimated that getting recognition right could prevent close to half of voluntary turnover. Recognition here means a specific thing: whether a person believes the organization can see what they contribute. The people doing invisible work are, by definition, the hardest for any organization to see, which makes them your highest flight risk and your least obvious one.

Run the cascade for the infra engineer. He leaves in the fall, citing "a new challenge." You're stunned, because his one-on-ones were fine and his comp was at market. You spend four months and a recruiter's fee replacing him. During those four months, the thing he prevented for nine straight months starts happening, because the person who knew which corner of the system was load-bearing is gone and the new hire hasn't found it yet. Your uptime slips. A large customer feels it mid-renewal. The invisible work becomes extremely visible, in the worst possible way, on a status page and in a churn conversation.

That's the trap. The cost of work you can't see stays hidden right up until it converts into a cost you can't miss. You get one bill or the other. The cheap one is recognition. The expensive one is the replacement search plus the outages plus the renewal you lose while the seat sits empty.

And it spreads before he's even gone. The other careful people on your team are watching how the careful engineer gets treated. When the person preventing fires gets less attention than the person who started one and then put it out heroically, everyone learns the lesson fast: visible firefighting beats invisible fireproofing. So your steadiest people stop doing the preventative work that goes unnoticed and start angling for the splashy work that gets a mention. You will have taught your most reliable operators to chase the scoreboard, and your fire count will climb the quarter after.

If your accounting hasn't kept pace with your business, it's quietly costing you. Outdated financials, no clear view of profitability, and hours lost every week — these are growth bottlenecks, not just bookkeeping headaches. BELAY's Financial Experts handle it all.

Download the Free Guide

The fix takes an afternoon and a willingness to look at your own team sideways. Pull up the roster and put two columns next to every name. The first is what this person produces that lands somewhere you already look: a demo, a closed deal, a feature in the changelog, a number that moves on a dashboard. The second is what would break, slip, or start bleeding money if they stopped showing up tomorrow. Most of your people will have something on both sides. The ones you're hunting for have a thin first entry and a heavy second one. They hold the company up in a way your instruments don't register, and they are the names you'd be sickest to lose.

That list is most of the job, because once you can see the contribution, what to do about it stops being a mystery.

The heaviest second column usually belongs to someone a couple of rungs below where you'd point first. The support lead who saved four renewals this year by calling the right customer before they thought to complain. The ops person who caught a billing error before it reached a signed contract. The engineer who owns the gnarliest corner of the codebase and has never made a thing of it. They're easy to miss for the same reason they're load-bearing: they clear problems before the problems reach your chair, so from where you sit the trouble was never there.

Here's the reflex I get from founders the moment I describe this: he's paid to keep the systems up, so why throw him a parade for doing the work?

Wrong take.

You pay that engineer for the judgment that makes the work look easy, and that judgment is the scarcest thing in your building. The person who makes a hard problem look boring is doing the most valuable thing on your team. Boring is the achievement. Honor it as one, or watch it walk to a company that will.

So name it, out loud, with specifics. Not a generic nod to the infra team, but the real article: the migration that landed four days early, the churn somebody talked off the ledge over a weekend, the contract that came down $40,000. Say it in the room, name the person, and spell out what would have happened without them. Vague praise reads as obligation. A named save reads as the first sign that somebody at the top was paying attention.

Then put prevention on the board you already keep. Whatever you review every week, add a line for the disaster that didn't land: uptime held, incidents avoided, accounts pulled back from the edge of churn, sitting right beside the new logos you already cheer. When the only customer number you celebrate is a fresh signup, you've told your whole company that keeping what you have is somebody's unpaid side work.

And go ask. The people carrying invisible work are the last to advertise it, because the temperament that takes on load-bearing work nobody assigned is the same temperament that won't campaign for credit. Sit down with each of them alone, ask what part of their week would surprise you, then stop talking and let the silence get awkward. The first answer is modest. The third answer is the one where you learn that a single person has been standing between you and a problem you didn't know you had.

When the list turns up someone holding the place together, move their pay and title now, while it still reads as recognition. The same raise offered the week after a competing offer lands as a counteroffer, and a counteroffer teaches your best people that the way to get paid here is to threaten to leave. The market rate for the person keeping your product alive is whatever it costs to skip the four-month scramble to replace them.

The engineer with the flooded task list and the cooling coffee is running his math right now, in companies all over your space, this week. The work that holds the place together is the work nobody here can see, so why kill himself doing it well. The first half of that math is true. Whether the second half is true is a column on a list you haven't made yet.

You built the scoreboard when you were 10 people and drowning, and it counted the only things you had hours for. You're past that now, and the instruments that got you here go dark exactly where your most reliable people are standing. You scoped every dashboard you own, which means you're the one who has to scope this one on purpose, because nobody below you can add a gauge for the work they're the ones doing. It costs you an afternoon with a roster and the nerve to ask one uncomfortable question. The thing it prevents costs you a recruiter, a slipped quarter, and the lesson your whole team takes from watching your steadiest person leave unthanked.

Open the roster this afternoon and put the second column next to it. The names that scare you are the ones you've been thanking the least.