Hey everyone! I'm Dhyan, a student at a tier-3 college with less than ideal placement opportunities—only about 3% of students get placed. I'm determined to break into DevOps by building my skills independently. Here's my plan:
**Stage 1:** I'm diving into Data Structures and Algorithms (DSA) first because I've heard it's crucial for interviews.
**Stage 2:** Next, I'll strengthen my fundamentals in computer science, covering areas like operating systems, Linux commands, and networking concepts. I also want to learn Git and GitHub to manage my projects and showcase everything I create.
**Stage 3:** Then I'll focus on mastering AWS, getting familiar with core services like EC2, S3, IAM, and more.
**Stage 4:** After AWS, I plan to learn Python for automation and then move on to Terraform for managing AWS infrastructure. I also want to get into Docker and CI/CD practices alongside monitoring tools like CloudWatch and Prometheus.
Throughout this journey, I'll work on personal projects and upload them to GitHub to build a portfolio. What do you think of my plan? Am I on the right track, or should I make any changes or add anything important?
4 Answers
Definitely consider adding shell scripting alongside Python, maybe even Go after that, since those skills will be very beneficial in later stages of DevOps. I'd place that learning in between your second and third stages.
You might want to rethink your sequencing a bit. Starting with heavy DSA could slow you down because what really matters in DevOps is understanding practical system knowledge and automation skills. You should jump into Linux, networking, and some basic scripting first. Scale back the DSA focus and work more on your foundational skills in Stage 2. Your later stages, especially your plans around AWS, Docker, and CI/CD look great! Just don’t forget about configuration management tools like Ansible or Chef, and definitely learn Kubernetes after Docker. Also, I'd recommend getting a handle on monitoring tools earlier since observability is key in DevOps. Your project-centric approach is spot on—employers want to see actual work, not just certifications!
Thanks for the insights! How deeply should I dive into DSA just to handle interview questions?
Your plan looks well-structured! Just make sure you’re getting hands-on experience while learning. Shell scripting should be one of your early focuses, and don't skip Kubernetes after Docker. Staying active in communities for support is a high five—definitely on the right path! Have you checked out resources like kubecraft for more detailed insights?
I will! Thanks a bunch!
Before diving in, it might be worth browsing this forum for advice on starting in DevOps; similar posts have been discussed a lot here. Also, think about your motivations—why do you want to pursue DevOps? It shouldn't just be about the money. It's crucial to be genuinely interested in the subject to put in the effort needed to succeed. As for GitHub, I don’t see it as a solid portfolio tool, since many projects lack originality. However, as long as you truly understand what you’re creating, storing your work there is fine! Just know interviewers can often spot boilerplate projects.
Sure, I'll check it out! I find DevOps really interesting, and if I just wanted money, I'd have gone towards management instead. I think GitHub is a good way to store my progress; I’d know my projects inside out!
Sounds good, will do! Thanks for your advice!