From Senior Engineer to Tech Lead in 6 Months: What Actually Changed

Six months after joining as a senior engineer, my title changed to tech lead. The title was the smallest part of it. What actually changed was quieter and harder to point at — a shift in where my attention went and how I measured a good day.

From contributor to force multiplier

As a senior engineer, a good day was measured in shipped features. As a lead, my output is no longer my own commits — it's the throughput of the people around me. Unblocking three engineers before lunch is worth more than the feature I didn't get to. That reframing is uncomfortable at first, because the dopamine of personally closing a ticket is real and immediate, while the value of multiplying others is diffuse and delayed.

Thinking in systems, not features

Individual contributors optimize the feature in front of them. Leads have to hold the whole system in their head — how a change ripples through services, what it does to on-call load, whether it's a decision we can reverse cheaply. I started asking "what does this make easy or hard six months from now?" far more than "does this work?"

Communicating in two directions at once

The job is suddenly translation. Downward: turning ambiguous goals into concrete, motivating work. Upward: turning technical reality into something a product or business audience can act on. Doing both at the same time, honestly, without over-promising, is the skill I underestimated the most.

Code review became a leadership act

I used to review code to catch bugs. Now a review is where I teach, set standards, and signal what we value as a team — clarity over cleverness, tests as documentation, small reversible changes. A thoughtful review comment compounds: the engineer writes better code on the next ten PRs without me in the loop.

None of this required a new title. The promotion just made official a shift that had already started: caring less about what I build, and more about what the team can build because I was there.