But, the way I see it, the TL is a multifaceted role. They are a bridge between the solution design and the client. They are a caretaker of the development team. And they are the guardian of the codebase itself.
You need to be able to talk to the non technical business type folk about the problem they're facing and how your team can provide a solution to it. Once they've agreed, you need to be able to (single handedly or with an architect)design the solution. Then, break said solution down into byte sized morsels to hand off to your developers... before locking them away never to be bothered by the PM again.
I go into more detail in one of my posts on dev.to
As much as I want to hate
scottshipp
response below, he's not wrong.
But, the way I see it, the TL is a multifaceted role. They are a bridge between the solution design and the client. They are a caretaker of the development team. And they are the guardian of the codebase itself.
You need to be able to talk to the non technical business type folk about the problem they're facing and how your team can provide a solution to it. Once they've agreed, you need to be able to (single handedly or with an architect)design the solution. Then, break said solution down into byte sized morsels to hand off to your developers... before locking them away never to be bothered by the PM again.
I go into more detail in one of my posts on dev.to
Top 5 Responsibilities of a Tech Lead
teachingtechleads ・ Jul 18 ・ 4 min read