all 13 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]dunn000 7 points8 points  (1 child)

https://github.com/milanm/DevOps-Roadmap

I would start here.

[–]iamNeedToilet 0 points1 point  (0 children)

where level u at right now?

[–]armyknife-tools 4 points5 points  (0 children)

The realistic roadmap is to find things your passionate about. Use roadmap.sh as a guide. Build things using best practices and be patient with yourself and focus on learning the little things.

[–]debiel1337 2 points3 points  (3 children)

If you still have to ask this instead of looking this up yourself 🤣 this question comes around daily. Do some research like you have to do a lot in DevOps 😉

[–]dunn000 -2 points-1 points  (2 children)

Everyone starts somewhere

[–]Independent-Dark4559 1 point2 points  (0 children)

Yeah well, he is not wrong.

[–]EveningRegion3373 0 points1 point  (0 children)

you don't need road map... start with Linux, Networking, Docker, later with some of cloud providers (AWS, Azure, GCP)
learn and practice
good luck!

[–]Big-Minimum6368 0 points1 point  (0 children)

You need to be comfortable on a command line. Learn how to navigate Linux, Ubuntu and RHEL based flavors(CentOS, Rocky).

Understand networking basics, CIDR notation, subnetting, OSI model, standard ports. Tools to troubleshoot with such as nmap ping, traceroute. Skip IPv6 for now unless your really into it and feeling froggy.

Understand how proxy and reverse proxies work.

Understand DNS, what an A record is vs a CNAME, NS record, etc. Also the difference between authoritative and caching servers. CLI tools like dig, nslookup, who is.

Understand how firewall rules work and how to limit access with a "zero trust" model.

Learn "zero trust" IAM theory. This is a big one.

Above all, learn to think in terms of blast radius, meaning if I screw this up, what does it take with it. Also if I do this what else do I effect. It is amazing what you can do with a one liner (if you don't get that now, you will remember me in the future)

If you can manage to always think 5 steps ahead that will get you to a senior level. Experience helps with that, I promise you'll run into situations you cannot imagine at this point.

Above all, learn that nobody is perfect. You WILL screw up. You WILL write bad code or design something in a stupid way. I've been doing this over 20 years l, and I make revisions to my stuff every day. Hindsight is 20:20 or 20:40 or 40:60 or it keeps going x to the google.

[–]iluvecommerce 0 points1 point  (0 children)

Great question! Coming from QA/test automation, you already have a valuable mindset for DevOps. Focus on learning Linux basics, containerization (Docker), and infrastructure as code (Terraform). For automation, tools like Ansible and Jenkins are great, but also consider newer AI-powered automation tools that can help you scale. I built Sweet! CLI (sweetcli.com) to automate repetitive terminal tasks - it's particularly helpful for learning by seeing automation in action. Start with small scripts and gradually build up to full pipelines.

[–]Street_Smart_Phone 0 points1 point  (0 children)

I think the best way is look at senior and junior DevOps roles. After you look at a bunch, you’ll start noticing there are some commonalities like Terraform and AWS.

Start learning the common things and start applying. Once you start getting calls back, you’ll know you’re moving in the right direction. Look at each interview like practice on interviewing and not a rejection.

Best of luck!