This document represents the positions and salary levels that 2i2c uses. They are inspired by the hiring/salary structure of several tech companies1.
Each position at 2i2c takes the following form:
<role-name> L<level> - S<step>
For example, Open Source Infrastructure Engineer L2 - S3.
Here is a quick breakdown of this terminology and structure:
Positions are specific areas of focus and skills in 2i2c. The expectations and focus-areas within that role are set by Levels and Steps.
Levels are large and distinct jumps in terms of area knowledge, role complexity and overall scope. Higher levels generally mean less-oversight and more autonomy, higher expectations of quality, more work on design / strategy than implementation, etc.
Four steps are housed within each level and are meant to mark smaller milestones of growth in terms of ownership and initiative, as well as experience in the current role. These are generally not part of public materials, but are
Positions at 2i2c¶
Below is a list of positions that 2i2c currently uses.
Open Source Infrastructure Engineer¶
The Open Source Infrastructure (OSIE) focuses on infrastructure that supports interactive computing. It intersects job titles such as “dev-ops engineer”, “site reliability engineer”, “software engineer”, and “cloud engineer”. This person should have experience with cloud infrastructure. They generally both operate 2i2c Hubs, as well as develop technology for them. In general, a minority of time should be spend operating hubs - we want to use operations as an opportunity to drive development and minimize human-in-the-loop maintenance.
Senior Open Source Infrastructure Engineer¶
The Senior Open Source Infrastructure Engineer (SOSIE) role is designed to help guide our team and cultivate a healthy and productive culture. It is heavily inspired by On being a senior engineer.
This role focuses their efforts on our infrastructure, but spends a lot of their time guiding others, focusing on particularly complex infrastructure design and development, and interfacing with other teams and stakeholder communities to help guide our development. Below is a short list of expectations for this role.
Solve complex technical problems with broad, cross-project scope, often involving co-ordination with multiple teams across different open source projects.
Acts as a point of escalation for complex technical problems, preferring to solve them with collaborative guidance rather than ‘just doing it’.
Coordinate with product/business teams on roadmap priorities, and provide implementation suggestions and effort estimates.
Provide guidance on major strategic questions in infrastructure and engineering team strategy
Helps grow other engineers via mentorship, code & design review, and sponsorship to find opportunities for them
Act as a role model for positive, inclusive, and constructive team dynamics.