The Hardest Transition in Tech
After two decades of writing code, debugging production issues at 2 AM, and
architecting systems from scratch, I made the deliberate choice to step into
leadership. Not because I stopped loving the craft — but because I realized I
could multiply my impact by helping others do their best work.
The shift wasn't easy. Early on, I had to resist the urge to jump in and
solve every technical problem myself. I learned that great engineering leadership
means asking better questions, not giving all the answers. It means creating
clarity from ambiguity, and protecting your team's ability to move fast.
Leading a large-scale system transformation at Citibank has been the ultimate
test — navigating competing priorities, legacy constraints, organizational
complexity, and high-stakes delivery, all while keeping a team of talented
engineers energized, aligned, and growing.
I document what I've learned here — the frameworks, the hard lessons,
and the principles that have made me a better leader.
