YouTube pushes 'stop hiring DevOps'

Vasilios Syrakis published a YouTube video on August 6 titled “Stop Hiring DevOps Engineers,” framing DevOps less as a standalone job label than as a way software teams should build and ship products. The video was posted hours ago and had roughly 19,000 views when indexed by search results. Its YouTube page links to a blog post on Syrakis’s website titled “you don’t know DevOps,” tying the video to a longer argument about how companies organize engineering work. (youtube.com) ### Why does a YouTube title like this travel so quickly? The phrase “Stop Hiring DevOps Engineers” is blunt, and the YouTube listing pairs it with Syrakis’s 103,000-subscriber channel. The platform page shows the video was posted hours ago, which helps explain why the clip circulated quickly in engineering feeds on August 6. The linked materials suggest Syrakis is arguing against a narrow, siloed reading of DevOps rather than against infrastructure work itself. (youtube.com) His YouTube page points viewers to a blog post titled “you don’t know DevOps,” which indicates the target is the hiring label and the way companies define the work. ### What is the argument underneath the headline? The YouTube page itself does not expose a full transcript, so the clearest verified signal is the title, the linked blog post, and the surrounding framing on Syrakis’s channel. (youtube.com) Those materials indicate he is pushing a view of DevOps as shared engineering practice, not a separate function handed a deployment checklist after product code is finished. That framing matches a broader pattern in technical career content this summer. (youtube.com) TechWorld with Nana, in a separate July YouTube video about AI and DevOps work, described automation as making individual engineers “more powerful” and highlighted platform-engineering career paths in its supporting material. ### Are companies actually hiring for different labels now? Job-market language in 2026 increasingly emphasizes platform, CI/CD and cloud automation roles alongside or instead of classic DevOps titles. (youtube.com) A “Junior Platform Engineer” role description published in April says the job centers on building internal platforms and foundational infrastructure so product teams can “ship software safely and efficiently.” A separate “Junior CI/CD Engineer” description defines the work as improving the automated path from source control to tested and deployable artifacts. (youtube.com) Those postings are not a full labor-market census, but they show how the vocabulary is moving. Even where “DevOps” remains in a title, recent job descriptions stress cloud automation, containerization, deployment support and reliability work rather than a narrow operations handoff. ### What does that change for junior engineers? For early-career candidates, the hiring signal is less about abandoning infrastructure and more about showing broader ownership. (devopsschool.com) The role descriptions surfaced this week repeatedly ask for work across automation, deployment, cloud environments and operational improvement. A portfolio that shows an application, a deployment pipeline, monitoring and some cost or reliability controls fits that language better than a repository of isolated scripts. (digitalxnode.com) That is an inference from the job descriptions and Syrakis’s framing, not a direct quote from employers, but it follows the skills those postings list and the critique implied by the video’s title. ### Where can readers check the source material next? (devopsschool.com) The August 6 video remains on YouTube under Syrakis’s channel, where the listing links to his blog post for fuller context. Readers looking for the hiring-side language can also compare current platform-engineering, CI/CD and cloud-automation job descriptions, which continue to use the terms employers are putting in front of junior candidates. (youtube.com)