I'm a recent Computer Science graduate currently weighing my options between waiting for a delayed software development job offer or jumping into a TechOps position right now. The TechOps role would involve production support, monitoring, incident/ticket handling, and some basic scripting. My ultimate goal is to transition into a DevOps engineering role. I'm really interested in hearing insights from those already working in this field.
- Is it realistic to move from TechOps to DevOps within 2–3 years?
- What specific skills, tools, and certifications should I focus on right from the start to enhance my candidacy for DevOps?
- In my current TechOps work, which areas should I concentrate on to align better with DevOps methodologies?
- Are there any common pitfalls I should be aware of to avoid getting stuck in support roles indefinitely?
Any guidance or personal experiences would be super helpful! Thanks a lot! 🙂
2 Answers
The TechOps role can offer server management and infrastructure monitoring, but it might not expose you to the DevOps side as much as you'd like. If you can, I'd recommend waiting for a development role since you'll get coding experience, which is essential for DevOps. If you choose TechOps, be prepared to learn cloud and automation on your own since the workload can be a barrier to DevOps exposure.
Starting in TechOps can be a great foundation for moving into DevOps, especially if you focus on automation and CI/CD processes. Just be careful not to get stuck in support tasks. For interviews, check out prepare.sh for practical DevOps interview questions; it's a huge help!
Thanks for the tip! If I end up in TechOps, I'll make sure to focus on automation and cloud tech instead of getting bogged down in ticket issues. I appreciate it!
It's mostly about job monitoring and ticket handling, which makes me hesitate. My dev offer is taking forever. Should I wait for the dev position or start with TechOps to learn cloud/automation on my own? Thanks for your advice!