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

Sr Software Engineer 1 (Individual Contributor Path)

Years of experience (guideline)

Software Engineer 3 Sr Software Engineer 1

4 to 6

5 to 8

Scope of action

Software Engineer 3 Sr Software Engineer 1

Epic / Project

1-2 Products / Key components

Role Description

Software Engineer 3

An experienced engineer and expert in one product area who drives team-level planning and communication while delivering on larger tasks independently. They evaluate scope to right-size solutions, break down and estimate large initiatives, and participate in improving engineering best practices. They contribute to design docs, mentor through code review, and help resolve issues in their area of expertise.

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.

Scope of knowledge (Breadth and Depth)

Software Engineer 3
  • Solid technical understanding of 1 product / key component.
  • Expert in one technology on one part of our stack.
  • Strong proficiency in primary focus area (BE/FE/Data/or DevOps).
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.

reference: Products and key components (internal link)

Responsibilities

Software Engineer 3
  • Solid understanding of the product and ways that our customers use it. Evaluates scope to right-size a solution based on this understanding.
  • Consistently delivers on time and on target, even on larger tasks when given a clear definition.
  • Comfortable troubleshooting issues in their area of focus.
  • Regularly participates in team-level planning and drives some team-level communication.
  • Able to break down and estimate large initiatives.
  • Writes code in a style consistent with the codebase, creates tests for their work.
  • Participates in improving engineering best practices.
  • During critical outages or high-impact issue investigations, participate in group calls if in your area of focus. Help come to a solution when it is in your area of expertise.
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.

Communication and leadership

Software Engineer 3
  • Gives timely, helpful feedback to peers and managers.
  • Understands how their work fits into the larger project and identifies problems with requirements.
  • Proactively and thoughtfully communicates with team in regards to questions, assumptions, blockers, and changes of estimated timeline.
  • Participates in team events, both within engineering and the broader team at Beyond.
  • Contributes to design docs and Tettra articles.
  • During critical outages or when there is a high-impact issue, clearly communicate the status and high-level impact in the appropriate public channels for visibility and awareness.
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.

Competencies focus

Software Engineer 3 Sr Software Engineer 1
  • Deliver Results.
  • Inclusion.
  • Deliver Results.
  • Service Oriented.

reference: Individual Contributor competencies (internal link)

Checkpoints for reaching this level

Software Engineer 3
  • Has owned development, deployment, and improvements of multiple product features.
  • Has paired with teammates on a regular cadence (once every one or two weeks is recommended) for 12+ months.
  • Has reviewed other engineers’ contributions through pairing or PRs weekly for 6+ months.
  • Has broken a Jira epic down into smaller pieces.
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.

Trending Tags