Someone recently asked about a tech vacancy and it seemed like they had plenty of developers, back-end, front-end designers and data scientists on their team. What was missing is someone who would be the gatekeeper, someone in whose hands you could hand over the keys and they could ensure your sound sleep. They asked for help on what qualities to look for while interviewing someone for the role and I hope this post is useful for someone looking to hire or evaluating their own career trajectory in this role.
A description on the wiki page goes like this :
"A set of practices intended to reduce the time between committing a change to a system and the change being placed into normal production, while ensuring high quality."
In the present context, the foremost skills goes along the agile concepts:
- Continuous Deployment: Containerization, its packaging, deployment and monitoring of cloud native applications and dependent services.
- Continuous Integration: Knowledge of setting up an integration pipeline which involves gather unit test, integration test results, building and maintaining artifacts versions etc.
Dilletante & Communicator
General qualities which one sees in such an individual is a know how about practically everything. As a devOps, though coding might not be an everyday task, it is preferred that it is someone who considers themselves as a dilletante of languages, new frameworks, sdk and api libraries with a sprinkle of scripting and handy with the shell commands. He / She knows not only all the team members and stakeholders on a first name basis but perhaps even their family and kids. This relationship is often reciprocal in nature and even they have him / her on speed dial and become the goto person when anything goes south.
Systems thinking + Attention to Detail
Being the true gatekeepers of any solution, a system thinking approach to the overall solution is of priority. At any stage the architecture of data flow and control show should be so clear that they can draw it even if asked at 3am. Attention to detail could seem contrary to the previous quality but it is the team priority to inform and keep the devops person updated of the parameters and controls for each of these individual systems.
Integrity
Situation specific integrity is also another trait amongst these Jedi masters. They are the ones who will refuse to promote a change to prod without being tested on a regular day at the risk of sounding like a blocker. But at the same time, when shit hits the fan, they will take the call to rip apart the prod server module by module with their root admin access. They are the ones who would ensure IPs have been whitelisted, SSL certificates have been installed, backups been taken, config been setup.
Experience and Exposure
Finally a reliable devops is usually someone who doesn't panic at the drop of the hat. They have seen their fair share of deployments, misconfigurations, backup failures, production bugs and roll on with the day even be it with some grumbling along the way.













