Enova has decided to open source it's career ladders. You can find background on why we created new ladders here and why we open sourced them here.
There's 6 ladders contained:
- core_engineer - This is the basis of every team member, regardless of your specific focus.
- software_engineer - Software Engineer Ladder
- software_ui_engineer - Software UI Engineer Ladder
- software_test_engineer - Software Test Engineer Ladder
After you become a Lead Engineer, you can select to either go into the Individual Contributor track or the Mangement track:
- individual_contributor - Principal Engineer Ladder
- mangement - Manager Ladder
Each position is meant to build on the position before it. So a Sr. Software Engineer II is expected to fulfill everything found in the Software Engineer I, II and Sr. Software Engineer I descriptions.
The ladders also progress in terms of what each position impacts: starting with a project, moving to your team, core, SE, tech and, finally, to the company.
Within the ladders there's some Enova specific terminology:
- Core - We have organized teams focused on either specific products or internal operations. These core teams don't change that often. This is the bulk of our team.
- Ranger - The remaining engineers are broken out into 4 person ranger teams. These teams are assigned every 6 weeks during a company wide prioritization process known as EPG.
- SE - Software Engineering
- Architecture Council - Large, cross functional team made up of members of SE, IT, Analytics, Data Services and TechOps that help organize company wide projects and initiatives.
Markdown doesn't represent tables / matrices well. GFM only supports single line table cells, so they wouldn't work here. If you have some suggestions, please, open up an issue, or better yet, submit a PR.
Feedback is welcome. Feel free to ping Griffin Caprio with questions or comments.
These Career Ladders are released by Enova under the MIT License.