Many software engineers pursue tech leadership titles as the ultimate goal of their careers. This happens for various reasons. Some people want the power to define and drive a company’s tech strategy. Others want to focus on more abstract engineering tasks instead of routine coding. Some simply want to create a bigger impact.
However, almost everyone feels stuck when they finally reach a leadership level. They often have no idea what to do or how to do it right. Every week, I receive questions from people I know—and even from random folks—asking what they should do in their projects as tech leaders.
To answer the most common questions, I started writing this book for all tech leaders: CTOs, team leads, tech leads, and engineering managers. Here, I’ve collected some of the good decisions I’ve made in my own tech leadership career. These insights come from my personal experience in the software industry. It’s not the ultimate truth, but it certainly worked for me and others.
Each chapter aims to be both helpful and practical, offering questions for you to reflect on, along with instructions and examples to address specific challenges in your tech leadership journey. Feel free to read it all at once or just the chapter you need when you feel lost.
I’m publishing new chapters every 1–2 weeks, so make sure you subscribe to my LinkedIn to avoid missing any new content.