Engineering Paths Technical Lead Manager
Page-eng-paths
Cancel

Technical Lead Manager (People Manager Path)

Years of xp (guideline)

Sr Software Engineer 1 Technical Lead Manager Engineering Manager

5 to 8

8+

10+

Scope of action

Sr Software Engineer 1 Technical Lead Manager Engineering Manager

1-2 Products / Key components

  • 1 team / 3-4 directs.
  • 1-2 Products / Key components.

2-3 teams / 6-8 directs

Scope of knowledge (Breadth and Depth)

Sr Software Engineer 1
  • Technical expert on 1 product / key component.
  • Learning to solid understanding of 2 other products / key components.
  • Expert in one technology on one part of our stack.
  • Strong proficiency in primary focus area (BE/FE/Data/or DevOps).
  • Proficient with DevOps and Observability stacks.
Technical Lead Manager
  • Foundational IC management.
  • Team synergy leadership.
  • Technical expert on 1 product / key components.
  • Expert in primary focus area (BE/FE/or Data).
  • Strong proficiency in DevOps, PG/CH, Observability, and other platform technologies.
Engineering Manager
  • Advanced IC management.
  • Team synergy leadership.
  • Talent strategy.
  • Compensation strategy.
  • Culture leadership.

Responsibilities

Sr Software Engineer 1
  • Expert understanding of the product and ways that our customers use it.
  • Proactively guides scope at team-level to right-size solutions.
  • Consistently delivers on time and on target, even on large or high-risk tasks.
  • Analyzes and implements technical solutions in an efficient manner. Has a keen eye for reusing code and writing reusable tooling to improve future team efficiency.
  • Can drive team-level planning and communication.
  • Provides accurate effort estimates for large initiatives and clarifies assumptions and risks, even when the scope is still ambiguous.
  • Maintains projects with an understanding of how to make them better over time and understands when the time is right.
  • Thinks about the big picture in the scope of the whole project, sees the impact of the changes they’re making and how they could impact other areas of the system.
  • Can drive improvements in engineering best practices.
  • During critical outages and high-impact issues, help identify solutions and ensure the outcomes are the best for the situation in technical aspects.
Technical Lead Manager
  • Owns consistent team delivery according to quarterly roadmaps. Makes sure to update roadmaps/OKRs to reflect current work and progress.
  • Acts as a top contributor, consistently delivering on time and on target, even on large tasks, and can define scope to meet stakeholder expectations.
  • Drives teammates’ happiness, engagement, and growth.
  • Collaborates with the team’s PM on inter/intra-team communication, planning, and delivery.
  • Drives adoption of engineering best practices at a team level.
  • Acts as the primary driver (together with EM/PM) of the team’s vision document, driving the planning and delivery towards it.
  • Participate in critical outages and high impact issues meetings if in your area of focus. Help come to a solution with the suitable IC or the technical approach when it is in your area of expertise.
  • Able to create, drive, and communicate big systems architecture decisions and initiatives within the team.
  • Takes ownership of the team’s technical scope of responsibility by nurturing scalability, reliability, and efficiency.
  • Fosters cost-awareness by advocating for initiatives that lead to savings, and diligently monitoring spending across the team scope.
Engineering Manager
  • Drives Engineers’ happiness, engagement, and growth.
  • Operates talent strategy (IDPs, retention, acquisition).
  • Collaborates with TL and facilitates consistent team delivery according to quarterly roadmaps.
  • Collaborates with the team’s PM on inter/intra-team communication, planning, and delivery.
  • Leads team organization and controls processes.
  • Collaborates on planning and contributes to Engineering Operations.
  • Proactively works together with PM and TL to unblock the team.
  • Advocates on behalf of team members.

Communication and leadership

Sr Software Engineer 1
  • Communicates effectively across functions; can work well with Product, Design, Ops, Finance, Sales, and any other internal stakeholders, as necessary.
  • Mentors junior engineers via pairing, design review, and code review.
  • Proactively identifies problems with requirements (lack of clarity, inconsistencies, technical limitations) for their own work and adjacent work and communicates these issues early to help course-correct.
  • Communicates technical decisions through design docs, PED talks, and Tettra articles.
  • Communicates well both in writing and verbally with teammates, peers, and stakeholders.
  • Positively influences team culture.
  • During critical outages and high-impact issue investigations, make thoughtful and clear communication regarding how to achieve the proper outcomes.
  • Able to discover, analyze, understand, and communicate trade-offs with PM and EM, and drive Engineering improvements within the team scope.
Technical Lead Manager
  • Makes independent decisions for the team; is actively learning how to handle complex management situations.
  • Contributes to the career development of others.
  • Expected to meet regularly with their direct reports, create openness to feedback by asking for it, use that openness to provide frequent feedback on their work, help the individuals set goals, and work with the HR partner and director or VP to ensure employee growth and retention goals.
  • Communicates team’s vision and mission to Engineering. Proactively clarifies the “why’s” of changes and decisions taken to the team and all stakeholders, creating buy-in on those.
  • Leads and embodies team culture.
  • Use communication to bring the right ICs to the critical outages and high-impact issues meetings and help/facilitate decisions, ensure communication is clear and visible in the appropriate channels and help debrief the outcomes through messages on the proper channels and/or post-mortem documents.
Engineering Manager
  • Manages independently; communicates context to the team and surfaces concise people and technical information to upper management.
  • Able to communicate technical concepts to business stakeholders and business objectives to the technical team. .
  • Sets clear expectations for team members; solicits, synthesizes, and delivers feedback.
  • Communicates timeline, scope, and technical concerns inside and outside OBTs to all relevant stakeholders.
  • Leads delivery of major initiatives on clear timelines.
  • Owns the quarterly Roadmaps/OKR setting and review process for teams under their oversight.
  • Able to identify areas of strategic technical debt and provide cost/benefit analysis for eliminating this debt and suggested timelines for how to prioritize it.
  • Comfortable managing team members with different skill sets and technical areas of focus.
  • Sells Beyond as a company and their organization as a team to potential candidates. Inspires potential recruits to join the company.
  • Leads and embodies team culture.
  • During critical outages and high-impact issue investigations, identify and bring the right people to the group call. Ensure communication is clear and visible in the appropriate channels.

Competencies focus

Sr Software Engineer 1 Technical Lead Manager Engineering Manager
  • Deliver Results.
  • Service Oriented.
  • Deliver Results.
  • Service oriented.
  • Service oriented.
  • Deliver results.

reference: People manager competencies (internal link)

Checkpoints for reaching this level

Sr Software Engineer 1
  • Has lead code reviews for the team for 12+ months.
  • Has participated in 2+ technical planning or designs of large Epics or engineering initiatives.
  • Has presented 1+ times on a technical topic for a PED talk, ideally based on Friday afternoon L+D initiatives.
  • Has documented 1 technical aspect of systems implementation and/or post-mortems.
Technical Lead Manager
  • Has been a tech lead for 1+ year.
  • Has proposed and participated in 3+ technical planning or designs of large Epics or engineering initiatives.
  • Has presented 1+ times on a technical topic for a PED talk, ideally based on Friday PMs L+D initiatives.
  • Has documented 3+ technical aspects of systems implementation and/or post-mortems.
  • Has stepped through explorative material and checked in with their manager as they consumed said material. For example, recommendations include “Radical Candor” and “Crucial Conversations.”.
Engineering Manager
  • Has participated in mentoring, advocating, and executing 2+ IC promotions.
  • Has stepped through explorative material and checked in with their manager as they consumed said material. For example, recommendations include “An Elegant Puzzle”, “Staff Engineer”, and “The Manager’s Path”, as well as broader choices on business, personal growth, and communication such as 7 habits, 5 dysfunctions, How to decide, Leadership is language, Turn the ship around, Measure what matters, Coaching habit, EI 2.0, Nonviolent communication, Dare to lead, …

Trending Tags