With the rapid growth of DevOps teams and jobs, it tracks that there are candidates out there who are expanding — or flat-out forging — their significant skills and experience. We sat down with Nick Piette, Director of Product Marketing API Integration Products here at Talend to get the inside exclusive on how to commercial the DevOps fakers in the crowd:
- What signs should you look for on a resume or LinkedIn profile that somebody is faking their DevOps qualifications?
For individuals requesting DevOps experience, I tend to look for the allowing technologies we’ve seen pop up since the idea’s inception. What I’m looking for often depends where they are coming from. If I see they have hard programming knowledge, I look for free examples where the candidate references knowledge with basis control management (SCM), form automation, or containerization technologies. I’m also watching for what infrastructure displays and configuration management tools they have used in the previous. The opposite is true when candidates come from an operations background. Do they have coding experience, and are they capable in the latest domain precise languages?
- What symbols should you look for in an interview?
How should you draw these out? DevOps is a methodology. I ask interviewees to provide concrete examples of overpowering some of the challenges many organizations track into, how the candidate’s team summary the cost of downtime, how they felt the conversion of present manual tests to automated tests, what plans they executed to prevent code getting to the main branch, what KPIs were used to measure and dashboard. The main is the detail — individuals who are indefinite and lack attention to detail increase a red flag from an experience position.
- Do you reflect DevOps know-how is easier to fake (minimum up to a point) than technical skills that might be easier caught in the screening/hiring process?
Yes, if the interviewer is just examined for understanding vs. experience. It’s easier to speak up on the methodology and best practices and have book intellects than it is to have the technical experience and street smarts. Asking about both during an interview makes it tougher to fake.
Suggested read: Advantages of adopting DevOps
- How can you teach people who turn out to have DevOps-related deficiencies?
Every organization is changed, so we always expect some sort of deficiency related to development. We do the best we can to ensure everything here is documented. We’re also practicing what we preach-it’s a mindset and a company policy.
- Should we be skeptical of people who define themselves as “DevOps gurus,” “DevOps ninjas,” or like in their online profiles?
Yes. There is a difference between being an early adopter and an expert. While features of this methodology have been everywhere for a while, momentum really happening over the last couple years. You might be an expert with the technologies, but DevOps is much more than that.
Also read: The true power of enterprise DevOps