The defining career move for any engineer is the transition from effort-based value to expertise-based value. Everything else — negotiation, branding, networking, job satisfaction — is downstream of making this transition.
Early in my career, I noticed there are fundamentally two kinds of work:
Mode 1: High effort, low ownership, low creativity. You’re paid for hours and output. Your value is your availability and willingness to grind. You’re fungible — any competent engineer could replace you.
Mode 2: Expertise-driven, high responsibility, high credit. You’re paid for judgment and decisions. Your value is knowing which problems matter and how to solve them. You’re hard to replace — not because you hoard knowledge, but because your pattern recognition took years to build.
Understanding Mode 2 doesn’t come naturally. Nobody tells you this transition exists, let alone how to navigate it. You figure it out by watching the people around you who seem to have outsized impact with what looks like less effort, and realizing they’re playing a different game.
After seven years of building — from data science intern to engineering manager — I’ve come to see this transition as a five-stage sequence. Each stage builds on the last. Skipping stages doesn’t work.
Cal Newport nails this: career passions are rare and take time to develop. The craftsman mindset — focusing obsessively on what value you produce rather than what the job gives you — is the foundation.
Early in my career at Datasutram, I wasn’t thinking about personal brand or career strategy. I was building satellite image classification models and NLP systems because I was Employee #1 and everything needed to get done. That urgency to learn by doing, not by planning, is the craftsman mindset.
The key insight: high-leverage activities produce disproportionate value. Not all skills are equally valuable. The ability to build a real-time distributed system is more leveraged than the ability to write clean Python. Both matter, but one opens more doors.
This is the move from “I write code” to “I design systems and make decisions.”
At Epic One, I started as the sole engineer and grew the team to 12. Somewhere in that process, I stopped being the person who writes the most code and started being the person who decides what gets built, how it’s architected, and in what order. Senior engineers focus on requirements definition, non-functional requirements, dependency mapping, testing strategies, deployment, observability, and measuring success.
The shift is uncomfortable. You feel like you’re producing less because you’re writing less code. But the leverage is enormous — one good architectural decision saves the team months of rework.
The traits that define great work — creativity, impact, autonomy — are rare and valuable. You can’t demand them. You earn them.
Control over your work is the dream-job elixir. But there are two traps:
Trap 1: Seeking control without expertise. You ask for autonomy before you’ve proven you can handle it. This gets you fired or sidelined.
Trap 2: Having expertise but not exercising leverage. Your employer benefits from your skills but has no incentive to give you more control. You have to push for it, knowing you have the capital to back it up.
At Clootrack, I had enough expertise to take real ownership — leading the transition from manual reports to automated templates, designing the multi-tenant architecture for 2.0. Each of these created more leverage, which created more control.
This is the part most engineers resist. Branding feels like vanity. It’s not — it’s the signaling layer that converts invisible expertise into visible leverage.
Your manager should be able to recite your big wins. If they can’t, you have a positioning problem, not a performance problem.
The formula is simple: Identity + Opinions = Brand.
Write about what you’ve built. Talk about what you’ve learned. Have a point of view on how things should be done. Not in a self-promotional way — in a “here’s what I think and here’s the evidence” way.
This is partly why this website exists.
Every negotiation tactic works better when you’re in Stage 4. Negotiation power comes from being the person they can’t easily replace, not from scripts or tactics.
When I joined DriveX as a Tech Lead and negotiated a path to EM and then Architect, it wasn’t because I had better negotiation skills. It was because I had a track record of building from zero and scaling — Epic One, Reward360, Clootrack — and that track record was visible.
Most career advice treats these stages as independent: “learn to negotiate,” “build your brand,” “develop deep expertise.” But they’re not independent. They’re sequential. Brand without expertise is empty. Negotiation without leverage is weak. Control without skill is dangerous.
The assembled sequence turns a vague sense of career dissatisfaction into a traversable path. You’re not stuck in Mode 1 because you lack talent. You’re stuck because you haven’t completed a stage you need before the next one unlocks.
Everything I build on the side — IdeaMaze, the WhatsApp auction platform, the dozen other projects — is Stage 1 and Stage 4 happening simultaneously. Each project develops rare skills (Stage 1) and makes those skills visible (Stage 4).
Building is the fastest path through the leverage transition. You can’t fake a shipped product.
This framework draws on ideas from Cal Newport’s “So Good They Can’t Ignore You,” Edmond Lau’s “The Effective Engineer,” and Shawn Wang’s “The Coding Career Handbook” — filtered through seven years of building from zero.