Even “DevOps Engineers” don’t call themselves this way.. at least most of them. This role name is more used by recruiters and headhunters more than anyone else but now since it’s common to say “DevOps Engineer”, I will be using it in this article!
What is DevOps ?
DevOps is not a just a role or a team, it started with a movement, a philosophy or better: a culture.
DevOps is not tooling and tooling is not engineering. A good engineer is the one who has the capacity to learn new technologies, someone who never stops learning!
What are some technologies you are learning this period ?
DevOps, agile, lean, Kanban are sets of behavioral and cultural skills and checklists. DevOps focus on modernizing teams before technologies.
I worked with companies where technologies and tools are underused because of cultural problems.
What are some cultural problems you have seen during your last experiences and what solutions you imagined to make things better ?
Some “DevOps engineers” comes from system administration, others come from development teams, but the ideal DevOps should come from both ops and dev teams and can speak the language of each team.
What have you been doing over the last 3 years?
Release management is one of the most important skills. It is not just some tools and techniques but requires a good understanding of business KPIs like Time To Market.
What are some metrics that could measure the DevOps success in an organization ?
Automation is one of the keys to DevOps success. Find out how much your candidate is passionate about solving business and technical problems by automating stuff!
What is the configuration management tool you use and why ?
However, automating failure or vulnerable systems may cause a disaster:
How to implement security and quality checks in a DevOps environment?
There is an urban legend that says that developers and software engineers care less about money than the project itself. This is a myth. If 10% or 20% or even 30% of engineers think that way, this doesn't mean every other engineer think the same way.
Sure, an interesting project is a source of pride and fulfillment and a springboard to success but between two interesting projects, it is evident to choose the one with the higher compensation.
Compensation could be the first thing that impacts the choice of your candidate. If you are sure that the developer who stands in front of you is the right one to recruit, make sure to suggest a motivating salary.
€$$ $$€$€€$ $$€$$€$$$, $€€$$$€$$$€€€€$ $$ €$€$$$€€$$€€$ $$ ! $$€€$$€ ???
For the vast majority of any developer and IT professional, freedom is important.
The first freedom is freedom of choice.
As a recruiter, you should understand that hackers are like painters, both are creative and creativity needs freedom.
Besides, everything in the IT ecosystem is disputable, debatable and questionable. Technologies are not established as facts, and so open to question or debate.
This is why some of us do not use proprietary solutions while others do not find any problem in using proprietary and closed source systems. This is also why some of us use this or that technology while others find that a madness .. There are plenty of examples.
Take this as a reality: The candidate will choose the work environment that gives her/him the freedom to choose, test and learn.
Technology is moving fast and one should follow tech trends. After all, DevOps is about learning, building and measuring to generate feedback.
Do you contribute to Open Source projects or have side projects ?
Of course, you should ask technical questions and test the skills of your candidate. A good engineer should have knowledge in development, operations, QA, tooling, releasing software, building, CI, CD, network and security. Well, in my experience, DevOps practitioners will touch everything.
How does traceroute work ?
(Note that the questions I share in each tip are just for here are indicative only)
I co-wrote this checklist and it may help you:
The Must Know Checklist For DevOps & Site Reliability Engineers (Updated)_This list is not exhaustive but enumerates only technical basic, must-know skills, and some random thoughts. You may…_medium.com
DevOps professionals are faced to manage emergencies and blackouts.
We act like firefighter.
These special cases require a good understanding of IT processes, good technical knowledge, and proven experience. Ask about incident management and postmortems.
What’s the first thing to do after fixing a production problem ?
Our community counts more than 10k members and our sponsored posts reach more than 20k DevOps practitioners.
Posting your job in our job board Jobs For DevOps, will help you in reaching this community.
Once your job is posted to the job board our web bot Kina, will share it on our Social media accounts + our Slack team chat.
Read more here:
Jobs For DevOps: Welcome Kina the Bot_Jobs For DevOps is the DevOps job board of eralabs tribes ecosystem. It is dedicated to promoting your job offer and…_medium.com
If you are an employer, you can create an employer profile and start posting your job offers. It depends on the plan you want to use but your job offer could be shared to our weekly newsletter and our Slack team chat (channel #jobs) so it could be seen and noticed by people that are really looking for new opportunities.
You can find plenty of other questions to ask, like the ones that I published in “The Must Know Checklist For DevOps & Site Reliability Engineers” article, but keep in mind that not only technical aspects are important but also the human sides of this cultural shift: Check my article The 15 Point DevOps Checklist.
We helped companies and candidates get in touch and will continue to provide more help and improve the job board. If you have any feature request, idea or suggestion, we will be glad to hear from you, get in touch with us using this form.
For more updates, deals and exclusive news, don’t forget to join Jobs For DevOps Facebook group and Linkedin group.
Do you want to give it a try? Post your job on Jobs For DevOps, and Kina will do the rest.