Software developer career path: from junior to senior, lead and beyond
Each step up the software developer ladder, from junior to lead and beyond: what changes in the job, the gap to close, how to show it on your CV and in interviews, and a realistic plan.
The cvscored team
Contents
The ladder at a glance
| Step | What you are measured on next | Typical time |
|---|---|---|
| Junior software developer to software developer | Tasks you finish without help, tested | 1 to 2 years |
| Software developer to senior software developer | Features you own end to end, and their quality | 2 to 4 years |
| Senior to lead software developer | A team's technical direction and delivery | 2 to 3 years |
| Lead to software architect | Designs that several teams build on | 2 or more years |
| Lead to engineering manager | People, hiring and a team's results | After leading a team |
| Engineering manager to head of engineering | Several teams, budgets and the engineering strategy | 3 or more years |
Two specialist ladders run beside this one up to lead and then join it for the general steps: apps for phones on the mobile developer career paths, software inside devices on the embedded software engineer career paths.
Lead developers who choose people over code take the management road; its steps beyond the first engineering manager role, through senior engineering manager and director to VP of engineering, are on the engineering manager career paths.
The people who write the guides and API references for what developers build have a ladder of their own, from junior technical writer to head of documentation, on the technical writer career paths.
If your work is configuring the Salesforce platform rather than coding on it, the road up to Salesforce solution architect is described on the Salesforce consultant career paths.
The steps up to lead
Junior software developer to software developer
What changes: you take a ticket from start to finish on your own: understand it, ask the right questions, write the code with its tests, and get it through review and release.
The gap: confidence in one language such as JavaAsked in 20% of software developer ads (as of 5 Nov 2026).Modern Java (records, streams, generics) in a framework such as Spring, with tests and a build tool. or PythonAsked in 26% of software developer ads (as of 5 Nov 2026).Clean, tested Python: a small web service or a script others can run, with types, tests and packaging., unit testsAsked in 8% of software developer ads (as of 5 Nov 2026).Fast tests for one piece of logic each; they run on every change and fail for one reason., GitAsked in 33% of software developer ads (as of 5 Nov 2026).Branches, pull requests, a clean history, and fixing a merge conflict without panic. and pull requests, reading unfamiliar code, and debugging with logs instead of guesses.
On the CV and in interviews: one line per feature you shipped, with what it did and one result. Expect a coding round and questions on how you test and how you handle review comments.
Plan (6 to 12 months, on the job): take one small feature end to end each month; write the tests before asking for review; fix one bug a week in an area you do not know; read the team's best code reviews and copy what makes them good.
Software developer to senior software developer
What changes: you own a feature or a service, not just tasks: its design, its quality, its behaviour in production and its documentation. Others ask you for advice and you review their work.
The gap: design with trade-offs, API designAsked in 6% of software developer ads (as of 5 Nov 2026).Design an HTTP API with clear resources, status codes, versioning, paging and helpful errors., databases and performance (SQLAsked in 18% of software developer ads (as of 5 Nov 2026).Write joins and aggregations, read a query plan, and know when an index helps., indexes), CI/CDAsked in 29% of software developer ads (as of 5 Nov 2026).Every change is built and tested automatically; a green pipeline can ship, a red one stops the release. and production support, design patternsAsked in 1% of software developer ads (as of 5 Nov 2026).Named solutions to common design problems (adapter, strategy, observer); use them when they make code simpler. used with judgement, and helping newer colleagues.
On the CV and in interviews: one line per system you owned, with a measured result such as speed, errors or cost. Expect a system design round and a story about a production incident and what you changed after it.
Plan (9 to 12 months, on the job): lead the design of one feature and write it up for review; join the on-call rota or the incident reviews; mentor one junior; take one performance or reliability problem and measure it before and after.
Senior software developer to lead software developer
What changes: you are responsible for how a team builds, not only for your own work: the technical plan, the standards, the reviews, and unblocking others. You write less code and spend more time on decisions and people.
The gap: planning work across a team, breaking big goals into deliverable pieces, technical decision records, running good reviews and meetings, managing risk, and explaining technical choices to product owners and managers in agileAsked in 10% of software developer ads (as of 5 Nov 2026).Short cycles of planning, building and showing work; adjust the plan from what you learn. planning.
On the CV and in interviews: the team's size, what it delivered under your technical lead, and standards you introduced. Expect questions on a disagreement you settled and a project that slipped.
Plan (12 months): act as tech lead for one project; write the team's decision records; run the planning for one quarter's technical work; mentor two developers until they own features.
The steps up from lead
Lead software developer to software architect
What changes: you design the structure that several teams build on: how systems are split, how they talk, where data lives, and how they stay secure and affordable. Your output is designs, decisions and guidance, and you check that they work in practice.
The gap: architecture across systems, service boundariesAsked in 6% of software developer ads (as of 5 Nov 2026).Know when splitting a system pays off, and what it costs: network failures, data consistency, tracing. and integration, cloud architecture on AWSAsked in 5% of software developer ads (as of 5 Nov 2026).Core services (compute, storage, databases, IAM for access rights) and what they cost. depends on the provider or AzureAsked in 8% of software developer ads (as of 5 Nov 2026).Microsoft's cloud: app services, functions, storage and identity; common in larger European firms. depends on the provider, securityAsked in 5% of software developer ads (as of 5 Nov 2026).The common attacks on web software and how code prevents them; the OWASP Top 10 is the usual list. and data protection, cost estimates, and presenting options to people who are not engineers.
On the CV and in interviews: designs that were adopted, how many teams or systems they covered, and the result. Expect a whiteboard design with trade-offs, often in front of managers.
Plan (9 to 12 months): write two architecture documents for real problems at work and get them reviewed; take one cloud architect certificate; lead one cross-team design review; present one design to a mixed audience.
Lead software developer to engineering manager
What changes: people come first. You hire, coach, give feedback, plan and remove obstacles, and you answer for what the team delivers and how it works together. Your own code becomes a small part of the week.
The gap: one-to-ones, feedback, hiring interviews, handling poor performance, planning and reporting, and protecting the team's focus.
On the CV and in interviews: the team's size, what it delivered, the people you hired and helped grow, and changes you made to how the team works. Expect questions about conflict and feedback; bring real examples and what happened after.
Plan (6 to 12 months): take on one or two direct reports if your company allows it; run the hiring for one role; find a manager to mentor you; read one book on management and try its ideas with your team.
Engineering manager to head of engineering
What changes: you lead several teams, often through other managers. You own the engineering strategy, the budget, the hiring plan and how engineering works with product and the rest of the business.
The gap: organisation design, budgets, growing managers, setting goals across teams, delivery and quality measures, and representing engineering to the leadership team.
On the CV and in interviews: the size of the organisation, what it delivered, how you grew it and the leaders you developed. Expect questions on strategy, a hard trade-off and a team you turned around.
Plan (12 months or more): manage a second team or a manager; own the yearly plan and budget for your area; set and report two engineering measures, such as release frequency and incident rate; build peer relationships with product and finance.
Your CV for the next step
A step up shows on a CV as proof of the bigger responsibility, in the words that level's ads use, under a real job. Three rules:
- Add, never rename. Keep your past job titles. Add lines that show the new work.
- Use the next level's words. A senior role wants "owned", "designed", "mentored"; a lead role wants "led", "set standards"; a manager role wants "hired", "grew", "delivered".
- One result per line. Speed, errors, cost, users or time saved.
| Skill | Weak line | Strong line, with proof |
|---|---|---|
| API designAsked in 6% of software developer ads (as of 5 Nov 2026).Design an HTTP API with clear resources, status codes, versioning, paging and helpful errors. | Worked on APIs. | Designed the orders API used by 3 partner apps; integration time for a new partner fell from 6 weeks to 2. |
| CI/CDAsked in 29% of software developer ads (as of 5 Nov 2026).Every change is built and tested automatically; a green pipeline can ship, a red one stops the release. | Improved the pipeline. | Led the move to automated releases; deployments went from monthly to daily with fewer incidents. |
| ArchitectureAsked in 6% of software developer ads (as of 5 Nov 2026).Know when splitting a system pays off, and what it costs: network failures, data consistency, tracing. | Architecture experience. | Split billing out of the monolith along a clear boundary; billing releases no longer wait for the main app. |
| Leadership | Mentored juniors. | Mentored 3 developers; 2 now own services end to end. |
| Management | Managed a team. | Managed 7 engineers; hired 3, and the team's release frequency doubled in a year. |
Key takeaways
- The ladder runs junior, developer, senior, lead, then architect or engineering manager, then head of engineering.
- Developer is about finishing work alone; senior is about owning a system; lead is about a team's technical direction.
- Beyond lead, choose between designing systems (architect) and leading people (manager).
- Each step changes what you are measured on; prepare proof of that, not just new knowledge.
- Add proof to your CV in the next level's words, one result per line.
Frequently asked questions
- What comes after senior software developer?
- Lead software developer, and from there software architect or engineering manager, then head of engineering.
- How long does it take to become a senior developer?
- Often a few years of owning features end to end. What counts is the responsibility you can show, not the years alone.
- Do I have to become a manager to move up?
- No. Lead and architect roles are steps up without managing people; engineering manager and head of engineering are the steps that do.
- What should the CV show for a lead role?
- The team you led technically, what it delivered, the standards you set and the people you helped grow, each with a result.