Sr Software Engineer 2 (Sr Individual Contributor Path)

5 to 8

8+

10+

1-2 Products / Key components

2-3 Products / Key components

Whole platform

• 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 expert on 2 products / key components, solid on the rest of the platform.
• Expert in primary focus area (BE/FE/Data/or DevOps).
• Strong proficiency in DevOps, PG/CH, Observability, and other platform technologies.

• Technical expert in most key components and solid on 2 products.
• Expert in primary focus area (BE/FE/Data/or DevOps).
• Strong proficiency in all other technologies across the codebase and infrastructure.

• 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.

• 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.

• Leads cross-teams projects and initiatives, and inter-team communication.
• Identifies org-level opportunities, prioritizes, plans, and creates buy-in for resolution.
• Mentors engineers and fosters their growth.
• Coaches teams to continuously improve delivery pace and quality.
• Can step in as a contributor on any team when needed.
• Able to suggest when/how projects could take shortcuts and still maintain quality to satisfy our customers.
• Self-guided in a professional way, do their own prioritization when needed.
• Uses data and facts to debate technical architecture with team members and stakeholders to gain buy-in.
• Take the lead on following up on the incidents that happened, proactively looking into ways to improve the systems to avoid those same issues from happening again, and/or improve monitoring to detect those sooner whenever applicable.
• Fosters cost-awareness by advocating for initiatives that lead to savings, and diligently monitoring spending across existing systems.
• Comfortable with navigating ambiguity, being able to define the next steps of own scope that align with Engineering and the company’s needs.

• 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.

• 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.

• Multiplies the effectiveness of others by facilitating cross-team work.
• Primarily acts as a multiplier by building systems, authoring tools, or introducing policies or patterns that raise the level of productivity of the entire org.
• Listens and guides debates to help reach decisions, drives commitment and accountability; clearly communicates to and backs all stakeholders.
• Sets medium-term strategic technical direction, able to look ahead 6 months, identify the areas of greatest need across the engineering org, create plans to improve them, and build teammate and exec buy-in around the plan.
• Serves as a technical advisor and works closely with senior management.
• Clearly communicate the status and impact of critical outages and high-impact issues in the appropriate public channels for visibility and awareness.
• Consistently provides feedback to engineers, with the intention of supporting their career growth and professional development.
• Leverage communication and expertise by working closely with the teams to ensure that cross-team work is being executed successfully, within the scope and timelines required.

• Deliver Results.
• Service Oriented.

• Deliver Results.
• Service Oriented.

• Deliver results.
• Stretegic thinking.

• Sr Backend Engineer
• Sr Fullstack Engineer
• Sr Data Engineer (Algo)
• Sr DevOps Engineer

• Sr Backend Engineer
• Sr Fullstack Engineer
• Sr Data Engineer (Algo)
• Sr DevOps Engineer

• Staff Engineer

• 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.

• 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 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 been a tech lead for 2+ years.
• Has championed and executed 2+ technical migrations or large multi-months platform/staff projects.
• Has documented 10+ technical aspects of systems implementation and/or post-mortems.
• Has championed the promotion of 2+ engineers.