Understand the job before you chase it.
What people actually do, what employers expect, the difficult parts, how people get in and where the role can lead.
Full role guides
15 with photos, a day in the role and projects
IT Support
The people who move on fastest aren't the ones who close the most tickets. They're the ones who notice the same ticket keeps coming back and ask why.
Read the guide →
Security Architect
The architects who get listened to are the ones who can say yes with conditions. A reviewer who only ever says no gets routed around.
Read the guide →
SOC Analyst
The analysts who progress are rarely the fastest closers. They're the ones who tune the rule that keeps waking everyone up at 3am.
Read the guide →
Cloud Engineer
The job title covers at least six different jobs. Two cloud engineer adverts can share almost nothing beyond the provider's name, so read the duties, not the title.
Read the guide →
Infrastructure Engineer
It gets declared dead every hiring cycle and it keeps hiring. What changed is that the role now has to understand cloud as well, not instead.
Read the guide →
Network Engineer
The first five years have a clean shape: CCNA, support the network, learn the kit. Year six is harder, because the next step means choosing between security, automation, cloud networking or design.
Read the guide →
GRC Analyst
It's hiring hard and has the worst hiring asymmetry in security. Employers want people who understand the technology underneath, and most applicants arrive with a framework cert and no technical background.
Read the guide →
DevOps Engineer
The title survives because nobody agrees what it means. In one company it's a build engineer, in another a cloud engineer who writes YAML, in a third it's the person who gets paged. Ask which before you accept.
Read the guide →
Platform Engineer
It's either DevOps with a clearer boundary or DevOps with a new sticker. The test is whether the team has a defined product, a promise to its users and the power to say no.
Read the guide →
Cloud Architect
It completes the infrastructure to cloud engineer to cloud architect path, but the jump into it is mostly about writing and persuasion. The strongest engineers don't always make it if they can't explain a tradeoff to a finance director.
Read the guide →
Sysadmin
The admins who move up are the ones who write the runbook after the incident. The ones who don't, fix the same thing every month.
Read the guide →
Pentester
Juniors think the job is finding things. Seniors know it's the report. A critical finding nobody understands doesn't get fixed.
Read the guide →
Data Analyst
The analysts people trust most are the ones who say 'the data can't tell you that' out loud, instead of producing a chart anyway.
Read the guide →
Software Engineer
The engineers who progress aren't the fastest typists. They're the ones who make a change smaller, safer and easier for the next person to understand.
Read the guide →
Applied AI Engineer
The strongest AI engineers spend more time on evaluation than on prompts. A demo that impresses once proves very little.
Read the guide →
Foundations & enterprise IT
10 rolesDesktop Support
Imaging, app packaging, hardware swaps, deskside escalations, hands-on Windows/macOS estate work.
Responsibilities, trade-offs and next moves →Endpoint Administrator
Intune policies, Autopilot, compliance baselines, app delivery, the modern desktop estate at scale.
Responsibilities, trade-offs and next moves →Enterprise Architect
Stakeholder meetings, capability maps, multi-year roadmaps, vendor reviews.
Responsibilities, trade-offs and next moves →Helpdesk
Phones, tickets, password resets, the literal front door of IT.
Responsibilities, trade-offs and next moves →Infrastructure Engineer
Hypervisors, storage, network fabric, the layer above the OS and below the app.
Responsibilities, trade-offs and next moves →IT Operations Engineer
Run-book ownership. Endpoint, identity, light cloud, light networking, occasional firefighting.
Responsibilities, trade-offs and next moves →IT Support
Ticket queue, password resets, hardware swaps, fast feedback, low autonomy.
Responsibilities, trade-offs and next moves →Junior Sysadmin
Patching, basic AD, file shares, supervised changes, the apprentice rung of sysadmin.
Responsibilities, trade-offs and next moves →Sysadmin
Own the boxes. Patching, backups, AD/Linux, the occasional 2am alert.
Responsibilities, trade-offs and next moves →Virtualization Engineer
vCenter, NSX, storage fabric, the boring layer that keeps the lights on.
Responsibilities, trade-offs and next moves →
Cybersecurity
30 rolesAdversary Simulation
Long campaigns, C2 OPSEC, custom tooling. Adversary emulation as a craft, not a script-kiddie sport.
Responsibilities, trade-offs and next moves →AppSec Engineer
Threat-modelling features, reviewing code, hunting bugs in web/mobile, building paved roads with devs.
Responsibilities, trade-offs and next moves →CISO
Board decks, budget defence, incident accountability, regulator calls. Most weeks are politics and translation, not engineering.
Responsibilities, trade-offs and next moves →Cloud Security Engineer
Guardrails, CSPM tuning, IaC scanning, incidents in 200 AWS accounts.
Responsibilities, trade-offs and next moves →Compliance Specialist
Evidence collection, audit prep, ISO/SOC2/PCI cycles, long workstreams with hard deadlines.
Responsibilities, trade-offs and next moves →Defender/Sentinel Engineer
Sentinel content, Defender XDR tuning, KQL all day, the modern Microsoft detection engineer.
Responsibilities, trade-offs and next moves →Detection Engineer
Write Sigma/Splunk rules, tune noise, hunt the gap your SIEM missed.
Responsibilities, trade-offs and next moves →DFIR Analyst
On-call rotations, evidence preservation, timeline reconstruction, security at its most clinical.
Responsibilities, trade-offs and next moves →Exploit Developer
Weeks debugging a single primitive, bugs, mitigations, ROP, kernel internals.
Responsibilities, trade-offs and next moves →Forensics Specialist
Disk and memory imaging, chain of custody, court-ready reports, the slowest, most evidentiary lane.
Responsibilities, trade-offs and next moves →GRC Analyst
Frameworks, audits, control evidence, translating tech into board language.
Responsibilities, trade-offs and next moves →IAM Engineer
Identity lifecycle, SSO, federation, conditional access, the unsung gate.
Responsibilities, trade-offs and next moves →Incident Responder
Breaches, forensics, war rooms, the call at 3am that defines the quarter.
Responsibilities, trade-offs and next moves →Junior SOC Analyst
Tier-1 alert triage. Close the false positives, escalate the rest, learn the playbooks.
Responsibilities, trade-offs and next moves →Malware Analyst
Reverse-engineering binaries, unpacking, writing YARA, deep solo focus.
Responsibilities, trade-offs and next moves →Network Security Engineer
Firewalls, segmentation, SSE/SASE, east-west controls, perimeter engineering as a craft.
Responsibilities, trade-offs and next moves →Pentester
Scope, recon, exploit, write the report nobody reads. Repeat next engagement.
Responsibilities, trade-offs and next moves →PKI Engineer
Certificate authorities, HSMs, key rotation, signing infrastructure.
Responsibilities, trade-offs and next moves →Platform Security Engineer
Guardrails, paved roads, golden images, policy-as-code, security inside the platform team.
Responsibilities, trade-offs and next moves →Red Teamer
Long campaigns, adversary emulation, AD chains, evasion against modern EDR.
Responsibilities, trade-offs and next moves →Reverse Engineer
Static + dynamic analysis of unknown binaries. IDA/Ghidra, sandboxes, hours of patience.
Responsibilities, trade-offs and next moves →Risk Analyst
Risk registers, control mapping, vendor reviews. Translating security into business probabilities.
Responsibilities, trade-offs and next moves →Security Architect
Reference architectures, trust boundaries, design review, security as a systems-design discipline.
Responsibilities, trade-offs and next moves →Security Automation Engineer
SOAR playbooks, glue scripts, ticket enrichment, replacing your own toil.
Responsibilities, trade-offs and next moves →Security Manager
1:1s, vendor calls, board updates, budget, security as a people-and-strategy job.
Responsibilities, trade-offs and next moves →Security Operations Analyst
Triage in Sentinel, run playbooks, investigate XDR incidents. Tier-2 SOC for Microsoft estates.
Responsibilities, trade-offs and next moves →SOC Analyst
Triaging alerts on rotation, writing tickets, chasing false positives.
Responsibilities, trade-offs and next moves →SOC Lead
Shift rotations, metrics, vendor management, mentoring tier-1.
Responsibilities, trade-offs and next moves →Threat Hunter
Hypothesis-driven hunts across telemetry, proactive, low-alert, high-judgment.
Responsibilities, trade-offs and next moves →Vulnerability Researcher
Bug hunting at scale, fuzzing, CVE drops, conference talks if you're lucky.
Responsibilities, trade-offs and next moves →
Cloud
6 rolesAzure Administrator
Subscriptions, RBAC, networking, VMs, governance, the day-to-day operator of an Azure estate.
Responsibilities, trade-offs and next moves →Cloud Architect
Whiteboards, design reviews, cost models, less keyboard time than you think.
Responsibilities, trade-offs and next moves →Cloud Engineer
Provision, glue services, fight IAM, own one cloud account end-to-end.
Responsibilities, trade-offs and next moves →Junior Cloud Engineer
Ticketed cloud work. Provisioning, IAM cleanups, supervised changes inside someone else's design.
Responsibilities, trade-offs and next moves →M365 Administrator
Tenants, Exchange Online, Teams, SharePoint, Entra, the productivity plane of Microsoft shops.
Responsibilities, trade-offs and next moves →Solutions Architect
Customer calls, reference architectures, PoCs, occasional code review.
Responsibilities, trade-offs and next moves →
Platform / DevOps
7 rolesDevOps Engineer
Pipelines, infra glue, on-call, the team everyone blames when CI is slow.
Responsibilities, trade-offs and next moves →DevSecOps Engineer
Bake security into the pipeline. SCA, SAST, IaC scanning, dev advocacy.
Responsibilities, trade-offs and next moves →Kubernetes Engineer
Cluster ops, operators, networking quirks, helm charts that nobody reads.
Responsibilities, trade-offs and next moves →Observability Engineer
Metrics, traces, logs at scale. Prometheus, OTel, the cost spreadsheet.
Responsibilities, trade-offs and next moves →Platform Engineer
Build the paved road. Internal platforms, golden paths, developer experience.
Responsibilities, trade-offs and next moves →Software Engineer
Reading existing code, making small safe changes, code review, and the occasional production bug.
Responsibilities, trade-offs and next moves →SRE
SLOs, error budgets, postmortems, building the thing that pages you less.
Responsibilities, trade-offs and next moves →
Networking
4 rolesJunior Network Engineer
NOC-adjacent. Tickets, change windows, supervised configs, 2am pages occasionally.
Responsibilities, trade-offs and next moves →Network Automation Engineer
Ansible + Python against network gear, CI for configs, less CLI than you'd think.
Responsibilities, trade-offs and next moves →Network Engineer
Packets, VLANs, BGP at 3am. Methodical, deep, occasionally on-site.
Responsibilities, trade-offs and next moves →NOC Technician
Monitoring screens, ticket triage, change-window execution, the network equivalent of Tier-1 SOC.
Responsibilities, trade-offs and next moves →
Data
2 rolesApplied AI Engineer
Building features on AI models, then spending more time testing whether they work than building them.
Responsibilities, trade-offs and next moves →Data Analyst
SQL, reconciling numbers that don't match, then explaining what they mean to people who wanted a different answer.
Responsibilities, trade-offs and next moves →