Engineering Paths Sr Software Engineer 2
Page-eng-paths
Cancel

Sr Software Engineer 2 (Sr Individual Contributor Path)

Years of experience (guideline)

Sr Software Engineer 1 Sr Software Engineer 2 Sr Software Engineer 3

5 to 8

7+

9+

Scope of action

Sr Software Engineer 1 Sr Software Engineer 2 Sr Software Engineer 3

1-2 Products / Key components

2-3 Products / Key components

  • Multiple Products/Key Components.
  • All domains of core team and cross-teams tasks.

Role Description

Sr Software Engineer 1

A senior engineer and technical expert on one product with growing knowledge across others who leads team-level planning and drives architecture decisions within the team. They proactively guide scope, provide accurate estimates even with ambiguous requirements, and mentor junior engineers. They communicate effectively across functions and drive improvements in engineering best practices.

Sr Software Engineer 2

A senior engineer and technical expert across multiple products who leads team and inter-team communication while defining scope to meet stakeholder expectations. They make others better through code reviews, documentation, and technical guidance. They create buy-in on decisions, coach team members on breaking down work, and take ownership of the team’s technical scope including scalability, reliability, and efficiency.

Sr Software Engineer 3

A senior engineer who owns the team’s technical vision, bridging technical execution and business strategy while making critical decisions in high-pressure situations. They take proactive ownership of the team’s technical direction, anticipate future needs, and secure stakeholder buy-in. They develop risk mitigation strategies and hold the team accountable to high technical standards while inspiring innovation and excellence.

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.
Sr Software Engineer 2
  • Technical expert on 2 products / key components, solid on the rest of the platform.
  • Expert in primary focus area (BE/FE/Data/or DevOps).
  • Proficiency in DevOps, PG/CH, Observability, and other platform technologies.
Sr Software Engineer 3
  • Technical expert on multiple products / key components, knowing all the extent of their core team’s domain.
  • Expert in primary focus area (BE/FE/Data/or DevOps).
  • Strong proficiency in DevOps, PG/CH, Observability, and other platform technologies.
  • Thrives in an environment with ambiguous scope, clarifying uncertainties and defining clear paths forward with the best outcomes given the goals.
  • Provides guidance and direction to their team rather than waiting for instructions, finding opportunities and ensuring proactive and innovative problem-solving.

reference: Products and key components (internal link)

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.
Sr Software Engineer 2
  • Consistently delivers on time and on target, even on large tasks, and defines scope to meet stakeholder expectations.
  • Leads team planning and communication, and can lead inter-team communication when needed.
  • Leads improvements in engineering best practices.
  • Provides accurate effort estimates for large initiatives, and clarifies assumptions, even when the scope is still ambiguous.
  • Ensures accumulated knowledge is being shared within the team, and inter-team as needed.
  • Coaches team members on task grooming to break work down into smaller pieces.
  • Able to optimize or tune queries/code to address performance problems.
  • During critical outages and high-impact issue investigations, facilitate and help with solutions. Ensure that the outcomes are the best for the situation in technical aspects.
  • 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.
Sr Software Engineer 3
  • Takes proactive ownership of the team’s technical scope and responsibilities, not only delivering on tasks, but also strategically establishing, creating buy-in and executing a short and long-term vision for the team’s technical direction.
  • Anticipates future needs, articulates clear plans, and secures buy-in from key stakeholders and team members.
  • Acts as a bridge between technical execution and business strategy, advocating for technical decisions that support the overall success of the organization.
  • Develops strategies to mitigate risks effectively, ensuring robustness and resilience in technical solutions.
  • Capable of making critical decisions during high-pressure situations, maintaining a focus on achieving optimal outcomes technically and business-wise.

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.
Sr Software Engineer 2
  • Makes others better through code reviews, thorough documentation, technical guidance, and mentoring or serving as a Tech Lead on a project. .
  • Understands the tradeoffs between technical and product needs to lead to solutions that take all of these needs into account and drive business outcomes.
  • Identifies and proposes strategies around technical problems affecting their team, communicates standards, and gets buy-in on solutions.
  • Able to discuss complex technical issues at an abstract level with non-technical people.
  • Strongly influences and leads team culture.
  • During critical outages and high-impact issues, clearly communicate the status and high-level impact in the appropriate public channels for visibility and awareness.
  • After a critical outage or high-impact issue is resolved, help debrief the outcomes through messages on the proper channels and/or post-mortem documents and create follow-up action items (when applicable) as a measure to prevent the issue from happening again or to be able to detect it sooner.
  • Able to analyze and execute cross-team engineering initiatives by leading the scope of implementation within own team.
  • Communicates clearly with all stakeholders, being able to articulate trade-offs and shift the priorities when necessary.
  • Helps to create buy-in on the decisions (together with the EM and PM) by helping the team to understand the “why” of the decisions being taken.
Sr Software Engineer 3
  • Thrives in communication, ensuring clarity and objectiveness for individuals with varying levels of technical expertise.
  • Able to clearly articulate pros and cons of possible options, including: costs, tradeoffs, risks, and benefits.
  • Proactively establishes the team’s technical vision and strategic direction.
  • Inspires and motivates team members towards a shared vision, cultivating a culture of innovation and excellence.
  • Helps on the professional development of team members through mentorship, knowledge sharing, and promoting continuous learning.
  • Holds the team accountable to high technical standards and best practices.

Competencies focus

Sr Software Engineer 1 Sr Software Engineer 2 Sr Software Engineer 3
  • Deliver Results.
  • Service Oriented.
  • Deliver Results.
  • Service Oriented.
  • Deliver results.
  • Strategic thinking.

reference: Individual Contributor 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.
Sr Software Engineer 2
  • Has been a tech lead for 1+ year.
  • Has participated in 3+ technical planning or designs of large Epics or engineering initiatives.
  • Has presented 3+ times on a technical topic for a PED talk, ideally based on Friday afternoon L+D initiatives.
  • Has documented 5+ technical aspects of systems implementation and/or post-mortems.
Sr Software Engineer 3
  • Has been a tech lead for 2+ years.
  • Has proposed and led 3+ large technical epics (from design to execution).
  • Has led the team on 1+ cross-teams initiative.
  • Has led the discussion and establishment of a long-term engineering plan for own team.
  • Has presented 3+ times on a technical topic for a PED talk, ideally based on Friday afternoon L+D initiatives.
  • Has documented 5+ technical aspects of systems implementation and/or post-mortems.
  • Has supported the growth of at least 1 engineer in the team.

Trending Tags