You cannot just be a devops engineer as soon as you pass out. It takes experience, production experience and a specific outlook towards release cycles. You will need to experience it on the job. But you can surely start your way into it. Start by automating stuff that you do manually. Start making doing things easier for people around you. Then start making systems reliable and highly available. You'll have to be open to learn new stacks everyday and at times try to resolve one bug for days. Being a devops engineer is kind of a deconstructed sysadmin. Who also has to code at times. Just start thinking of anything you need to do twice has to be automated.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You cannot just be a devops engineer as soon as you pass out. It takes experience, production experience and a specific outlook towards release cycles. You will need to experience it on the job. But you can surely start your way into it. Start by automating stuff that you do manually. Start making doing things easier for people around you. Then start making systems reliable and highly available. You'll have to be open to learn new stacks everyday and at times try to resolve one bug for days. Being a devops engineer is kind of a deconstructed sysadmin. Who also has to code at times. Just start thinking of anything you need to do twice has to be automated.