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
Lead Programmer (L4)
3-5 years as a Lead ProgrammerSkills to master
- Mastering team leadership, project ownership for a major game pillar, influencing cross-functional teams, and making significant technical decisions under pressure.
You're ready to move on when
- Successfully led the technical delivery of 1-2 major game features or systems from concept to launch.
- Consistently received positive feedback on your mentorship and people management skills from your direct reports and peers.
- Demonstrated ability to anticipate and mitigate technical risks for your team's work.
- Proactively contributed to architectural discussions beyond your immediate domain.
- 2
Principal Engineer / Architect (L4 equivalent IC path)
4-6 years as a Principal EngineerSkills to master
- Deep expertise in a specific technical domain (e.g., rendering, networking), solving the hardest technical problems, setting technical standards, and influencing without direct authority. This is often an IC path that can transition to management.
You're ready to move on when
- Recognised as the go-to expert for a critical technical area across the studio.
- Successfully designed and implemented highly complex, performant, and scalable technical solutions.
- Consistently influenced the technical direction of multiple projects through your expertise and proposals.
- Demonstrated ability to mentor and elevate the technical skills of other senior engineers.