What it means to be a Tech Lead and what it doesn’t. Why should someone aspire to become a Tech Lead and why not. What can you do in order to become a Tech Lead.

1. Tech Leads
What is it, do I want it,
and how to get it
Yuval Kesten, Facebook
June 2018

2. WIFM
• Get tools to decide if I want to be a Tech Lead
• (assuming I do) Learn how to get there

3. Tech Lead
Engineering
Manager
Team Lead
Architect
Scrum
Master
Product
Manager

4. Some facts about FB
• Management is not a promotion
• No team leads ("1st tier" managers support 7-12
people)
• No architects
• Outcome and impact driven
• Bottom up roadmapping and goal setting
• We don't do scrum

5. TL - One Liner
• A TL in a project is accountable to the success
and impact of an entire project, including other
people's work.

6. Career Growth
PeopleManager
SeniorEngineer
TechLead

7. TL vs Senior Engineer
• We want all our senior engineers to influence the
team, mentor and support. A TL is accountable
for the actual outcome.
• Accountability => Less solo hands-on time and
more context switching

8. TL vs Manager
• The TL’s top priority is the success of the project
while the EM’s is the success of the team
members.
• The EM will own the “people management” and
org building - Growth plans, soft skills, personal
issues, recruiting etc'
• People Management => Less hands-on time
and more context switching

9. Detailed Expectations
• Goal setting, metrics definition, roadmapping
• Disambiguation of big tasks
• Continuous risks analysis and mitigation
• Continuous priorities inspection
• Realtime feedback to the engineers and their
managers

10. Why do we need TLs
• Horizontal scaling of the team
• Flat organizations
• Impact driven culture => Shared accountability with
product
• People management as a profession
• Architecture quality accountability
• Adds an "engineer" POV to the strategy discussions

11. Why should you?
(become a tech lead)

12. Why not?
(become a tech lead)

13. How to
(become a tech lead)

14. Technical Prerequisites
• Direct hands-on involvement
• Deep understanding of the architecture
• Deep understanding of the interfaces the team
has with customers and other teams
• Very active in planning and goal setting.

15. "Soft" Prerequisites
• Giving feedback about our culture, structure and
how we operate.
• Efficient communication.
• Informal mentor the new people on the team.
• Already established as an informal organic
technical lead in this area or in a related area.

16. Opportunity - New Area
• Exploration and proof of concept
• Define the Go/NoGo criteria
• Curve out more scope for other people

17. Opportunity - Existing Area
• Proven track record in this area
• Map out the things your manager does
• Gradually take responsibilities in the project from
your manager

18. Recap - Ask Yourself
• Do I want to be a Tech Lead?
• Am I demonstrating the required skills?
• What are my opportunities?
• Do I enjoy it?
• Am I perceived as a Tech Lead?