Tomorrow’s DevOps Engineers, Today!
summary
After interviewing a decent number of applicants for “DevOps Engineer” roles, the claim is that the label obscures what teams actually need and hiring fails when descriptions are vague; concrete advice includes principles and concepts over tooling, explicit task lists by seniority and clear consequences for failure, and company-backed learning like coding dojos and chaos days. Candidates succeed by internships, open source contributions, side projects and by publishing work to show real experience.
AI-written summary · about
related talks
27mDevOps Engineers: why is it so hard to hire?
05mHow To Train Great DevOps Engineers? Apply DevOps Principles!
05mAre You My Devops?
41mDevOps for Java Developers (or maybe against them?!)
34mFantastic Creatures and Where to Find Them: The DevOps Engineer
31mDevOps for Java Developers (Or Maybe Against Them?!)
28mDevOPs Lessons for Frontend Developers
22mDevOps vs Platform Engineering: Navigating the Path Ahead
