What comes after senior full-stack developer?

Lead full-stack developer, then solutions architect or engineering manager, and later head of engineering.

Is full-stack a good path to management?

Often, yes: seeing the whole product helps you plan work across a team. You still need to learn hiring, feedback and planning.

Do I need to manage people to move up?

No. Solutions architect is a step up without managing people.

Do certificates help at senior level?

A cloud architect certificate helps for solutions architect roles, especially at consultancies. Features and systems you shipped count for more.

What should the CV show for a head of engineering role?

The teams you built, what they delivered, the budget you managed and company results you made possible, each with a number.

Full-stack developer career path: from junior to lead, engineering manager and head of engineering

Each step up the full-stack ladder, from your first job across both halves of an app to solutions architect, engineering manager or head of engineering: 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 teamPublished 27 Oct 2026 · Updated 27 Oct 2026

Contents

The ladder at a glance
The steps up to senior
The steps up from senior
Your CV for the next step
Key takeaways
Frequently asked questions
More on the full-stack developer role

The ladder at a glance

Step	What you are measured on next	Typical time
Junior full-stack developer to full-stack developer	Features you ship across both halves on your own	1 to 2 years
Full-stack developer to senior full-stack developer	A product area: its design, data and releases	2 to 3 years
Senior to lead full-stack developer	A team's work, standards and delivery	1 to 3 years
Lead to solutions architect	How systems, partners and data fit together	2 or more years
Lead to engineering manager	People, hiring and the delivery of one or more teams	1 to 3 years
Engineering manager to head of engineering	The whole engineering organisation and its budget	2 or more years

The steps up to senior

Junior full-stack developer to full-stack developer

What changes: you take a feature through every layer yourself: the screen, the API, the table and the release, instead of finishing one half and handing over the other.

The gap: your weaker side brought up to shipping level, SQL and safe schema changes, sign-in and access checks, TypeScript types shared between the halves, and tests on both sides.

On the CV and in interviews: two or three features you built from screen to database, each with a result. Expect a take-home app and questions on what happens when the API fails.

Plan (6 to 12 months, on the job): pick features that cross your weaker layer; build one small product of your own with sign-in, a database and a deploy; ask for reviews from a specialist on each side.

Full-stack developer to senior full-stack developer

What changes: you own a product area, such as onboarding or billing, from the screens to the data: how it is designed, released and measured. You choose how a feature is split between the layers.

The gap: API design for your own frontend, data modelling, caching across the layers, releases with feature flags, page speed and query speed, and running what you build with Docker and CI/CD on a cloud such as AWS.

On the CV and in interviews: a product area you owned and what improved for users or the business. Expect a system design question about a whole feature and a story about a cross-layer bug.

Plan (6 to 12 months, on the job): own one area's metrics with the product manager; lead a feature that changes all three layers; set up preview deploys; mentor a junior on their weaker side.

The steps up from senior

Senior full-stack developer to lead full-stack developer

What changes: you lead a small team's technical work: plan it with the product manager, decide the stack and standards, review designs, and make sure no part depends on one person.

The gap: planning and estimating, writing decisions down, spreading knowledge across frontend and backend, Communication skills with founders or product leads, and coaching.

On the CV and in interviews: the team, what it shipped, and a decision you made for it, such as the stack or the release process. Expect questions on a deadline you could not meet and on a teammate who struggles.

Plan (9 to 12 months): lead one quarter's planning; write the team's setup and architecture notes; run design reviews for features that cross the layers; coach one developer to senior.

Lead full-stack developer to solutions architect

What changes: you design how whole systems fit together for a product or for customers: the apps, the services, the partners' systems, the data flows and the cloud set-up, and you explain the design to people who are not engineers.

The gap: integration styles (APIs, events, files), cloud architecture on AWS or Azure, security and data protection under GDPR (EU) and similar laws, cost estimates, and writing designs that others build from.

On the CV and in interviews: a system you designed across several parts, its reasons and result. Expect a case: a customer, a deadline, an old system to connect.

Plan (12 months or more): design the next integration with a written comparison of options; take a cloud architect certificate if the ads in your market ask for one; present a design to a customer or leadership; review other teams' designs.

Lead full-stack developer to engineering manager

What changes: you manage people: hiring, one-to-ones, growth, performance and the team's delivery. You code much less, and the team's results become your results.

The gap: Leadership, hiring, honest feedback, planning with Agile methods, balancing features against technical debt, and working with product and design leads as a peer.

On the CV and in interviews: people you hired and grew, what the team delivered, and how you changed how it works. Expect questions on a hard conversation and on a missed goal.

Plan (12 months): run one-to-ones for two developers; join every hiring loop; own the team's delivery for a quarter; ask your manager for monthly feedback on your management.

Engineering manager to head of engineering

What changes: you run engineering for the company or a large part of it: the teams and their shape, the budget, hiring plans, the technical roadmap, and what is built or bought. You report to the founders or the CTO and work with the other heads as a peer.

The gap: managing managers, budgets and vendor contracts, a roadmap tied to company goals, team design as the company grows, and explaining engineering in money and risk.

On the CV and in interviews: the organisation you built, what it delivered, and company results it made possible, such as faster releases or lower costs. Expect a case about your first ninety days.

Plan (12 months or more): own an engineering budget for a year; reshape teams around product areas; write the hiring plan with finance; review build-or-buy choices with the founders.

Your CV for the next step

Moving up as a full-stack developer shows on a CV as more of the product and then more of the team in your hands: from a feature to a product area to an engineering organisation. 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", "end to end", "product area"; a lead role wants "led", "stack", "standards"; a manager or head role wants "hired", "grew", "budget", "roadmap".
One result per line. Features shipped, users or revenue moved, releases sped up, or people grown.

Skill	Weak line	Strong line, with proof
Product area	Worked on onboarding.	Owned onboarding from sign-up screen to welcome emails; activation in the first week up from 31% to 44%.
Stack decision	Chose technologies.	Chose one TypeScript codebase for web and API; 4 developers work on both halves, no handovers.
Leadership	Managed developers.	Hired and managed 6 developers; none left in 2 years, and 3 now lead features end to end.
Organisation	Head of engineering.	Grew engineering from 5 to 22 in 3 product teams; release frequency held at daily throughout.

Key takeaways

The ladder runs junior, full-stack developer, senior, lead, then solutions architect or engineering manager, then head of engineering.
Senior means owning a product area from the screens to the data.
Solutions architect is a step up without managing people; engineering manager and head of engineering lead people.
Each step changes what you are measured on; prepare proof of that, not just one more framework.
Add proof to your CV in the next level's words, one result per line.

Frequently asked questions

What comes after senior full-stack developer?: Lead full-stack developer, then solutions architect or engineering manager, and later head of engineering.
Is full-stack a good path to management?: Often, yes: seeing the whole product helps you plan work across a team. You still need to learn hiring, feedback and planning.
Do I need to manage people to move up?: No. Solutions architect is a step up without managing people.
Do certificates help at senior level?: A cloud architect certificate helps for solutions architect roles, especially at consultancies. Features and systems you shipped count for more.
What should the CV show for a head of engineering role?: The teams you built, what they delivered, the budget you managed and company results you made possible, each with a number.