Skip to content
v2.0 Plato Engineering Career Ladders
Share
Explore
Engineering Career Ladders v2.0
We invite you to explore our growing collection of public Engineering Career Ladders and Rubrics gathered across various industries around the world. Feel free to explore, or log in to contribute your own ladders and rubrics.
Currently, a total of
20 public career ladders/rubrics have been added!
Which career ladder & rubric would you like to view?
Select a track:
Individual Contributor
Select a company career ladder:
Envoy's Engineering
Envoy's Engineering
Career Ladder*
View all roles/functions in this ladder
Level #/Code (Req'd)
Roles/Functions
Additional information
1
Band 1
Engineer I
N/A
2
Band 2
Engineer II
N/A
3
Band 3
Engineer III {Senior Engineer}
N/A
4
Band 4
Staff Engineer
N/A
5
Band 5
Principal Engineer
N/A
6
Band 6
Unlimited
N/A
No results from filter
SELECT TWO LEVELS TO COMPARE:
Select a level
THEN
Select another level
Clear to refresh / view all
1
Band 2 // Engineer II
Band 4 // Staff Engineer
Clear filter/Refresh data
There are no rows in this table
Band 2 // Engineer II
3
Band 4 // Staff Engineer
3
Scope
2
You will own a small component or project, guiding it from inception through completion in a timely manner.
You design solutions to medium complexity problems, managing simplicity, completeness, performance, and risk-tolerance.
You will seek and incorporate reviews; handle testing, instrumentation, deployment, and monitoring.
You will provide thoughtful, constructive code reviews.
You will take on mentorship of more junior engineers, highlight their accomplishments, and help them find their way in the organization.
You will participate in an on-call rotation, applying your expertise to solve problems where you’re familiar, or helping to find the right person to solve the problems where you’re not.
You will own large components, systems, or projects, coordinating and communicating with teams and leads across the organization.
You will design solutions to high complexity problems, with high-availability and high-reliability in mind.
You will instigate design discussions and facilitate engineering-wide learning.
You will represent engineering across the organization.
You will be the primary driver of resolving production issues, holding post-mortems, and owning long-term fixes.
You will take on independent greenfield projects with an eye to furthering the products and services of the organization.
You help decide when it is appropriate to spike or create an MVP in order to ensure we learn quickly, and can rally the team around the appropriate tradeoffs needed to do so.
Skills & Experience
2
You have a background and experience in software development — a Computer Science degree (or comparable) and several years’ working experience in non-trivial software development.
You possess a deep understanding of computer science fundamentals: data structures, algorithms, and strategies.
You have in-depth knowledge of multiple programming languages, frameworks, and/or specialized systems. You are able to discern and articulate the relative merits of each.
You have knowledge of how the internet and networking works (i.e. DNS, HTTP, TLS, Certificates, etc) and the tools and services that enable people and devices to connect to services (e.g., browsers, CDNs, proxies, etc).
You have some knowledge of and experience with how systems work at scale (e.g. threads, virtualization, configuration management, load balancers, caching).
You are skilled in managing your time and the projects you lead or are a part of and can leverage processes, ceremonies, and tools to do so.
You have a deep understanding of the landscape of our codebases, components, and services.
You have a mastery of your primary languages and frameworks.
You are up to date with the landscape of technologies and techniques and able to evaluate their impact on the organization and its products and services.
You understand and drive techniques for improving engineering productivity.
You are experienced with a wide variety of development approaches, patterns, and implementation styles.
Behaviors & Mindset
2
You're championing quality through your own coding practices.
You are actively working to hone your craft and be a better programmer.
You seek to learn more about the organization, our business, and problem domain.
Testing is a natural part of your workflow; you feel better when you're shipping a test. You guarantee your software and are the first to know if something is amiss.
You enjoy participating in and providing feedback on design and code reviews. You're socializing and testing your designs for components/modules before cutting code.
You are accountable: if you ship something you own it from inception to production.
You are collaborative: you work with other engineers on solutions that cut across teams/technologies.
You can work independently: you manage your own time efficiently with a strong sense of prioritization.
You can manage your workload: you communicate frequently and honestly to stakeholders and yourself about the work you commit to.
You are fast-paced: you love the speed of and impact you have in startups. You set aggressive milestones for yourself and do extra to meet them.
You are actively seeking out opportunities to teach and mentor fellow team members.
You are actively pushing back on over-engineered solutions. Conversely, you are advocating for improving under-implemented solutions.
You are quick to revisit past assumptions - the solution that worked 'then' may not be the right solution for 'now.'
You help determine team goals, KPIs, and projects necessary to deliver on those goals / measure KPIs.
You actively contribute to motivating and growing the team. You're asked to provide performance feedback and input on opportunities for individual growth.
You are a picture of responsibility and accountability. The organization depends on you.
You play a key role in hiring and promoting the organization as an employer.
All product names, logos, and brands are property of their respective owners in the United States and/or other countries
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.