Responsibilities

• All of the responsibilities of an

Plus

• Managing engineer(s) on the team with the goal of
  • Helping those engineers grow and succeed
  • Giving them regular feedback via weekly or biweekly 1-1s
  • Coaching them on
    • how to become better coders
    • on communication
    • on prioritization
    • on product-orientation
    • on taking on larger and harder projects
• Helping hire new engineers onto the team
  • Holding initial calls about Warp
  • Devising strategies to attract new engineers
• Helping onboard engineers
• Surfacing issues and suggesting improvements on culture & process
  • Raising issues to Zach
  • Raising them to the team at large
  • Trying to figure out how the team as a whole can operate better
• Helping establish a more formal review and promotion process
  • When the process is in place, helping their reports through it

Not responsible for

• Engineering compensation and promotion decisions
• Assignment of projects to engineers, although they can definitely help engineers figure out what they want to work on
• Technical leadership or ownership of any particular part of the codebase
  • Engineers they manage will be working across the team
  • Technical leadership will continue to be on a project by project basis

Success criteria

• The same as for an Engineer plus
• Success and growth for their reports according to the Engineer responsibilities

Note on leveling

• Leveling is separate from whether one has reports or not (e.g. having reports does not de facto make you higher on the ladder)
• Leveling in general still needs to be defined