Who gets cut first in an engineering team — and how I stopped looking like that person

I used to think the first cut was the weakest coder. Then I watched a careful engineer leave in a round while a louder one stayed, and I watched a quieter one stay while a brilliant contractor-shaped employee did not. The spreadsheet was not a leaderboard. It was a story a director could tell in twenty minutes: what breaks if this name is gone, what still ships, what we already decided to stop. I had been optimizing the wrong column. I was trying to be hard to replace as a puzzle. I needed to be easy to explain as a load-bearing wall.

This is not a guide to surviving by politics. Politics exist. I am talking about the pattern I kept seeing, and the habits that made me look like a line item instead of a surface.

Who gets cut first, in the rooms I have seen

People whose work has no name. If your manager cannot finish the sentence “they own ___” without listing six half-tickets, you are a pool. Pools get skimmed. I was a pool for a year. I was helpful. Helpful is a compliment and a category. Categories get a percentage.

People attached to a bet the company already quietly killed. The platform rewrite that is now “maintenance.” The second app. The research spike that never got a customer. You can be excellent on a dead bet. Excellence does not move the date on the bet. I have seen whole pods vanish because the slide had already changed and nobody told the pod in those words.

People who are expensive and interchangeable on paper. Senior generalists who do not own a scary system can look like a rate. Junior specialists who own the billing edge can look like a risk to remove. The paper is unfair. The paper is what gets used when the room has an hour.

People who are hard to schedule and easy to isolate. Remote in a company that started to value hallway again. A timezone that makes the standup awkward. A personality that made one director’s last meeting sour. Those cuts get called “fit.” Sometimes fit is real harm. Sometimes fit is a cover. I cannot fix a cover from the inside except by not giving them an easy story. Being the person nobody can describe is an easy story.

Last in, when the round is a headcount math problem. That one is not about skill. I say it so we do not pretend every cut is a performance review. Some rounds are a number. If you are new, you can still make the number harder by becoming the name on a surface fast. You cannot always win that race. I will not lie about that.

What I was doing that put me in the pool

I took every ticket that was stuck. I was proud of that. The board looked healthier. My name was on nothing a customer could point at. When the list came, I was “flexible.” Flexible is a pool word.

I kept knowledge in my head. I thought bus factor made me safe. Sometimes it does, for a week, because they are scared. Then they cut you and the team is angry and the wiki is empty and the company still made the number. Hoarding is not a strategy. It is a hostage situation you will lose. I started writing the runbook while I still had the job. That felt like making myself replaceable. It was making myself legible. Legible people get defended with sentences.

I optimized for cleverness in reviews and silence in planning. Directors do not read your review comments. They hear who spoke when the roadmap slipped. I am not saying perform. I am saying the work has to show up in a room that is not git.

How I stopped looking like that person

I picked a surface with a noun. Payments webhooks. The search index. The deploy for the app that makes money. A noun a VP can repeat. I asked to be the name on it. If there was already a name, I asked to be the backup who writes the notes. Backup who writes the notes is still a sentence.

I started sending a short weekly note to my manager: what moved on that surface, what is risky, what I need. Not a brag thread. A status they can paste. I hated it. It took twelve minutes. It is the cheapest insurance I have bought. When they were asked “what does Quinn do,” they had a paragraph. I used to hope they would remember the Friday I stayed late. They remember paragraphs.

I attached myself to uptime or money, not to polish. Polish dies first in a cut. Uptime and money get a defender. If your job is polish, make the polish a named risk: accessibility legal, conversion on the checkout, a regulation. If you cannot name the risk, you are in the nice-to-have column. I have been in that column. I left it on purpose.

I made one junior or one peer able to ship my surface without me. That is the opposite of hoarding. It turns you from a single point of failure into a small bench. Benches look like teams. Teams are harder to delete than heroes. Heroes look expensive. Benches look like a capability.

The week I changed the habit

A reorg rumor week. I looked at my last thirty tickets. Eighteen were “helped X.” Two were “the webhook is mine.” I booked thirty minutes with my manager and said I wanted the webhook to be official, including the page. They said it already was, in their head. I asked them to write it in the team doc. They did. That afternoon felt small. In the next planning meeting someone else tried to put a rewrite on that surface without me. The doc was the sentence. I would not have had the sentence two weeks earlier.

I also stopped volunteering for every stuck ticket in standup. I started saying “I can look after noon if it is still stuck, I am on the webhook today.” That felt selfish. It was a boundary. The board got slightly worse. My name got clearer. I still help. I do not build a career out of being the mop.

What I will not tell you

I will not tell you that this makes you safe. Rounds happen to good people with nouns. Companies lie. Managers lose arguments. A whole product dies. If your surface dies, you can still go. The habits still help the next job: you can point at a thing you owned, a note you wrote, a person you trained.

I will not tell you to become a politician. I will tell you to become explainable. Explainable is a craft. It is tickets with outcomes, docs with owners, a sentence in planning, a number on the board. Coders who only code are easy to love and easy to cut. I was easy to cut. I do not want to be easy to cut. I also do not want to be the person who survives by making others look like the pool. That is a different article and a worse night’s sleep.

If you manage the list

If you are the one who writes the list, the same pattern is a warning. If you can only keep people you can explain, you will systematically fire the quiet owners unless you do the work to learn the nouns. That is on you. I have seen managers discover too late that the person they cut was the only one who understood the night job. Do the paragraph exercise from the other side: every name, one noun, one risk if they leave. If you cannot fill it, you do not know your team yet. Do not pretend the spreadsheet knows.

I stopped looking like the first cut by getting a noun, writing the paragraph, tying the noun to money or uptime, and teaching a backup. I still write code. I just stopped hiding the load-bearing parts in a pile of helpful tickets. Helpful tickets are real work. They are also how you disappear. I do not want to disappear. I want the sentence to be easy when the room is in a hurry. Easy sentences are not vanity. They are how the work stays in the building when the building is scared. If you only take one thing: ask your manager tonight what noun they would use for you. If they hesitate, that hesitation is the whole article. Fix the noun before you fix your editor theme. The theme will not be in the room.