Square’s Growth Framework for Engineers and Engineering Managers

A system for leveling up at Square

Info

Since the publication of this post, we have updated our growth framework for engineers and engineering managers. You can learn about our updated growth framework in this new blog post.

At Square, we’re building products and services that help consumers and businesses participate and thrive in the economy. To accomplish this, we need to cultivate an environment where engineers can challenge themselves, achieve their goals for professional growth, and do their best work for our customers.

We’ve developed a set of principles, frameworks, and processes to support engineers as they build their skills, assume more responsibility, and grow in their careers. These clear principles and standards give engineers a roadmap for professional growth, even when interests and aspirations vary significantly from person to person. They enable a partnership with their manager to align personal goals with projects that serve our customers.

Our Software Engineering Career Ladder is a crucial element of Square’s toolkit for supporting engineers’ growth. It helps us ensure that we evaluate and reward engineers consistently and fairly, regardless of their team, discipline, or background. Every employee has a level, which describes the scope, complexity, and impact of their role and factors into compensation.

We’re sharing our engineering level definitions and principles to provide a window into how Square thinks about growth and development for engineers and engineering managers. We want to help prospective candidates understand how they’re being evaluated during the interview process and what expectations will look like when they start at Square. Our levels don’t line up perfectly with those of other companies: some have more levels, some have fewer, some are more granular, some less, and some have very different paces for promotion. You likely can’t accurately compare level numbers or titles directly between companies, even with tools that provide mappings between companies. It’s best to consider the actual criteria that define a Square level.

See our Engineering Career Ladder →

Guiding Principles

As We’ve Refined Our Software Engineering Career Ladder Over Time, We’ve Converged On a Set Of Guiding Principles That Reflect Our Values As An Engineering Organization And That We Believe Support Engineers’ Growth Most Effectively. Here Are Some Of The Most Important Ones

• Two Tracks: Engineers and Engineering Managers are on two distinct career tracks. This ensures that an engineer can grow in their career and take on more responsibility without having to become a manager. While there are some overlapping responsibilities between the roles, the skills and motivations necessary to be effective can vary dramatically. We want engineers to consider becoming managers if they are interested in the core responsibilities of people management; if they aren’t, we provide a path to take on larger scope and demonstrate leadership as an individual contributor. This helps ensure we don’t create an incentive to change roles for the wrong reasons. Engineers and managers at the same level will have comparable scope and impact on the business.
• Becoming a manager is not a promotion: As discussed in more detail below, we define a promotion as moving up a level. When an engineer first becomes a manager, they remain in the same level and move laterally to the engineering management track. Again, we don’t want to incentivize becoming a manager solely for career advancement.
• Scope & Impact vs. Behaviors: Our level criteria are organized into two major sections: Scope & Impact and Behaviors. Scope & Impact contain the defining criteria of a level. To be meeting the expectations of that level, an engineer or manager must be meeting every Scope & Impact criterion. We also enumerate a set of behaviors that exemplify that level of scope and impact. These are organized into categories like Technical Execution and Team Building. While we don’t expect everyone to demonstrate every single behavior listed for their level, we do need to see criteria from every category.
• Years of experience: We do not have strict minimum requirements for years of experience at any given level. We evaluate scope of responsibility and impact, and we never want to fail to recognize high performance because of a litmus test like years of experience. Our ladder does contain years of experience guidance to help set expectations, though. It takes time to demonstrate a track record of performance, to get the breadth of experience necessary to succeed at higher levels, and to assess the impact of long-term decisions.
• Generalized across teams and disciplines: Square has a wide variety of software engineering disciplines, including backend, frontend, mobile, security, and embedded to name a few. We also have many business units, products, and teams. We’ve written a single set of levels to apply to all software engineers across disciplines and teams. By ensuring we have consistent standards across the company, we can enable fluid internal mobility and further support individual growth. Engineers can broaden their skillset and perspectives by working on a wide range of products and problems.
• Levels build on each other: Each level implicitly includes all criteria and responsibilities of prior levels.