Which type of Engineer do you want to be this year?


Hello Reader,

Understanding this distinction would have saved me years of frustration in my engineering career.

Every organization has two kinds of engineers. There are functional engineers and there are vital engineers. Most people never realize this, and it keeps them stuck far longer than necessary. I learned this the hard way, after confusing output with outcome for a long time.

At first glance, functional engineers look impressive. They deliver tickets, close incidents, follow processes and meet requirements. They do exactly what is asked of them. They are reliable, competent and skilled but they are replaceable.

If the company finds a cheaper option, they take it. If priorities shift, they get moved aside. If budgets are tight, they are at risk.

Functional engineers see themselves as executors of processes. They focus on doing tasks better. They only optimize to make things faster, cleaner and more efficient. They measure success by output but the problem is that outputs are facts but outcomes are meaning. Most organizations reward outcomes because outputs tell you what happened but outcomes explain why it mattered.

Functional engineers often feel anxious. They worry about layoffs, automation, AI, someone younger, faster or cheaper showing up. They feel the pressure to stay relevant by learning one more tool, one more framework or one more system.

Vital engineers are aligned to results, not tasks. They care less about how something is done and more about what changes because it was done.

They ask different questions: why does this matter, who does this decision affect, what happens if we do nothing, what tradeoff are we making here? Vital engineers think in outcomes like reduced downtime, faster delivery, lower risk or higher revenue. They translate technical work into business impact. That is what makes them valuable and value is what makes someone hard to replace.

Vital engineers are seen as the life-force of a system, team or decision. They own a problem space. They develop a point of view. They have opinions that shape direction. They are not threatened by new tools or new people because they are quick to adapt, integrate and evolve. Their value is not tied to a single skill, It is tied to judgment.

Functional engineers fear time away. They worry about what happens if they step back. Will someone else take over or their contribution be forgotten?

Vital engineers welcome distance because space sharpens their thinking and perspective fuels their insight. People notice their absence, not just their presence.

Functional engineers bond over how hard things are, how broken the system is and how unfair leadership can be.

Vital engineers seek challenge, debate, friction and rooms where their thinking is stretched. They leave environments that numb them and move toward ones that sharpen them.

This is the real choice for you this year Reader.

You can either choose process or results, output or outcome, execution or impact, competence or credibility.

You can choose to do more or seek to change more.

You can seek clearer decisions instead of clearer instructions.

You can choose exhaustion by endless execution or be energized by meaningful progress.

From this point forward, you get to choose how you show up. I urge you to optimize for vitality and not functionality.

The Modern Engineer

Join 1k+ other forward-thinking professionals who receive the weekly newsletter, where I provide actionable strategies, insights and tools to escape the grind and build influential, future-proof careers. Sign up and I will send yoy a FREE copy of my 5-Stage playbook to multiply your impact and build a career that AI can't replace.

Read more from The Modern Engineer

Hello Reader, A few years ago, I proposed adding automated rollback capabilities to our deployment pipeline. The system was fragile—on-call rotations were painful, incidents were frequent, and small changes could break the entire workflow. The refactor wouldn't ship new features, but it would make everything more reliable six months from now. The response was polite: "Sounds sensible. Not right now. Let's revisit next quarter." Next quarter came with new deadlines, new priorities and other...

Hello Reader, A few months ago, I spoke with an engineer who described a design review he could not stop thinking about. It was a standard meeting. A dozen people on the call, a couple of senior voices leading the conversation and a solution that already felt decided before anyone joined. Halfway through, he noticed a scaling issue that would only show up during edge cases. He thought about bringing it up then he looked at the room. A senior engineer had already said it looked good. The...

Hello Reader, I spoke with an old friend last week. He told me he spent 4 years as a senior engineer watching less experienced engineers get to the next level ahead of him. His designs were cleaner. His solutions were faster. His technical reviews were thorough. But he kept getting the same feedback: "You need to be more visible and strategic" He thought that meant talking more in meetings. He was wrong. What he lacked was influence at work The Real Problem Here’s what actually happens when...