CareerPlug's reaches

Reaches exist to help with uniformity (the only area we believe should have some uniformity). Associates, Mids, Seniors, Principals, Managers, Directors, VPs, etc. These are all prefixes to titles throughout an organization. We've found that it brings a tremendous amount of clarity if they have a common meaning.

This common meaning, we believe should be the expected impact. In other words, regardless if you are an associate or a senior engineer... you both are engineers. However, the associate/junior is expected to impact the work that they are given. However, a senior is expected to impact the team, their discipline, and maybe the entire department.

This construct was borrowed from  Spotify's Steps Career Framework.
  • 1.1

    As an associate I's, we are expected to be able to do the work with significant help.


    This is what Spotify calls the Individual Step.

    At this step, you are focused primarily on being a useful contributor, gaining experience and learning how to be effective on their team. It is not expected that a member of technology would remain at this step during their entire time at Spotify. At this step, your focus should be on growing so that you can support your team. This is the only step where there is an expectation that all members of technology should move toward the next step.

  • 1.2

    As an associate II's, we are expected to be able to complete our work with little supervision over the day-to-day.


    This is what Spotify calls the Individual Step.

    At this step, you are focused primarily on being a useful contributor, gaining experience and learning how to be effective on their team. It is not expected that a member of technology would remain at this step during their entire time at Spotify. At this step, your focus should be on growing so that you can support your team. This is the only step where there is an expectation that all members of technology should move toward the next step.

    • --No positions defined at this reach level--
  • 1.3

    As an associate III's, we are expected to be able to do our work with very little help.


    This is what Spotify calls the Individual Step.

    At this step, you are focused primarily on being a useful contributor, gaining experience and learning how to be effective on their team. It is not expected that a member of technology would remain at this step during their entire time at Spotify. At this step, your focus should be on growing so that you can support your team. This is the only step where there is an expectation that all members of technology should move toward the next step.

    • --No positions defined at this reach level--
  • 2.1

    As an intermediate I, we are able to fulfill our roles with nearly no supervision and can tackle projects that our squad deem medium priority


    This is what Spotify calls the Squad/Chapter Step.

    At this step, you are a resource for your chapter or your squad, either as a domain specialist for your team, or as a generalist/problem solver for them. You should be able to lead smaller efforts coordinating with other members of your team and drive them to completion and/or dig into tough problems and solve them independently taking in feedback from your peers and focusing on the outcome.

  • 2.2

    As an intermediate II, we are able to fulfill our roles with no supervision and can tackle projects that our squad deem medium to high priority


    This is what Spotify calls the Squad/Chapter Step.

    At this step, you are a resource for your chapter or your squad, either as a domain specialist for your team, or as a generalist/problem solver for them. You should be able to lead smaller efforts coordinating with other members of your team and drive them to completion and/or dig into tough problems and solve them independently taking in feedback from your peers and focusing on the outcome.

  • 2.3

    As intermediate III's, we are able to fulfill our roles with no supervision and can begin to lead projects that our squad deem high priority with some guidance from a senior.


    This is what Spotify calls the Squad/Chapter Step.

    At this step, you are a resource for your chapter or your squad, either as a domain specialist for your team, or as a generalist/problem solver for them. You should be able to lead smaller efforts coordinating with other members of your team and drive them to completion and/or dig into tough problems and solve them independently taking in feedback from your peers and focusing on the outcome.

    • --No positions defined at this reach level--
  • 3.1

    As seniors/managers, we are able to fulfill our roles with no supervision and lead projects that our squad deems a high priority.


    This is what Spotify calls the Tribe/Guild Step.

    At this step, you have an impact across squads or chapters. You are a resource for a larger group as a domain expert or generalist. You will lead cross-team (squad/tribe/chapter) efforts involving more people and drive them to completion and/or you will take on large challenges, working with diverse stakeholders in multiple teams to solve a problem that affects your larger organization.

  • 3.2

    As seniors/managers, we are able to fulfill our roles with no supervision and lead projects that our squad deems a high priority.


    This is what Spotify calls the Tribe/Guild Step.

    At this step, you have an impact across squads or chapters. You are a resource for a larger group as a domain expert or generalist. You will lead cross-team (squad/tribe/chapter) efforts involving more people and drive them to completion and/or you will take on large challenges, working with diverse stakeholders in multiple teams to solve a problem that affects your larger organization.

    • --No positions defined at this reach level--
  • 3.3

    As seniors/managers, we are able to fulfill our roles with no supervision and lead projects that our squad deems a high priority.


    This is what Spotify calls the Tribe/Guild Step.

    At this step, you have an impact across squads or chapters. You are a resource for a larger group as a domain expert or generalist. You will lead cross-team (squad/tribe/chapter) efforts involving more people and drive them to completion and/or you will take on large challenges, working with diverse stakeholders in multiple teams to solve a problem that affects your larger organization.

  • 4.1

    As directors and principals, we are responsible for org design as well as being principals in our craft for the entire organization.


    This is what Spotify calls the P&E/Company Step.

    At this step, your focus is significantly on supporting P&E-wide or company-wide initiatives. You will Road Manage projects that span tribes and be responsible for solving Tech-wide problems, and/or you will also represent P&E in the company and/or industry forums, and/or you will be a go-to person across the company to solve very complex problems

  • 4.2

    As directors and principals, we are responsible for org design as well as being principals in our craft for the entire organization.


    This is what Spotify calls the P&E/Company Step.

    At this step, your focus is significantly on supporting P&E-wide or company-wide initiatives. You will Road Manage projects that span tribes and be responsible for solving Tech-wide problems, and/or you will also represent P&E in the company and/or industry forums, and/or you will be a go-to person across the company to solve very complex problems

    • --No positions defined at this reach level--
  • 4.3

    As directors and principals, we are responsible for org design as well as being principals in our craft for the entire organization.


    This is what Spotify calls the P&E/Company Step.

    At this step, your focus is significantly on supporting P&E-wide or company-wide initiatives. You will Road Manage projects that span tribes and be responsible for solving Tech-wide problems, and/or you will also represent P&E in the company and/or industry forums, and/or you will be a go-to person across the company to solve very complex problems

    • --No positions defined at this reach level--
  • 5.1

    • --No positions defined at this reach level--
  • 5.2

  • 5.3

    • --No positions defined at this reach level--
  • 6.1

    • --No positions defined at this reach level--