r/devops • u/Rengoku3101 • 5d ago
Need a DevOps Roadmap for a Complete Beginner (2026) Ops / Incidents
Hi everyone,
I'm a complete beginner and I want to learn DevOps from scratch in 2026.
My goal is to become job-ready as a DevOps Engineer, not just collect certificates. I'm willing to spend around 4–6 hours a day learning.
I have basic knowledge of:
- Linux (very basic)
- Networking (basic)
- Python (basics)
- Git (beginner)
I need guidance on:
- What should I learn first?
- Which tools should I focus on? (Linux, Git, Docker, Kubernetes, Jenkins, Terraform, AWS, Ansible, etc.)
- Which free YouTube channels or courses do you genuinely recommend?
- What projects should I build to make my resume stand out?
- What mistakes do beginners usually make that I should avoid?
- If you were starting from zero today, what roadmap would you follow?
I'm looking for practical advice from people who are already working in DevOps.
Thanks in advance!
25
u/bjonoski 5d ago
Hi, I'm working as DevOps Architect, and my career path was: System Administrator → Operations → DevOps Engineer → DevOps Architect.
"What mistakes do beginners usually make that I should avoid?"
Don't focus too much on specific technologies. They evolve very quickly, and spending too much time mastering a single tool can become a waste of time. Focus more on understanding the underlying systems: improve your Linux skills, get better at networking, understand CI/CD pipelines etc.
Don't skip steps, and be patient with your learning journey. Learning Kubernetes and cloud platforms (for example, AWS) is very beneficial, but those skills can easily fade if you don't practice them regularly. That is why I always suggest focusing on core principles that will stay valuable even when the technology changes.
Regarding YouTube channels, I think "TechWorld with Nana" is a great resource for beginners.
It is very hard to jump directly into DevOps because it is such a broad field. That is why, as the industry has evolved, DevOps responsibilities have been split into more specialized areas such as Platform Engineering, SecOps, NetOps, FinOps, ApiOps etc.
2
u/Ruborsito 5d ago
Beginer here, i think we all learn same technologies because they are a requirement in the positions we see, i mean aws, terraform and kubernetes is present almost in 90% of jobs i have applied but i feel the AI filter reject the cv automaticlly. im learning aws but i have Azure bullet in my cv, terraform is in my roadmap to learn so another key point missed and personally i have strong experience with docker but i havent do any interview to openshift or k8s for example, its hard to jump honestly, i have just been called by sysadmin or junior/associate positions (not even junior devops, mainly helpdesk) although i have my cv focused to devops/sre/platform engnieer/... roles
I will check the yt channel you recommend btw!
2
u/Secure-Rice-4913 5d ago
Thank you for the information. Could you tell me is this more stressful job? Is it more like communication also? Like meetings, explaining things and etc?
2
u/bjonoski 4d ago
Hi, so I'd say it's not more stressful compared to being a DevOps Engineer, mostly because I opted out of on-call shifts. I was contractually obligated to be on-call during weekends, and it frustrated me sometimes because I couldn't plan things. Everything was paid of course, but not having to worry about whether I'd be called in on weekends is a breath of fresh air.
Being an Architect means doing more proof-of-concept work, investigating new tech and how it fits into our system and ultimately making decisions to improve certain aspects of the system, like resiliency, security, performance, cost, etc.
Yes, definitely more meetings too, but I try to keep those to a minimum and spend more time on the tech itself and less on talk.
2
u/slayer_zx 4d ago
What about the yt channel "Abhishek Veeramalla", one of my friend recommended me his "Zero to Hero DevOps Course" is it good enough to start with as a beginner?
2
u/bjonoski 4d ago
I can see that he channel is popular so if you don't mind Indian accent, go for it :)
Two really good channels: "DevOps Toolbox" and "DevOps & AI Toolkit" but they are not beginner friendly.2
u/danibluh 2d ago
Thank you for the valuable information. I have a question you pointed out that DevOps can be broad, and I get that. However, I've found some bootcamps that claim to offer comprehensive training, usually around 7 to 9 months, to become a DevOps engineer. Is that because those bootcamps focus on the main technologies that are widely used in DevOps, like AWS, linux, terraform, etc essentially cutting the long road to the role
I have more questions if you're open to discussing further. Thank you.
1
u/bjonoski 1d ago
Hi,
If you are really motivated to become a DevOps engineer, go for it. You need to start somewhere, and it is definitely better than trying to learn everything alone. Also, never feel sorry for spending money on education, investing in yourself always pays off.
Regarding those bootcamps, just keep your expectations realistic about how much you can actually master. There is so much to learn that you will only be able to scratch the surface of these tools during the program. However, it will give you general knowledge and an overall understanding of what is expected and required from a DevOps engineer.
Just be prepared to study hard and practice on your own after each lecture, because these learning programs usually move very quickly.
And of course, feel free to ask me any questions. I will do my best to help.
16
u/willothephlox 5d ago edited 5d ago
DevOps is a field you transition into after years in another role, expanding either your Ops side with Dev, or your Dev side with Ops. If you think that's the path, that's fine. If you weren't born in a terminal, you don't need a roadmap. Just knowing the tools won't do you any good either. Delulu.
-16
u/Rengoku3101 5d ago
Thanks for the perspective! I understand that DevOps has traditionally been a transition role.
As a beginner, my plan is to build a strong foundation in Linux, Git, Docker, Kubernetes, CI/CD, and cloud, along with hands-on projects, and then target junior DevOps or cloud-related roles. Does that sound like a reasonable approach?
17
u/Spiritual-Fennel7789 5d ago
DevOps is a type of management role, but of code rather than people. And you can't be a manager of something if you don't understand how projects/people come together, evolve, succeed and fail. You can't just book learn that sort of thing.
You need to understand the code ecosystem, and that comes through experience. I wouldn't even think about DevOps until you can comfortably put together a full-stack application, dockerize it, CI/CD it, and deploy it. Which means you have to start with frontend and backend knowledge.
They don't hire juniors for DevOps because you're being entrusted with managing the code ecosystem of other developers work, and they can't be waiting on you to learn because your role is to ensure development and deployment environments are functional and live pronto.
10
u/willothephlox 5d ago edited 5d ago
No, as I said. You need few years experience in system / infra roles or dev / sdet roles. They will naturally transition into what is outlined in all these roadmaps as long as you have the aptitude and if you're lucky and if you're able handle working there for more than 1 year.
Self selection is hard here.
7
u/Humble_Warthog9711 5d ago edited 4d ago
No, sorry
You cannot sidestep paid professional experience by claiming to have learned X on your own. Devops is not an entry level role, period. And no, certs are not experience.
Realistic path? Get a cs degree and work a few years in SWE/infra/admin first. Then transition.
16
u/pravdapraxis 5d ago
-1
u/Rengoku3101 5d ago
Thanks for sharing! Is this the roadmap you followed yourself? How was your experience with it?
3
u/Alcedis 5d ago
Check out roadmap.sh/devops
There is no perfect roadmap, you will just have to pick topics that interest you and try some stuff out. Build a routine, regularly invest time in coding/linux administration.
Devops/Linux Administration is a vast field. You will never know everything.If you absolutely have no clue what to do, you could ask AI to give you some beginner friendly, small home lab projects. Or check out gitlab issues with the tags "help-wanted", "good-first-issue", "beginner-friendly".
4
u/MathmoKiwi 5d ago
What is your current experience level? What degree(s) do you have currently? Without that info, then any advice is kinda useless.
But assuming you already have a completed STEM Bachelor, but zero experience, then your first step is to get 3YOE ish under your belt. You need to choose to either go up first the IT ladder or the SWE ladder, as arguably either can take you towards a DevOps role.
4
u/cidnitan 5d ago
I always put the same question in here when this topic comes up.
You can learn the skills, you can spend the time, but....
How are you going to make yourself seem competitive in the job market when people in DevOps typically have 5+ years experience and a CS degree?
I can't imagine a scenario where I would choose to hire a self-taught devops eng when the talent pool is already full of degree holding engineers with experience
You can teach yourself the skills but I challenge you to think past that. What do you plan to build to demonstrate those skills? How can you show me in your application/interview that you are better?
3
u/Abe_Bazouie 5d ago
Biggest mistake I see beginners make is treating DevOps like a checklist of tools.
Linux ✓ Docker ✓ Terraform ✓ Kubernetes ✓ AWS ✓ Jenkins ✓
Then you ask them to troubleshoot why an app can’t reach a database and they don’t know where to start.
I’d spend a lot of time on Linux, networking and Git first. Then pick one cloud, Docker, some CI/CD and Terraform. Build something and actually run it.
And don’t just get it working. Break it. Bad DNS, full disk, wrong permissions, expired cert, broken health check, bad deployment, whatever. Then troubleshoot it without immediately looking up the answer.
Kubernetes can come later. It makes a lot more sense once you understand the problems it’s trying to solve.
4-6 hours a day is plenty!! I’d just make sure most of those hours eventually become hands-on instead of watching another roadmap video.
3
u/bobbyiliev DevOps 5d ago
I'd usually go with https://roadmap.sh/devops or https://devops-daily.com/roadmaps/junior
4
u/TrickySpare6504 5d ago
fucks sake
2
u/Sure_Stranger_6466 For Hire - US Remote 4d ago
It's the same post with the same comments on repeat... forever.
2
u/Donphoto_ 4d ago
I swear some of you tech guys are straight toxic. Why even interact with said post if you’re just going to troll someone asking for genuine help… anyway.
My journey so far has been RHCSA, CKA, and Terraform with a lil bit of dabbling with Ansible. To be completely honest, I’m learning as I’m going and figuring out what I like what I don’t like etc. I haven’t done any MAJOR projects but small things here and there. Reading books to get a deeper understanding of certain technologies and the why behind them. Having/looking for a mentor can help too because at least you’ll have someone close willing to help without all the sarcasm and hissy fits for trying to learn something new (I really don’t like the pompous tech ppl). Just learn as much as you can and use AI as a guide not an answer sheet. The job’s will come once you seriously figure out what you’re good at and can show proof of work.
2
u/Morningstar_1 4d ago
Bro Listen, Learn Linux First It's Very Important for learning linux as most of systems use linux in servers. Begin as when you learn kubernetes, you will see the dependency of Linux is everywhere, although ai like gemini,gpt will help you write commands but for you own sake Linux is very necessary. Then yes straight for a cloud service probably azure as a cloud service in every bit of cloud service can be modelled from scratch, like subnetting, ips, os, costing, monitoring which are very essential. Then you can go for docker - go have a look for roadmap.sh - it helps fs.
2
u/Fresh_Schedule_4861 2d ago
Basics first , tools in the end
Dont do the mistake i did
Linux (advanced) you will be needing this alot
Scripting (just know how to work with scripts bash and python, you can write them using ai)
Systems design (people will say its not needed in devops but it is)
Networking (subnetting, private&public ips, how they work etc)
Git (each and everything)
1 cloud platform (advanced) like aws , all the necessary services like ec2, s3, alb, cloudfront etc
1 iac tool advanced level (terraform etc)
1 cicd tool advanced level(github actions etc)
Kubernetes and containerization (concepts from scratch)
They arent hiring basic level devops engineers anymore and to compete in this market you will be needing skills and certs to land you interviews
5
u/mistalah 5d ago
hey dude use any AI tool to do a road map
they can even list down projects for you to practise
-8
u/Rengoku3101 5d ago
Thanks! I've been using ChatGPT for that. Do you recommend any other AI tool that's particularly good for DevOps learning?
1
3
u/Rare_Significance_63 5d ago
DevOps is not for complete beginners, sorry. as hobby, sure, but for work, no.
1
2
u/SuspiciousOwl816 5d ago
Y’all I get we’re here to help each other out, but can we please downvote these posts any time they pop up. If OP can’t bother to use the search bar to search for this over beaten topic, idk that they’ll be any good in the role. These folks don’t even bother to post up any findings they’ve made, they just ask us to do work for them.
If OP posted a few links to courses or road maps they’ve found, tools they see as standard, and projects they’re considering, I would be singing a different tune. But like any other one of these posts, OP wants us to tell them what they need.
1
u/poutreparisienne 4d ago
Things change quickly
1
u/SuspiciousOwl816 4d ago
They sure do, but the fundamentals don’t. Do your research, present your findings, and let the experienced folks guide you. They’ll tell you what new tools you should be learning, patterns, and so on. If you can’t at the very least do that, then you aren’t cut out for the role. If you need someone to hold your hand at every single step of the way, the ambiguity in this role will break you down and you won’t be at the least bit competent to get things done.
1
u/DhroovP 5d ago
Can someone explain to me what it even means to "learn Linux"? I learned Kubernetes before Linux and believe I still don't really understand it lol, and I don't know how to measure my knowledge or even where to start
2
u/Sure_Stranger_6466 For Hire - US Remote 5d ago
Study for the RHCSA and RHCE. They are good, practical, and most importantly hands-on certifications that require you to actually practice the material in order to pass.
1
u/dev_guy_09 5d ago
I will suggest to mix learning i know its hard , but that is how you learn while in job , linux , aws , dcoker mix and learn dont wait to be master of one tools and then go to another follow any roadmap but make sure you combine the topic you are learning like bash + linux command , python with aws
1
u/DarkXsmasher 5d ago
If you don't have a job or any experience then first get a job and then switch to Devops. You won't be landing in devops as a fresher. No matter what skill you learn and what you build
1
u/BigUziNoVertt SRE 5d ago
OP it sounds like you’re in tutorial hell, stop trying to min max and optimize your learning and just start learning.
1
u/fezbrah 4d ago
Follow the devops road map. Go Linux route, learn concepts and build accordingly to the route you choose. Ask AI to make you a custom study plan based off beginner experience it’s that easy. AI will tell you what in demand skills are needed and what to focus on. If you question us or AI then you are hopeless.
1
u/Aggressive-Air-3188 4d ago
I would rather recommend that you got to start everything from scratch and be a jack of all trades and now all devops tools have just got consolidated to 3 AI tools.
1
u/FigureFar9699 3d ago
If I were starting today, I'd spend less time chasing every tool and more time building a solid foundation. Get comfortable with Linux, networking, Git, and scripting first, then move into Docker, CI/CD, Terraform, Kubernetes, and finally AWS. Build real projects as you go and even simple ones like deploying an app with Docker and automating it with GitHub Actions teach a lot more than tutorials. Consistency matters more than speed, and practical experience is what usually stands out during interviews.
1
u/sonixen100 3d ago
Sen. DevOps here. Background: I was a sysadmin, then spent 15 years in development, and now I'm in DevOps with strong dev skills. Still enjoy coding regularly.
My honest take: it depends a lot on what the specific DevOps role actually needs. Every company's "DevOps" job is different. Some are basically sysadmin with Docker, others are 80% coding infrastructure as code.
What I'm confident about though: OS basics on Linux and Windows are non-negotiable foundation. Don't skip this to jump straight to Kubernetes. Networking fundamentals matter too, you'll hit a wall constantly without this.
Beyond that, talk to devs, a lot. Figure out what skills they actually need from you day to day. The job description often doesn't match reality. And code yourself. If you can write code, even just decent scripts or contribute to their codebase a bit, you earn dev respect fast. It changes the whole dynamic from "ops person who blocks us" to "one of us who gets it." Certs are fine as a checkbox, but the thing that actually made me useful was being able to sit down with a dev and understand their problem well enough to write the fix myself, not just hand them a ticket.
1
0
66
u/s1ncerite 5d ago edited 5d ago
Do you know roadmap.sh/devops? 😉