To learn DevOps, start with Linux and the command line, then Git, one scripting language (Bash and Python), networking basics, CI/CD pipelines, Docker containers, one cloud provider, infrastructure as code and monitoring. Build small projects at each stage so you can show working pipelines, not just certificates.
Quick answer: Linux → Git → scripting → networking → CI/CD → Docker → cloud → Terraform → Kubernetes → monitoring. Expect several months to a year of steady part-time study before you are job-ready, depending on your background.
What DevOps actually is
DevOps is a set of practices that bring development and operations together so software can be built, tested, released and run reliably and often. Job titles vary: DevOps engineer, site reliability engineer (SRE), platform engineer, cloud engineer or build and release engineer. Most entry points come from system administration, QA automation or software development. If you are coming from testing, see how to become a QA tester.
The DevOps roadmap at a glance
| Stage | What to learn | Project to prove it |
|---|---|---|
| 1. Linux | Files, permissions, processes, package managers, SSH | Set up and secure a Linux server |
| 2. Git | Branches, merges, pull requests | Host all your projects on a Git platform |
| 3. Scripting | Bash and Python basics | Automate a backup or log cleanup |
| 4. Networking | DNS, HTTP, ports, load balancers, TLS | Serve a site with a domain and HTTPS |
| 5. CI/CD | Pipelines, automated tests, artefacts | Pipeline that tests and deploys an app |
| 6. Containers | Docker images, Compose | Containerise a multi-service app |
| 7. Cloud | Compute, storage, IAM, networking on one provider | Deploy your app to the cloud |
| 8. Infrastructure as code | Terraform or similar | Recreate your environment from code |
| 9. Orchestration | Kubernetes basics | Deploy to a small cluster |
| 10. Observability | Logs, metrics, alerts | Dashboard and alert for your app |
Stage 1 to 3: foundations
Linux is the backbone of most servers, so be comfortable in a terminal before anything else. Learn Git early and use it for everything; our Git and GitHub for beginners guide covers the basics. For scripting, Bash handles quick automation and Python handles anything more complex. Python is also widely used in tooling; see how long it takes to learn Python.
Stage 4 to 6: delivery and containers
Understand how requests travel: DNS, HTTP, ports and TLS certificates. Then build a CI/CD pipeline that runs tests on every commit and deploys automatically. Containers come next: write a Dockerfile, keep images small, and use Compose to run several services together.
Stage 7 to 10: cloud, code and operations
Choose one cloud provider and go deep before learning others. Learn identity and access management early, because security mistakes are the most expensive. Then describe your infrastructure with code so it can be rebuilt reliably. Kubernetes is powerful but complex; learn it after Docker and cloud basics, not before. Finally, add logs, metrics and alerts so you know when something breaks. For the security side of cloud work, read how to start a cloud security career.
How long does it take?
- Coming from IT support or sysadmin: you already have Linux and networking; focus on CI/CD, containers and IaC
- Coming from development: you know Git and code; focus on Linux, networking and cloud
- Complete beginner: plan for a longer path and consider starting in IT support or QA first
Timelines depend on weekly hours and prior experience, so treat any promise of a few weeks with caution.
Self-study, course or bootcamp?
Self-study works if you are disciplined and build projects. Structured courses and bootcamps add mentoring, deadlines and portfolio reviews. Compare costs and formats in our coding bootcamp cost guide for Canada before you commit.
Portfolio checklist
- A public repository with a working CI/CD pipeline
- A containerised app with clear README instructions
- Infrastructure defined as code that anyone can redeploy
- A monitoring dashboard screenshot and alert rules
- A short write-up of a problem you debugged
FAQ
Do I need to know how to code for DevOps?
You need scripting and the ability to read application code. You do not need to be a senior software developer.
Should I learn Kubernetes first?
No. Learn Linux, Docker and one cloud provider first. Kubernetes makes much more sense once those are familiar.
Which cloud should I start with?
Pick the one most common in job postings near you. The concepts transfer between providers.
Are certifications required?
Not strictly, but a cloud certification can help get past filters. Projects still matter more in interviews.
Conclusion
DevOps is a broad field, but the path is clear when you take it in order. Master the foundations, automate everything you build, and document your projects. That combination is what hiring managers look for.
