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.
DevOps is a versatile role, that can be a bit tricky. It's more about the setting up the flow of value from idea inception to deploying the code to production(and everything in between like testing, etc).
But start small. Set up a simple deployment workflow. Read about Continuous Integration and Continuous Delivery. Learn about automated testing. Set up your own Jenkins pipeline, connect it with Github or Bitbucket.
A good intro would be reading "DevOps Handbook" or the "Phoneix Project" to understand that DevOps is less of a skillset, and more of a set of ideas and values. Yes, there's a lot of overlap with a sysadmin role, but there's also programming and management involved. It's a wide field so start fiddling with some tools and you'll get to it.
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.
How can one become a devops engineer after graduating college? What sort of skills are required? Also, how much does devops overlaps with sysadmin?
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.
DevOps is a versatile role, that can be a bit tricky. It's more about the setting up the flow of value from idea inception to deploying the code to production(and everything in between like testing, etc).
But start small. Set up a simple deployment workflow. Read about Continuous Integration and Continuous Delivery. Learn about automated testing. Set up your own Jenkins pipeline, connect it with Github or Bitbucket.
A good intro would be reading "DevOps Handbook" or the "Phoneix Project" to understand that DevOps is less of a skillset, and more of a set of ideas and values. Yes, there's a lot of overlap with a sysadmin role, but there's also programming and management involved. It's a wide field so start fiddling with some tools and you'll get to it.