Start with your experience, and explore where it could lead you next in tech.
Explore pathwaysExample route
IT Support
Sysadmin
Cloud EngineerExplore your options
Each route shows where it usually starts, where it leads, and links through to the role guides along the way.
A useful setting for learning diagnosis, user communication and safe service changes.
Explore this route →
Plan your move from technical delivery into security architecture: progression stages, practical projects, certification choices and evidence of readiness.
Explore this route →
Digital forensics and incident response combine evidence handling with decisions during an investigation.
Explore this route →
Cloud security work joins threat reasoning with knowledge of how workloads are deployed and operated.
Explore this route →
A practical engineering route combining cloud deployment with access, reliability and cost decisions.
Explore this route →
Governance and risk work that connects control evidence to accountable decisions.
Explore this route →Helpful guidance
Explore possible next steps, check the responsibilities and choose work you can demonstrate. Your route can change as you learn more.
Compare two pathwaysIf you read nothing else
A route to compare when you enjoy deploying and operating services, including access, recovery and cost decisions.
Compare the actual cloud and security responsibilities rather than assuming one route is easier to enter.
A route to compare when you want to build reusable capabilities for engineering teams and support their adoption.
Check whether the team has users, a funded roadmap and a clear support model.
Compare investigation, engineering and governance work. Different security roles ask for different evidence and working patterns.
Look for the supervision and responsibilities of the particular vacancy, including any direct junior entry programme.
Entry opportunities differ between SOC, engineering, governance and supervised programmes. Compare responsibilities and mentoring rather than treating a cyber shortage headline as a promise of a first job.
Read the full take on Defensive / SOC, in contextConnectivity knowledge can support networking, cloud and security work. The useful comparison is the depth of troubleshooting, change authority and automation in a particular role.
Read the full take on Network Engineer, in contextCompare the work you can demonstrate with the vacancy: implementation, testing, review and maintenance. A course duration does not predict when someone will be hired.
Read the full take on Software Engineering, in contextOffensive work requires authorised scope, reproducible findings and useful reporting. Junior programmes and transitions from other roles can both be relevant; a certificate alone does not establish the whole remit.
Read the full take on Offensive Security, in contextPractitioner guidance · reviewed 24 September 2026. Not statements of worth. Your context will vary.
Reality check. Ratings are directional. Compensation, on-call load, and remote availability vary heavily by employer, geography, and seniority. Treat them as hypotheses to validate, not facts.