Why I stopped calling myself a developer

For years my title was some flavour of "developer." Backend developer. Full-stack developer. It was accurate and it undersold everything that mattered.

Nobody buys a developer

A restaurant owner does not want a Laravel developer. They want their café to run without three apps and a spreadsheet. A ministry does not want a Next.js expert. They want citizens to stop queuing.

The framework is invisible to the person paying for the outcome. When I led with the tool, I was competing on price with everyone else who listed the same tool. When I led with the outcome, the conversation changed entirely.

Product Engineer is a stance, not a title

Calling myself a product engineer is not vanity. It is a commitment:

• I care what the thing is for, not just whether it compiles.
• I will push back on a feature that adds complexity without adding value.
• I own the outcome from architecture to the moment it is in someone's hands.

That stance makes me a better engineer, not a lesser one. The hardest technical work — the multi-tenant core, the offline-tolerant mobile app, the 2am-safe deployment — only matters because it serves a product someone relies on.

What changed in practice

The work looks similar from the outside and feels different from the inside. I spend more time understanding the business before writing code, and less time gold-plating abstractions nobody asked for. I ship smaller and watch harder.

Code is still my craft. It is just no longer my identity. The product is.