4 ms·
On the flip side, I just interviewed two candidates claiming 10 and 16 years of experience for a "Senior DevOps" position. Neither of them could tell me what a
by markatto 10y ago
On the flip side, I just interviewed two candidates claiming 10 and 16 years of experience for a "Senior DevOps" position. Neither of them could tell me what a default route was - one of them spewed some nonsense buzzwords and the other one thought it might have something to do with DNS.
- benjaminwootton 10y agoDevOps doesn't imply network knowledge. It can include CI/CD, dev tooling, automation, containers, cloud engineering etc. Just saying in case you and your candidates have a different idea of the role you are hiring for.
- zandor 10y agoI'd say that network knowledge is a key part of the Ops part of DevOps (especially when talking about cloud engineering). But that is what you get with great buzzwords like DevOps.
- mugsie 10y agoDevOps is a culture not a job. Most good candidates know this, and will actively avoid "DevOps" roles. Now someone claiming 10 - 16 years experience as a DevOp, is : A: Lying. The term is 6-7 years old B: If they have even been using / administering computers for that long should know what a default route is. Could they have misinterpreted the question? I know the even at a senior level, interviewees can get flustered and confuse themselves.
- markatto 10y agoI didn't write the job title/posting, but the description makes it clear that strong linux and programming skills are required. These folks have 10+ years of "software engineer" and "systems administrator" jobs on their resumes, they're not claiming specific "devops" experience. I just talked to two more similar folks and I'm starting to despair at the state of the industry. What job title would you suggest to find people with a working knowledge of programming, config management, and infrastructure/systems internals? If all you can do is copy-paste jenkins tutorials off of the internet, you're not a "senior" anything.