Leveling Up as a Tech Lead

Chapter 4. Running One-on-Ones with Your Team

One of the very first things I do when stepping into a tech lead role with a new team is set up recurring one-on-ones with each team member. While the collaborative dynamic of the team as a whole is essential, these individual one-on-ones are where you can build personal connections, understand unique perspectives, and address concerns that might not surface in group settings. Before diving into the tech stack, analyzing the codebase, or meeting stakeholders, I prioritize these meetings, because the team’s collective success starts with understanding and supporting each individual.

That said, there’s an important distinction worth calling out early. In some companies, one-on-ones are formally owned by engineering managers, and that can lead to some confusion about whether tech leads should still run their own. My view is simple: yes, you absolutely should. Even if there’s some overlap in topics, that doesn’t mean the conversations are redundant. It just means you’ll need strong alignment with your EM and clarity with your team about your role in supporting them.

Take growth, for example. An EM might manage the formal side, including things like promotions, compensation processes, and official career frameworks, but that doesn’t mean people’s growth isn’t also your responsibility. Quite the opposite. Their development impacts the team’s outcomes, and by extension, your success as a lead. As someone who works closely with them day to ...