Transitioning From Engineer to Technical Leader

​This weekend we are having a conversation with Paul Chesa, a seasoned full-stack engineer.

Many technical leaders begin as strong individual contributors.

​They are good at:

• ​Writing code

• ​Solving technical problems

• ​Debugging systems

• ​Shipping features and

• ​Making things work

​But technical leadership requires a different kind of contribution. A technical leader must learn how to:

• ​Guide people

• ​Make trade-offs

• ​Communicate direction

• ​Mentor others

• ​Influence decisions

• ​Protect engineering quality and

• ​Connect technical work to business outcomes

​This session explores what changes when an engineer moves from being responsible for their own output to being responsible for the direction, quality, and growth of a technical team.

FOCUS AREAS

​From Individual Output to Team Impact

​Communication & Influence

​Mentorship & Team Growth

​Balancing Code, People & Direction