[00:03] DevOps that nobody talks about. You understand quality gates, testing strategies, failure scenarios, which is exactly what DevOps needs, especially the part that is called CI/CD automation. Because as a test automation
[00:18] engineer, you already know how to write logic to test different scenarios. So, you can take your scripting or programming skills and translate that directly to infrastructure as code automation. Because infrastructure as
[00:31] code is basically just scripting logic to automate creating infrastructure. But your challenge, something that is not your strength and you would need to learn completely new is learning infrastructure and cloud platforms. So,
[00:44] as a QA or test engineer, that's probably going to be your weakest spot, and that means you will know exactly where to invest most of the time because it is going to be a new land, foreign land for you, but once you learn that
[00:58] part, then you can very easily connect all the dots together. And I always recommend to choose one cloud platform, usually AWS, and learn the cloud and infrastructure concepts first, and then learn maybe four to five basic AWS
[01:14] services in the context of application deployment. And in terms of a timeline, if you really dedicate your time and focus on this transition, four to six month of commitment will be more than enough for you to get deep level
[01:31] knowledge of DevOps. Not just shallow, I understand a little bit of Docker and Kubernetes and CI/CD, but like really, really understand and be able to build actual end-to-end processes in DevOps. That's exactly why we're doing for a
[01:46] limited period of time completely free orientation calls with engineers all over the world in our community to help them understand and get clarity on their next steps. The link is going to be either in the comments or in the bio, so
[02:01] either in the comments or in the bio, so make sure to check it out there.