EpicCleverName

DevOps Job Apps - Know Everything?

People who apply to DevOps job openings - do y'all actually have all that experience? Jenkins, Docker, AWS, Kubernetes, Puppet, Chef, etc. etc.? Even at the 10+ year level, that seems like a lot to be a master of, and especially so at the 2 year level.

Add a comment
Microsoft macheté Aug 7, 2017

Fake it til you make it. Seriously tho- 10+ years of DevOps? 😂 If you are a master of all the aforementioned tech above, you aren't a DevOps engineer, you are an architect

Synack vycE67 Aug 7, 2017

+1

Intuit baconoil Aug 7, 2017

Architects are the pension plan of software. Maybe 1 in 10 worthy of the title, and the other 9 will strangle a business to death with a lack of pragmatism. DevOps was never intended to describe individuals tho.

New
teez Aug 7, 2017

yeah, you pick it all up after a couple companies

Intuit baconoil Aug 7, 2017

Can confirm, am DevOps unicorn. Basically anyone that's run a startup past Series A checks all those skillset boxes. A manager once told me it doesn't matter how many years of experience you have, if you keep repeating the same year through your career.

Tableau pipe2null Aug 7, 2017

I've been doing dev ops for about 5 years and 10 years of systems engineering with automation focus before that. With the bonus of all that c++ from the CS degree. I'm strong in one of each type of tool but understand a bit better than a jr all the competitors. If your really good with Python you can be fairly competent in Ruby after a year or so. Same is true with Puppet/Chef/Ansible/Salt or AWS/Azure/Google Cloud. When I hire I don't care which tool you used as long as your deep in one of them.

Microsoft trenches Aug 7, 2017

DevOps isn't a specific role anyway, it isn't just something you do. I roll my eyes at reqs looking for a DevOps engineer. You aren't a super hero or a ninja, regardless of what the recruiter says. It takes more than just you to make shit happen. It is cultural adoption, teamwork and tight knit cohesion between two or more teams (dev, ops, infra, sec, etc) rolling in unison to create a great dynamic experience for the user. As mentioned above, if you've been thrown into the fire by yourself at a really small company or with a dedicated team, you will use all of the above and then some as you scale.

Mapp KFRT73 Aug 8, 2017

Am DevOps Engineer, can confirm it can be a role if a company lacks DevOps. I think SV nerds call the role "evangelist of ______" for other things. As far as work role, it's just basically being a build, release, automation, and operations engineer. Heavy emphasis on Automation. Having worked in software field for ten years now there are a lot of SysAdmin types and Developer types that are so silo'd they sometimes need me to help them make good decisions and show them how to save themselves time. Then my job is breaking down those silos. At a startup I agree no one has time for these all the be separate roles and you just do them, however in a lot of old school software companies no one is doing build/releases/automation/orchestration/containers/etc at all.

Mapp KFRT73 Aug 8, 2017

Fake it till you make it is right. No one expects you to know everything but they expect you to understand the role of each type of tech and know one of them well. for example I'm an Ansible, Docker, Jenkins, AWS, Go/Python guy. I don't know Ruby or TravisCI, Puppet/Chef, Kubernetes, but I could learn then quickly because I understand the tech.