Career field guide · Updated September 20, 2026
Turn exam study into skills you can show.
Start with the work you want to do. Choose one path, investigate local job requirements, and build a small project that proves you can diagnose a real problem. A certificate can support that evidence; it cannot promise a job or a salary.
Before choosing an exam: inspect ten jobs
Collect ten current vacancies in your location and desired seniority. Record the tasks, required experience, recurring tools, and whether a certification is required or preferred. Separate requirements you already meet from gaps you can demonstrate in a lab. Choose your next study topic from the repeated gaps, rather than from the longest certification list.
If you are changing careers, include transferable evidence: explaining a difficult issue, following a controlled process, documenting a handover, or handling an incident. Rewrite each example around the problem, your action, and the verifiable outcome.
Five practical starting paths
IT support → systems administration
You enjoy solving user problems and explaining fixes clearly.
- Learn
- Operating systems, accounts, DNS, backups, basic scripting, and ticket writing.
- Choose a study track
- Compare CompTIA A+ objectives with local support vacancies; consider Network+ when networking is a repeated gap.
- Build evidence
- Build two local virtual machines. Create a user, deliberately break name resolution, diagnose it, and restore a file from backup. Publish a ticket with symptoms, evidence, fix, and verification.
- Check your work
- A stranger can reproduce your fix from the ticket without asking you for missing steps.
Networking → network operations
You like tracing why packets reach one destination but fail at another.
- Learn
- Subnetting, switching, routing, VLANs, DNS, DHCP, and reading packet captures.
- Choose a study track
- Compare CCNA and Network+ objectives against the equipment and responsibilities in your target jobs.
- Build evidence
- Draw a two-subnet network, document its address plan, and simulate a routing or VLAN fault in a lab. Record the checks that isolate the fault and the evidence that it is resolved.
- Check your work
- You explain both the forward and return packet path, rather than only presenting a successful ping.
Cloud support → cloud administration
You enjoy automating infrastructure and balancing permissions, reliability, and cost.
- Learn
- Linux or Windows administration, IAM, networks, storage, logging, and infrastructure as code.
- Choose a study track
- Use AWS or Azure fundamentals to learn vocabulary; consider an administrator or architect track when you can build and troubleshoot its core services.
- Build evidence
- Choose one small lab from the resources hub. Draw its trust boundaries, deploy within a budget, test an access failure, inspect the logs, and remove the resources. Save a sanitized runbook.
- Check your work
- Your README explains deployment, permissions, failure recovery, cost checks, and teardown.
IT operations → security operations
You enjoy investigating evidence and deciding which response reduces risk.
- Learn
- Networking, identity, operating-system logs, incident triage, and clear incident reports.
- Choose a study track
- Use Security+ objectives to organize security fundamentals. Match further credentials to the actual work in target vacancies.
- Build evidence
- Run an intentionally vulnerable application locally in an isolated lab. Reproduce one documented issue, explain the root cause, propose a fix, and describe a retest. Never test systems without authorization.
- Check your work
- Your report distinguishes observed evidence from assumptions and explains the limits of your test.
Linux administration → platform engineering
You enjoy command-line troubleshooting and making deployments repeatable.
- Learn
- Linux, Git, containers, networking, Kubernetes, observability, and recovery.
- Choose a study track
- Consider CKA after hands-on Kubernetes practice. A multiple-choice diagnostic alone does not demonstrate readiness for a practical exam.
- Build evidence
- Deploy an application in a disposable cluster. Break its Service selector, inspect endpoints and logs, repair it, then document a second independent failure and recovery.
- Check your work
- You can repeat the diagnosis without a walkthrough and explain why each command narrowed the problem.
A six-week plan you can adjust
- Week 1: choose a target. Review ten jobs, select one role, and take a diagnostic. Record uncertainty as well as wrong answers.
- Week 2: repair foundations. Work through the weakest objective with official documentation. Explain the concept in your own words.
- Week 3: build a small lab. Make it work, save the configuration, and record how you validated it.
- Week 4: troubleshoot. Introduce one controlled fault. Capture observations before changing settings; write a short incident report.
- Week 5: test transfer. Attempt fresh questions and repeat the lab with changed values. Recognition of a memorized answer is not enough.
- Week 6: publish and apply. Sanitize your work, write a clear README, rehearse a five-minute explanation, and apply to roles matching your demonstrated skills.
This is a planning template, not a claim that everyone becomes job-ready in six weeks. Increase the time for unfamiliar foundations and practical exams.
