Here’s a short list of some of the aspects that I feel make
for a quality Tech Lead. It’s certainly not an all-inclusive list and I’m sure
there is a large collection of TL’s out there that do just fine at it without
having some of these. In somewhat of a priority order…
- Caring (for both the team and the code)
- Compassionate
- Understanding
- Open to confrontation
- Willing to mentor
- Stepping in to take the bullet
- Fighting for what’s right (both in the team and in the code)
- Not afraid to fail
- Ability to be a hard-ass when needed
- Technical in the actual stack of that which they are leading
Some of you may be questioning why I ranked actually being
technical last, and it’s really an easy answer. Being a Tech Lead has way less
to do with the knowledge and a lot more to do with the actual leading. Get it? That’s why we call them a “Tech Lead”,
not “Tech Know It All”. You could be the most knowledgeable expert
in the tech and still suck at leading. A quality Tech Lead supports the people
over supporting the tech. They motivate more than coordinate. They inspire
rather than conspire. They trust over relying on control. They do the right
thing more so than doing things right. In short, they care.
Oh, and there is one other critical point to being a quality
Tech Lead. Actually wanting to do it.
The passion for it has to be there, or else it’s a waste. All too often, seniors
take the step to TL, only because it’s the perceived next rung on the ladder of
their career, only to find out they don’t like the view once there and
therefore don’t want to do it. I was lucky enough to realize before my jump to
leadership that I enjoyed helping a team realize their goal more so than myself
taking the glory.
I’ll close with a little advice for anyone who already has,
may be looking to, or someday in the future might take the step to a Tech Lead.
Be honest with yourself on if you’re ready, willing and able to truly LEAD.
d2.
