Why We Built CloudOpsJobs

When I was searching for my next role as a DevOps Engineer, I spent weeks wading through generic job boards. I'd search for "Platform Engineering" and get results for full-stack developers. I'd filter for "DevOps" and end up with sysadmin positions that hadn't been updated since 2015. The worst part? Half the time, the recruiter on the other end couldn't tell the difference between Kubernetes and a container of leftovers in the fridge.

If you've worked in Platform Engineering, DevOps, SRE, FinOps, or MLOps, you know exactly what I'm talking about.

The Problem Nobody Was Solving

I'm a DevOps Engineer and team lead in my current role, where I work with multi-cloud infrastructure, containerization, CI/CD pipelines, and infrastructure-as-code. I mentor junior engineers and make architectural decisions that affect how our entire team operates.

But when I looked for new opportunities, here's what I found:

Mislabeled Roles: A "Platform Engineer" job that was actually a front-end React position. An "SRE" role that was really just on-call support with no automation or engineering work. A "DevOps Engineer" position that was 90% manual deployments and clicking buttons in a UI.

Poor Matching: Generic job boards don't understand the nuances. They treat "AWS" as just another keyword, not recognizing that someone with deep EKS experience is fundamentally different from someone who spins up EC2 instances. They can't distinguish between a Platform Engineer building internal developer platforms and a DevOps Engineer maintaining CI/CD pipelines.

Recruiter Friction: I'd get contacted about "DevOps roles" that required zero cloud experience. I'd see postings asking for "5 years of Kubernetes experience" when Kubernetes itself was only 6 years old at the time. The disconnect was real.

It's Not Just Job Seekers

The problem goes both ways. As someone who's been on hiring committees, I've seen how hard it is to find qualified Platform Engineering talent through traditional channels.

You post a role for an SRE with Terraform and observability experience. You get 200 applications. 150 are from people who've never touched infrastructure-as-code. 30 are from recruiters mass-applying. 15 are from developers who think "DevOps" means writing deployment scripts. You're left with maybe 5 qualified candidates buried in the noise.

Meanwhile, the exact person you need is out there, frustrated because they can't find roles that match their actual skillset. They're scrolling past your posting because it's drowned in irrelevant results, or because the job title doesn't match what they're searching for.

The numbers back this up. According to recent industry research, 37% of IT leaders identify DevOps and DevSecOps as their top technical skills gap, while 19% of recruiters report struggling to find experienced DevOps professionals. This isn't a talent shortage problem—it's a matching problem. The right people exist, but they're buried under noise on generic job boards that don't understand the nuances between a Platform Engineer and a full-stack developer.

The Market Gap

Here's what became clear: the cloud operations space needed its own job board. Not because we're special or elite, but because our roles are fundamentally different from traditional software engineering positions.

A Platform Engineer isn't just a developer who knows Docker. An SRE isn't just a sysadmin who learned Python. A FinOps Analyst isn't just an accountant who works with AWS bills. These are distinct disciplines with their own tools, practices, and career paths.

Generic job boards can't handle this nuance because they're built for volume, not precision. They optimize for SEO and ad revenue, not for matching the right engineer with the right role.

Why CloudOpsJobs Exists

That's why I built CloudOpsJobs.

This isn't a VC-backed platform trying to disrupt everything. It's not a marketplace charging premium prices for "exclusive access." It's a focused job board built by someone who lives in this world, for people who work in this space.

Here's what makes it different:

Specialized Categories: We don't lump everything under "DevOps." We have distinct sections for Platform Engineering, SRE, DevOps, FinOps, and MLOps because these are different roles with different requirements.

Cloud-Native Focus: Every job is pre-filtered to be relevant to cloud operations. No more sorting through unrelated postings. If it's on CloudOpsJobs, it's actually a cloud operations role.

Quality Over Quantity: We're not trying to list every job on the internet. We're trying to list the right jobs for cloud operations professionals.

Built by Engineers: I know what it's like to evaluate infrastructure code at 2 AM. I understand the difference between multi-cloud architecture and vendor lock-in. I've been in the on-call rotation. This platform reflects that understanding.

What's Next

CloudOpsJobs is just getting started, but the vision is clear: build the best place for cloud operations professionals to find their next role and for companies to find the talent they need.

Here's what I'm working on:

• Better filtering: Search by cloud provider, tools, and infrastructure patterns that actually matter (IaC, GitOps, observability stacks)
• Company insights: Transparency about on-call expectations, team size, tech stack, and engineering culture
• Community resources: Eventually, this won't just be a job board. It'll be a hub for the cloud operations community with guides, salary insights, and career development resources.

The goal isn't to replace LinkedIn or Indeed. It's to create a signal-to-noise ratio that actually works for our niche. When you search for a Platform Engineering role on CloudOpsJobs, you should find Platform Engineering roles. Not full-stack positions in disguise. Not legacy IT jobs with a cloud keyword sprinkled in. Actual, relevant opportunities.

Join Us

If you're a job seeker: Browse the jobs, set up alerts, and let me know what you'd like to see. Your feedback shapes this platform.

If you're hiring: Post your cloud operations roles where they'll actually be seen by qualified candidates. No inflated costs, no algorithmic games, just direct access to people who do this work. Click here to find out more.

And if you're just interested in where this goes: stick around. I'm building this in public, and I'd love to have you along for the ride. Find us posting on this blog or on X @cloudopsjobs

Let's make job searching in cloud operations a little less painful.

---

Jimmy is a DevOps Engineer, team lead, and mentor with experience deploying to and managing multi-cloud infrastructure. He built CloudOpsJobs because he was tired of generic job boards that don't understand cloud operations roles. You can find him on the platform or reach out with feedback.