5 Aspects to Shape a Tech Lead
Recap on what to focus for promoting to Tech Lead
There are many new people in the newsletter since I started to write about real-life lessons for thriving in Software Engineering, Technical Leadership, and Technical Growth.
Also, many people provide feedback about their interest in growing in the technical ladder to Tech Lead.
Because of that, today I’ve decided to recap and compile the different emails I’ve sent in the past to define 5 aspects that a Tech Lead must work on for this role.
Let’s start from the beginning.
☝🏼 I think knowing in advance what a role is about is a good practice. You can think that you want to reach a role, but without knowing it, you can face a difficult situation. When I say knowing the role, I mean in deep.
👉🏼 What are the responsibilities of a Tech Lead?
In the email below, I tried to summarize the main responsibilities that a Tech Lead has to own to succeed 👇🏻
There, you will find 7 responsibilities for the Tech Lead role organized by area of influence:
Within the team.
Outside of the team.
Crosswise.
☝🏼 When we work as less experienced Software Engineers, we trust in upper management to decide what is a priority and what makes sense to be done. When you grow in the technical ladder, though, what is expected from you is that you question the status quo to ensure your team or organization delivers the right value.
👉🏼 How to ensure you deliver the right value?
In the email below, I tell you a real case by which you will learn how to ensure that you focus on the right thing to do. 👇🏻
Do not be afraid to question your manager; it’s expected of you!
☝🏼 As a future Tech Lead, you have to find how to solve problems that impact beyond your team. You have to demonstrate that you are accountable and reliable. Also, you have to demonstrate that the company's goals are your goals too.
👉🏼 Seek opportunities, all the time.
In this email below, I transmit how to make an opportunity from a company’s problem. 👇🏻
Pay attention, opportunities are everywhere.
☝🏼 The role Tech Lead is composed of the 2 words “Tech” and “Lead”. Even though human skills are key to growing and success in this role, do not forget about the tech part. For that, the Tech Lead must own the technical backlog, and one of the most important parts of it is the technical debt.
👉🏼 How do you deal with and reduce the technical debt?
In the email below, I explain the technique that helped me keep the technical debt under control without impacting the delivery of new features. 👇🏻
There, you will find that applying the “Girl Scout Rule“ is the key.
But that’s not all. Dealing with tech debt is not enough… is it?
☝🏼 You are acting as Tech Lead, or you have reached the role for real. Now, what? Is it all working fine, the sky is blue, and the stars are shining?
👉🏼 How do you know you are performing well as Tech Lead?
In the email below, I explain the 4 metrics every Tech Lead must track. 👇🏻
You will see:
Ensure quality code.
Optimize Software Delivery.
Manage Technical Initiatives.
Mentoring Teammates.
This is it for today’s email. Hope you enjoyed this guidance for reaching the Tech Lead role.
Are you interested in other roles? Is there something concrete you would like to know more? Drop me an email and tell me more, I answer all emails!
We are ✨1139 Optimist Engineers✨!! 🚀
Thanks for your support of my work here, really appreciate it!
If you enjoyed this article, then click the 💜. It helps!
If you know someone else will benefit from this, ♻️ share this post.
Great post, Marcos!
A great Tech Lead seeks opportunities to deliver value, within the team and outside (cross-teams) as well.
Thank you Marcos, really insightful.
I would add one aspect I've been studying and practicing more intentionally lately: developing an executive presence.