Engineering · Individual contributor
The individual-contributor path for engineers. A guideline for conversations, not a checklist. · 5 roles
Engineer I
Delivers well-defined tasks with guidance.
- Craft
- Delivers well-scoped changes with tests, asking for help when stuck.
- System design
- Explains how the parts they work on fit into the system.
- Ownership
- Follows their work through to release and fixes what they break.
- Collaboration
- Asks for and acts on code review feedback.
- Communication
- Keeps the team informed about progress and blockers.
Engineer II
Delivers features independently.
- Craft
- Delivers features end to end with little guidance and leaves the code better than they found it.
- System design
- Designs components within an existing system and documents the choices.
- Ownership
- Takes responsibility for a feature in production, including its bugs and alerts.
- Collaboration
- Reviews others' work constructively and pairs when useful.
- Communication
- Writes clear descriptions of their changes and decisions.
Senior Engineer
Leads significant work and raises the level of the team.
- Craft
- Sets the technical standard on the team through their own work and reviews.
- System design
- Designs systems spanning several components and explains the trade-offs to the team.
- Ownership
- Leads a project from ambiguity to delivery, including the parts nobody owned.
- Collaboration
- Works with product and other teams to shape what gets built.
- Mentorship
- Helps teammates grow through regular, specific guidance.
Staff Engineer
Shapes technical direction across teams.
- Craft
- Solves the technical problems others get stuck on and makes the solutions reusable.
- System design
- Designs systems spanning several teams and gets agreement on the trade-offs.
- Ownership
- Identifies the most important technical problems across teams and gets them solved.
- Collaboration
- Aligns several teams around a shared technical plan.
- Mentorship
- Grows senior engineers into technical leaders.
Principal Engineer
Sets technical direction for the organization.
- Craft
- Defines engineering practices the whole organization adopts.
- System design
- Sets the long-term architecture and explains it to technical and non-technical audiences.
- Ownership
- Takes responsibility for the organization's most critical technical risks.
- Collaboration
- Partners with leadership on technical strategy.
- Mentorship
- Builds a bench of technical leaders across the organization.