Disclaimers

This levels framework is intentionally sparse. To reach the next stage, each one of us will need to stretch ourselves and extend our ownership boundaries as far as possible. We can’t possibly predict what’s around the next corner, and we are a very small team, so we can’t set precise expectations for each other.

Why have levels at all then?

Primarily because:

• We need to set compensation for new hires, and we believe the right way to do that is with a structured framework organized around impact.
• Even an imprecise definition of expectations will be much more helpful for new hires than none at all.

Design principles

We have aimed to make each level similar in scope to those at big companies like Google, Facebook, and Dropbox. We have also simplified this a bunch to reflect the ambiguity we face as an early stage company.

L2-L5 Software engineer

Note that expectations accumulate — i.e. L3 expectations are a superset of L2.

• Defines “how”
• Delivers individual features independently
• Balances velocity and quality | - Proactively identifies new problems and solves them | | L3 | Projects
• Defines both “what” and “how”
• Delivers entire projects independently
• Defines product and design requirements | - Drives product and technical decision-making | | L4 | Systems
• Delivers larger, more ambiguous systems
• Identifies unstated requirements and balances requirements along multiple dimensions | - Defines and meets success criteria
• Designs simple systems for the near future | | L5 | Products
• Ensures positive business impact
• Prioritizes at the company level | - Innovates e.g. by introducing new methods, ideas, or products |