Becoming a tech lead is the most common growth path for software engineers as they grow to senior and staff levels.
My manager suggested that I work on the skills below to advance my career. Do you have any masterclasses or other resources to develop these skills? I added links to the resources that I know about.
* Stakeholder management
* Project management
* Design & architecture -
* Communication -
* Leadership -
Hey folks,
I don't know how to contribute to our team's monthly planning. How should I come up with ideas for things that the team should work on and contribute to our team's road-mapping meaningfully?
I watched the video I am particularly interested in the point: "Great TLs sequence their project in such a way that all the highest risk things get knocked out first". Can you please give examples of doing that in a real life? What are some examples of activities that you found higher risk than others and therefore you decided to do them first to minimize the risk?
My goal is to get to this level someday, so I would love to understand more. In particular, how does this dynamic play out at Big Tech/larger tech companies?
At Microsoft, basic criteria for promotion is to deliver at next level consistently. Example: At L62, i need to work and deliver at L63s work level standards.
Crux is when you’re learning and digging deeper technically. How do you approach taking ownership and growing your impact on not just the project but across the team and larger axis?
A tech lead is responsible for guiding multiple software engineers throughout the execution of a project. They usually have many years of software engineer experience and system design knowledge to help them navigate through complex software engineering situations. They work with multiple stakeholders to ensure that a project is delivered on time. They also set expectations for deliverables and quality of the project.