An engineering career ladder defines what it takes to move from one level to the next, and who signs off on the move. Get it right and a promotion conversation takes ten minutes because everyone already agrees on the bar. Skip it and every raise turns into a negotiation won by whoever argues hardest. The frameworks below come from real, public ladders (Etsy's, James Shore's, the more than 30 companies collected on GitHub), but none say what to do when part of your team is a contractor or a nearshore engineer rather than a direct hire. That gap is worth closing before you write the document.
What is an engineering career ladder?
An engineering career ladder is a written framework that maps titles to expected skill, scope, and impact, and states plainly what separates one level from the next. It isn't a job description or a performance review template, though it feeds both.
Coderpad's breakdown of career ladder components splits the work into five pieces most frameworks evaluate in some form: craft, delivery, culture, leadership, and strategic impact. A senior engineer and a staff engineer can write equally good code; what usually separates them is leadership and strategic impact. Stack Overflow's 2019 developer survey found that about 43% of engineers ranked professional development among their top three job priorities, the retention case for building a ladder at all.
Treat the document as living, not a file written once and left in a wiki. Titles drift, and a ladder nobody revisits stops describing what people actually do within a year or two. A career ladder is one of the recurring documents covered in Engineering management guides for CTOs and VPs of Engineering.
IC track vs. management track: how the dual ladder works
Not every strong engineer wants to manage people, and making management the only path to more money is a fast way to lose your best individual contributors to a company that built a second track.
Amazingcto's Y-shaped career ladder is sized for a 10-50 engineer company. Everyone starts on one shared track (intern, junior, developer, senior, tech lead), then splits into a management branch (team lead, engineering manager, VP engineering, CTO) and a senior IC branch (staff, principal, fellow). The split point matters more than the level count: engineers choose a lane once they've proven themselves at tech lead, not on day one before they know which kind of work they prefer.
Jorge Fioranelli's Engineering Ladders framework names four separate paths (developer, tech lead, technical program manager, engineering manager), each scored across five dimensions: technology, system, people, process, influence. That's more structure than most 10-50 engineer companies need on day one, but the dimension breakdown is worth stealing: it forces you to say explicitly that a tech lead needs more system scope than a senior developer.
Not everyone splits the ladder at all. James Shore's proposed engineering ladder, published in April 2024, runs a single track from associate software engineer through principal engineer on a four-point skill scale, handling specialization (security, infrastructure, mobile) as a label on top of a level rather than a separate branch. That works when a team is small enough for a principal engineer and an engineering manager to coordinate directly, no second ladder in between.
How many levels do you actually need?
Etsy's public engineering ladder is IC only, with no management track: Engineer I, Engineer II, Senior Engineer I/II, Staff Engineer I/II, Senior Staff Engineer, Principal Engineer. It's proof a ladder doesn't need a management branch to be useful, just a clear top rung for engineers who never want one.
| Framework | Levels | Tracks | Source |
|---|---|---|---|
| Etsy | 8 | IC only | Etsy's public engineering ladder |
| James Shore | 6 | Single track | Published April 2024 |
| Amazingcto | 5 shared, then 7 across two branches | IC and management, split after level 5 | Y-shaped ladder for 10-50 engineers |
| Engineering Ladders | 5 per path | 4 paths (developer, tech lead, TPM, engineering manager) | Jorge Fioranelli's framework |
| Microsoft | 13 | Not disclosed | Coderpad's level-count comparison of Microsoft and Amazon |
| Amazon | 6 | Not disclosed | Same comparison |
The range runs from 6 to 13 among companies with thousands of engineers, and 5-8 among the smaller frameworks above. There's no single right number. What matters is that every level someone can name in the room maps to a real difference in scope.
Public engineering ladders you can borrow from
Ben Moeskau's GitHub collection links to more than 30 companies that have published their engineering ladders, including Artsy, Basecamp, Buffer, Dropbox, Etsy, and GitLab. Each was tested against a real team: a faster starting point than a blank document, provided you're honest about how much of it fits your size.
When to copy a public ladder vs. write your own
A 13-level structure built for a company the size of Microsoft solves a coordination problem that doesn't exist at 15 engineers: too many titles for too few people. Most published frameworks are sized for the company that wrote them, not a 10-50 engineer team hiring its second batch of senior engineers. Start smaller than whichever one you're borrowing from, and add a rung only once more than one or two engineers would sit on it.
Where contractors, nearshore, and augmented engineers fit on the ladder
None of the frameworks above address engineers who aren't full-time hires. Etsy's ladder, Fioranelli's framework, and the more than 30 companies in Moeskau's collection all assume a direct employee on the company's payroll. That's a real gap once a team is blended: a contractor covering one initiative, a nearshore engineer on a multi-year engagement, or an augmented senior engineer filling a role the internal team can't hire for fast enough.
Should an augmented or nearshore engineer be leveled at all?
Yes, informally at minimum. Even if an external engineer never appears on your compensation bands or promotion cycle, whoever manages them day to day needs a working answer to whether that person operates at a senior level or a mid-level one, since that decides what they're trusted to own without a second review. Skipping the exercise doesn't remove the judgment call, it just makes it implicit and inconsistent across managers.
Mapping an external senior engineer onto your internal levels
Map on scope and judgment, not tenure or a previous title. A nearshore engineer with eight years at a mid-sized product company and a "senior developer" title back home might land cleanly on your senior engineer rung, or a level higher if they're already making architectural calls unsupervised. Titles imported from a different company's ladder rarely translate directly: a partner firm's "lead engineer" might sit anywhere from your tech lead rung to your staff level, depending on how that firm defines the word.
The safest anchor is the same craft, delivery, culture, leadership, and strategic-impact breakdown used internally: do they design a subsystem unsupervised, mentor other engineers, or make a call that affects the roadmap.
What changes when the ladder includes external seats
Review cadence usually needs to shrink at first. A quarterly check-in that works for a direct hire someone sees in the office doesn't surface enough signal for an engineer a manager only talks to twice a week over video. Ownership of the promotion conversation should stay with someone on the contracting side, not the vendor, for the same reason a ship decision on a blended team belongs to whoever's headcount is accountable for the outcome.
Composition matters too. Agile team structure guidance on keeping an in-house seniority floor on blended teams applies directly here: an external hire's place on the ladder only means something if there's an internal anchor senior enough to judge it.
Vetting on the way in changes the starting point of that conversation. HighCircl runs a four-stage, engineer-led process before a candidate reaches a client: background and experience verification, a communication and product-thinking assessment, a take-home technical project, and a live technical session on architectural reasoning. Roughly 1 in 10 applicants clear all four stages.
Common mistakes when building a career ladder
Two show up more than any others. The first is over-engineering the ladder for the team's real size, borrowing a structure built for thousands of engineers and expecting it to hold together at twenty. Start with a handful of levels and add rungs only when engineers actually fill them.
The second is treating the ladder as a document written once and left alone. A ladder nobody revisits drifts from what the team is actually doing, and the promotion conversation reverts to whoever advocates hardest for themselves once the written definition stops matching reality.
Building the ladder is itself a timing question. What a CTO owns at each startup stage ties a formal leveling framework to the Series B stage, not before. Once the ladder exists, it feeds the next planning cycle too: how to build a technical roadmap as a CTO has to account for hiring and capacity timing.
FAQ
How many levels should an engineering career ladder have?
Published examples range from 6 (Amazon) to 13 (Microsoft) among large companies, and 6-8 among smaller public frameworks like Etsy's and James Shore's. Pick the smallest set where each rung maps to a real difference in scope, and add more only once engineers actually fill the gap.
What's the difference between an IC ladder and a management ladder?
An IC ladder rewards technical ownership without requiring anyone to manage people; a management ladder rewards the ability to grow and run a team. Amazingcto's Y-shaped model splits the two at the tech lead level, after engineers have proven themselves on a shared track. Some ladders, like James Shore's, skip the split and run one track with specialization layered on top.
How do you level a contractor or nearshore engineer on an internal ladder?
Map them on scope and judgment rather than tenure or their previous title, using the same craft, delivery, culture, leadership, and strategic-impact criteria applied internally. HighCircl's four-stage vetting process already tests architectural reasoning and product thinking before a candidate reaches a client, and roughly 1 in 10 applicants clear it.
When should a startup build a formal career ladder?
Once informal, verbal agreements about who's senior and who isn't stop scaling, when a manager can no longer personally vouch for every promotion decision. Before that point, a lightweight, one or two-track version is enough.