
Daan had been an operations engineer for six years when he noticed something odd about the people who got promoted. They were not always the best at Linux or the fastest at fixing outages. Often they were the ones who could walk into a room full of managers and explain, in plain language, why a system cost what it cost. That discovery changed how he approached his career, and it may change yours. The skill has a name in modern teams: knowing the unit cost.
The moment he realised he was missing something
It happened in a quarterly planning meeting. The head of product asked whether a proposed feature was worth building. A colleague, Marit, said it would add about as much to the cost of serving one customer as the existing search did, and that this seemed acceptable given what customers would pay attention to. Everyone nodded and moved on. Daan had spent a week tuning the database behind that feature and could not have said any of that. He had facts; she had a unit.
He walked back to his desk thinking that technical depth alone had a ceiling. The people in the room did not need more graphs. They needed a sentence they could use to decide. The engineer who could produce that sentence became part of the decision rather than a service the decision depended on.
What “unit cost” means for a working engineer
It sounds like an accounting idea, but it is really about translation. You take a large, abstract number such as the monthly cloud bill and divide it by something people can picture: a customer, a request, a deployment, a lab session. The result is small enough to hold in your head. Once it is there, three useful things become possible.
- You can see which technical choices drive the number, instead of guessing.
- You can compare this month with last month without worrying that growth is distorting the picture.
- You can discuss trade-offs with people who do not read dashboards.
How he built the skill, one small step at a time
Daan did not enrol in anything dramatic at first. He picked one service he owned and began a private notebook. Each month he wrote down the charges tied to it, the number of requests it handled, and what the quotient looked like. He added a line about anything that had changed: a new cache, a bigger instance, a seasonal peak. After three months he could explain the service’s economics in two minutes.
The next step was social. He showed the notebook to a finance colleague, who asked questions he had never considered. Why did the number jump in the week of a marketing campaign? Which part of it would double if traffic doubled? Each question sent him back to the system with sharper eyes, and each answer made him a better engineer, not just a more cost-aware one. If you are plotting your own route upward, the guide to moving from junior to senior DevOps engineer makes the same point from the ladder’s side: scope grows when your explanations grow.
The skills inside the skill
Learning to talk about unit cost quietly develops several abilities that employers prize.
- Systems thinking. You must understand how a request travels through a platform to know what it touches.
- Estimation. You become comfortable with rough numbers and honest about their limits.
- Communication. You learn to choose a unit that fits your audience instead of your own vocabulary.
- Negotiation. You can propose trade-offs without sounding as though you are defending turf.
None of these appears on a typical job advert, and all of them show up in performance reviews.
For people moving across from support and system administration
If you started in support or classic system administration, you may feel the cloud conversation belongs to developers. In truth, you have a head start. You already understand what keeps servers busy and what sits idle, and that intuition is the raw material of unit cost. The article on changing from sysadmin and support work into DevOps describes the wider transition. Add the habit of dividing the bill into units and you can offer something that many pure developers cannot.
A place to learn it with others
Eventually Daan wanted structure, and a community of people with the same questions. He looked at FinOpsSchool, which provides FinOps training and certification, where engineers and finance colleagues learn together how cloud spending can be made visible and shared. He liked that it was built for mixed groups, since his own breakthroughs had come from talking with someone who did not think like him.
What changed for him
A year later, Daan was the person who explained things in planning meetings. He was careful never to use the unit as a weapon. When a product manager proposed an expensive feature, he did not say no. He said what one customer’s share would be and asked whether that fit the plan. Sometimes it did. Sometimes the manager simplified the idea on the spot. In both cases the engineer was in the conversation early, which is where careers grow.
If you want to try the same thing, start with the smallest version. Pick a system you know well, find a month of its charges and a count of what it served, and divide. Write one sentence about what you see. Then say it aloud to someone from outside engineering and watch their face. That moment, when a total becomes something a person can picture, is the beginning of a skill that outlasts any single tool or platform.