Portions of this post were originally posted on the Puppet blog, and are republished here with Puppet's permission.\nDemand for people with DevOps skills is growing rapidly because businesses get great results from DevOps. Organizations using DevOps practices are overwhelmingly high-functioning: They deploy 200 times more frequently, with 2,555 times faster lead times. They recover 24 times faster from failures, and have one-third the \u00a0change failure rate that other organizations experience, according to Puppet\u2019s 2016 State of DevOps Report.\nIf you believe DevOps is the future, our new ebook is for you. DevOps and You: Advice for Building Your Career includes stories of how people got started in DevOps, details on how to improve your DevOps skills, and advice for landing your next job.\nWhat are DevOps skills?\nWhether you want to be a DevOps engineer or site reliability engineer \u2014 two very common DevOps positions \u2014 you\u2019ll need to beef up your skills. While it\u2019s great to improve your coding skills, and get familiar with automation tools, you\u2019ll also want to seek out projects that allow you to exercise the people and communication skills that are at the core of DevOps.\nFind opportunities to collaborate within and outside of your team. Help your company move to a faster test and deployment rhythm. Be open to listening to others\u2019 ideas.\nKeep in mind that DevOps is less about doing things a particular way, and more about moving the business forward and turning technology into a strategic advantage.\nDevOps points to a growing recognition that software isn\u2019t written in the old way anymore. Where software used to be written from scratch in a highly complex and lengthy process, the complexity of today\u2019s software lies less in the authoring, and more in ensuring that the new software will work across a diverse set of operating systems and platforms right away.\nLikewise, testing and deployment are now done much more frequently. That is, these can be more frequent \u2014 if developers communicate early and regularly with the operations team, and if ops people bring their knowledge of the production environment to the design of testing and staging environments.\nWhat is a DevOps engineer? And should you be become one?\nThere\u2019s not a single established \u00a0track for becoming a DevOps engineer. In fact, many people \u00a0who start as developers find they're interested in deployment and network operations. Just as often, sysadmins discover a passion for scripting and coding, and work closely with the development side, helping to improve the testing and the rest of the deployment process.\nIf DevOps is understood primarily as a mindset, you don\u2019t actually need "DevOps" in your title. You do need to be able to offer an employer a core set of DevOps skills and knowledge:\n\n\nAbility to code and script, and use a variety of technologies and tools\n\n\nExperience with systems and IT operations\n\n\nStrong grasp of automation tools\n\n\nComfort with with frequent, incremental code testing and deployment\n\n\nData management skills\n\n\nA strong focus on business outcomes\n\n\nComfort with collaboration, open communication and reaching across functional borders\n\n\nDownload DevOps and You to hear from dozens of engineers, managers and recruiters whose jobs (or the jobs they're hiring for) emphasize DevOps practices, and you\u2019ll be on your way to transforming your current job \u2014or landing a new one.