The pathway
How you actually get there, here
How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.
- 1
Senior Web Developer (IC Track)
Typically 2-4 years at Senior level before moving into management or Principal IC.Skills to master
- Deep technical expertise in a specific web domain, leading complex features, mentoring junior developers, strong technical design skills, and a clear understanding of system-level architecture.
You're ready to move on when
- You're the go-to person for complex technical challenges within your team.
- You're actively mentoring 2-3 junior or mid-level developers.
- You've successfully led the technical design and delivery of several major features.
- You consistently contribute to improving team processes and code quality.
- 2
Lead Web Developer / Team Lead
Roughly 1-3 years in a Lead role.Skills to master
- Managing a small team (3-8 people), project management, cross-functional collaboration, technical roadmap ownership for a specific product area, and early exposure to hiring.
You're ready to move on when
- You're effectively managing a small team, including 1-to-1s and performance feedback.
- You're successfully driving the technical roadmap for a specific product or feature set.
- You're adept at unblocking your team and managing dependencies with other teams.
- You've participated in hiring decisions and onboarding for new team members.
- 3
Technical Architect (Web)
Typically 3-5 years as an Architect.Skills to master
- Designing enterprise-scale web solutions, evaluating new technologies, creating technical roadmaps, influencing senior stakeholders, and providing technical leadership without direct people management.
You're ready to move on when
- You've designed and overseen the implementation of major architectural components.
- You're regularly consulted by multiple teams on complex technical challenges.
- You can articulate and defend complex technical decisions to both technical and non-technical audiences.
- You have a deep understanding of system-level trade-offs and long-term technical implications.