← Organisation & Leadership Learning Pathways

Structured progression from where you are to where you want to be.

Structured learning pathways for software engineers - from graduate through to senior and beyond. Each pathway maps the skills, behaviours, reading, and hands-on projects that drive progression.

Graduate Engineer Junior Software Engineer

Graduate Engineer to Junior Software Engineer

9-18 months

Build the professional habits and independent delivery capability that turn a supervised learner into a reliable, self-directed contributor.

🧠 AI as a learning accelerator and code quality mirror View Pathway →

Junior Software Engineer Intermediate Software Engineer

Junior Software Engineer to Intermediate Software Engineer

12-24 months

Move from completing assigned tasks to owning features end-to-end, making sound technical trade-offs, and beginning to raise the quality bar for those around you.

🧠 AI for design exploration and critical evaluation View Pathway →

Intermediate Software Engineer Senior Software Engineer

Intermediate Software Engineer to Senior Software Engineer

18-36 months

Develop the technical leadership, architectural judgment, and influence that make you the person the team relies on for hard decisions and complex problems.

🧠 AI-assisted architecture and critical AI governance View Pathway →

Senior Software Engineer Lead Software Engineer

Senior Software Engineer to Lead Software Engineer

12-24 months

Expand your technical influence beyond your team, shape engineering standards across the organisation, and make growing other engineers your primary leverage.

🧠 AI strategy, governance, and teaching AI critical thinking View Pathway →

Lead Software Engineer Architect

Lead Software Engineer to Architect

24-48 months

Transition from team-level technical ownership to organisation-wide architectural authority by developing systems thinking, technology strategy, and the trusted voice that makes hard decisions stick.

🧠 AI as an architectural force and strategic technology concern View Pathway →

Senior Software Engineer Technical Team Lead

Senior Software Engineer to Technical Team Lead

12-24 months

The first genuine leadership transition - moving from individual technical excellence to creating conditions where a whole team can perform. Your code matters less; your decisions, your culture, and your people development matter more.

🧠 AI as a leadership and decision-support tool View Pathway →

Lead Engineer Technical Team Lead

Lead Engineer to Technical Team Lead

12-24 months

Make the shift from technical authority to people leadership - running a high-performing team while remaining a credible technical voice, and learning that your primary leverage is through others.

🧠 AI in team processes and responsible adoption leadership View Pathway →

Technical Team Lead Engineering Manager

Technical Team Lead to Engineering Manager

12-24 months

Move from hands-on technical leadership to full people management - your job is no longer to be the best engineer in the room but to create the conditions where engineers can do their best work.

🧠 AI tool strategy, team adoption, and ethical leadership View Pathway →

Engineering Manager Head of Engineering

Engineering Manager to Head of Engineering

24-48 months

Move from managing a team to leading an engineering organisation - setting conditions for multiple teams to perform, shaping technical culture and strategy, and operating credibly with executive stakeholders.

🧠 AI strategy, ethics, organisational adoption, and responsible leadership View Pathway →

Architect Head of Engineering

Architect to Head of Engineering

24-48 months

A rare and demanding transition - from deep technical authority to broad organisational leadership. Architects who make it to HoE do so by developing the people leadership, commercial awareness, and organisational design capability to match their existing technical credibility.

🧠 AI governance and organisational AI capability View Pathway →

Head of Engineering VP of Engineering

Head of Engineering to VP of Engineering

24-48 months

The transition to VP is as much about organisational influence and executive presence as it is about engineering excellence. You move from owning the engineering function to co-owning the company's technology strategy at board level.

🧠 AI as a strategic and organisational capability View Pathway →