{"id":999882129,"date":"2013-09-20T13:37:00","date_gmt":"2013-09-20T13:37:00","guid":{"rendered":"https:\/\/dice.npgdev.com\/?p=574011509"},"modified":"2013-09-20T13:37:00","modified_gmt":"2013-09-20T13:37:00","slug":"devops-engineer","status":"publish","type":"post","link":"https:\/\/dice.npgdev.com\/hiring\/recruitment\/devops-engineer","title":{"rendered":"Tech Hiring Guide: DevOps Engineer"},"content":{"rendered":"

Return to Technical Hiring Guide<\/a><\/p>\n

DevOps Engineer<\/span><\/strong> This is a newer role and represents the bridge between the worlds of building software and the operations required to support it. As more organizations move into the cloud, and running systems becomes more about writing code than about configuring hardware, you\u2019ll see more of these roles and responsibilities being created. This role requires a candidate who understands the operational best practices of a website, but who also has the programming skills (or at a minimum strong scripting skills) of a software engineer. It is very hard for someone to fill this role without at least some experience running a production website, unless the role is in a bigger company with a larger support staff to properly train new hires. Software engineers are usually great fits for DevOps positions; excellent candidates will have a great passion for debugging and troubleshooting systems, and deeper systems knowledge. DevOps candidates can also come from system administrator roles who have a strong software and coding background, but with a solid handle on the operations required to deploy and release software. In general, this role usually requires a decent amount of programming, so it is more common to see an engineer moving into a DevOps role than a system administrator, because of the programming knowledge required going in. Questions for DevOps Engineers:<\/span><\/strong><\/p>\n