Focused on creating wonderful user experiences by attending to folks needs with empathy and creating spaces of safety. Senior Frontend Developer/Tech Lead at Dolittle.
I don't think any two tech lead roles are the same, as context is so, so important. What I can do is share my own experiences from being a tech lead myself, and serving with other great tech leads.
Being a tech lead to me is less about the tech, and more about being a lead. It's as much about having a relationship towards the more business aspects of the company and the dev-team as it does the technology itself. From a technology perspective, a tech lead should provide guidance by showing a clear direction about where your specific tech choices are headed and tie those choices back to business outcomes.
Guidance is an important word here, since it doesn't mean being prescriptive, but rather giving boundaries of what is expected, and allowing other team members to experiment within those boundaries. It's also about listening and mentorship. Your role as a lead is to communicate your vision to other team members and gather individual feedback that help the whole when it makes sense.
It means being hands-on the tech as much as possible, but perhaps focusing more on integration and communication between people, teams / services instead of the nitty gritty implementation details. It also means experimenting on technology (with other team members where it makes sense), and having an idea of where the technology needs to be in x number of years to continue to support the business aka "The Vision".
One of the most important aspects, though, is that you don't need to have all the answers. Instead, seek out opinions and views of others on the team, and amplify their voices. You may have the veto-call, but the less the use it, the more influence you will have on the team's direction and support.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't think any two tech lead roles are the same, as context is so, so important. What I can do is share my own experiences from being a tech lead myself, and serving with other great tech leads.
Being a tech lead to me is less about the tech, and more about being a lead. It's as much about having a relationship towards the more business aspects of the company and the dev-team as it does the technology itself. From a technology perspective, a tech lead should provide guidance by showing a clear direction about where your specific tech choices are headed and tie those choices back to business outcomes.
Guidance is an important word here, since it doesn't mean being prescriptive, but rather giving boundaries of what is expected, and allowing other team members to experiment within those boundaries. It's also about listening and mentorship. Your role as a lead is to communicate your vision to other team members and gather individual feedback that help the whole when it makes sense.
It means being hands-on the tech as much as possible, but perhaps focusing more on integration and communication between people, teams / services instead of the nitty gritty implementation details. It also means experimenting on technology (with other team members where it makes sense), and having an idea of where the technology needs to be in x number of years to continue to support the business aka "The Vision".
One of the most important aspects, though, is that you don't need to have all the answers. Instead, seek out opinions and views of others on the team, and amplify their voices. You may have the veto-call, but the less the use it, the more influence you will have on the team's direction and support.