1

Cloudops Engineer Jobs in Massachusetts (NOW HIRING)

Senior CloudOps Engineer

Boston, MA · On-site

$130K - $190K/yr

As a Senior Site Reliability Engineer you'll be a force multiplier for our engineering organization, owning the reliability, performance, and observability of the systems every team depends on, and ...

IT Infrastructure Systems Engineer

Wilmington, MA · Hybrid

$117K - $154K/yr

... Engineer to join a dynamic, security-first IT team operating across on-premises, hybrid cloud, and ... Cloud Operations (CloudOps) * Administer and optimize Azure and/or AWS cloud environments ...

Chief Product & Technology Officer (CPTO) Embedded collaboration with: ◦ Vertical engineering leaders (Platform, SCADA, EMS, APM, CloudOps, CAM/FSM/Product Ops) ◦ Product Management and Product ...

With decades of multicloud experience, we have specializations in Kubernetes, GenAI, CloudOps, and ... The Opportunity We're building a technical content program to serve data engineers, analytics ...

With decades of multicloud experience, we have specializations in Kubernetes, GenAI, CloudOps, and ... Approve the Finance Engineer's FP&A automation roadmap quarterly. * Build trusted relationships ...

Cloudops Engineer information

See Massachusetts salary details

$41.5K

$126.5K

$209.1K

How much do cloudops engineer jobs pay per year?

As of Sep 2, 2026, the average yearly pay for cloudops engineer in Massachusetts is $126,538.00, according to ZipRecruiter salary data. Most workers in this role earn between $90,600.00 and $165,500.00 per year, depending on experience, location, and employer.

What is the difference between Cloudops Engineer vs DevOps Engineer?

AspectCloudops EngineerDevOps Engineer
CredentialsCloud certifications (AWS, Azure, GCP), Linux, scriptingDevOps tools, CI/CD, scripting, cloud knowledge
Work EnvironmentCloud platforms, infrastructure management, cloud servicesDevelopment pipelines, automation, collaboration between development and operations
Industry UsageCloud service providers, SaaS companies, enterprises adopting cloudSoftware development companies, tech startups, organizations implementing CI/CD

While both roles focus on infrastructure and automation, Cloudops Engineers primarily manage cloud environments and services, whereas DevOps Engineers focus on integrating development and operations through automation and continuous delivery. The roles often overlap but differ in their core focus areas and tools used.

Are cloudops engineers still in demand?

CloudOps engineers are currently in high demand due to the increasing adoption of cloud infrastructure and the need for managing cloud environments efficiently. Skills in cloud platforms like AWS, Azure, or Google Cloud, along with automation tools and scripting, enhance job prospects in this field.

What does a Cloudops engineer do?

A Cloudops engineer is responsible for managing and maintaining cloud infrastructure, ensuring system reliability, security, and performance. They often work with cloud platforms like AWS, Azure, or Google Cloud, using tools such as Terraform or Kubernetes, and may require knowledge of scripting and automation to optimize cloud operations.

What are popular job titles related to Cloudops Engineer jobs in Massachusetts?

For Cloudops Engineer jobs in Massachusetts, the most frequently searched job titles are:

What job categories do people searching Cloudops Engineer jobs in Massachusetts look for?

The top searched job categories for Cloudops Engineer jobs in Massachusetts are:

Infographic showing various Cloudops Engineer job openings in Massachusetts as of August 2026, with employment types broken down into 87% Full Time, 8% Part Time, and 5% Contract. Highlights an 86% Physical, 5% Hybrid, and 9% Remote job distribution, with an average salary of $126,538 per year, or $60.8 per hour.

Senior CloudOps Engineer

CloudZero

Boston, MA • On-site

$130K - $190K/yr

Full-time

Re-posted 2 days ago


Job description

About the Role
CloudZero is growing fast. Our customer base is expanding, the data challenges we're solving are getting more complex, and the platform is scaling to match. We're standing up real-time ingestion on Kafka right now, spanning several engineering teams, and it's the most operationally demanding thing we've built. Nobody owns the reliability of that path end to end today. That's the first thing you'd own. As a Senior Site Reliability Engineer you'll be a force multiplier for our engineering organization, owning the reliability, performance, and observability of the systems every team depends on, and empowering teams to ship features that help customers understand and optimize their cloud spend.
This is real infrastructure work at real scale, not a ticket-closing role and not a console-clicking job. CloudZero processes billions of events daily across AWS, Azure, and GCP. Our customers rely on real-time, accurate cost data to make business-critical decisions, and any instability in our system impacts their planning. Built entirely on a unique serverless architecture with no EC2s and no containers, our platform demands infrastructure that scales gracefully, fails predictably, and recovers automatically. There are no Kubernetes clusters or broker fleets to tune here, so the reliability work is engineering, not firefighting. On-call is light: Nimbus carries a weekly rotation for shared infrastructure, and feature teams respond for their own services.
If you thrive on hard operational problems, care deeply about reliability and performance, and want to see your work matter to customers in direct and measurable ways, this role was built for you.
What You'll Do
Reliability and Observability
  • Own the reliability practice for CloudZero's real-time ingestion path: SLOs that span team boundaries, the failure modes nobody owns because they live in the seams, and the architectural changes that come out of what you learn
  • Sign off on shared critical paths before they go live, and call the pause conversation when an error budget burns
  • Instrument systems so that failures surface quickly and debugging happens with data, not guesswork
  • Build observability into everything so you know about problems before customers do

Python and Infrastructure as Code
  • Build the reliability tooling, not just the recommendations: load generators, fault-injection harnesses, SLO instrumentation libraries, deployment safety checks
  • Write production Python across shared libraries, internal services, automation, and agents, and set the standards others build against
  • Design and maintain CloudFormation and SAM modules that provision reliable, cost-efficient cloud resources
  • Own infrastructure end to end with no clicking through consoles

Automation
  • Automate deployments, scaling, backups, and limit changes; if humans are doing it repeatedly, build a system to do it instead
  • Balance automation intelligently, building solutions to real problems rather than automating for its own sake
  • Evaluate the autonomous agents we already run in production honestly, make the good ones excellent, and throw away the ones that aren't worth it
  • Make our systems legible to AI tooling as well as to people, starting with the service and ownership metadata in our developer portal

Partner with Product Engineering
  • Help teams design resilient services, review architectures for operational complexity, and build deployment pipelines that enable safe and fast shipping
  • Bake SLOs and instrumentation into shared templates so teams inherit good practice instead of reinventing it
  • Drive adoption across 40+ engineers by building the case, not by mandate
  • Optimize for cost and performance; CloudZero's business is helping others optimize cloud costs, and we should be exemplars of efficient cloud usage ourselves
What You Bring
  • Strong production Python as your primary language, owned, tested, and maintained at scale
  • An SLO you defined yourself, including what you deliberately chose not to alert on
  • Experience operating asynchronous, event-driven systems and reasoning about back-pressure, consumer lag, replay, poison messages, and partial failure (Kafka, Kinesis, SQS, Pulsar, or Step Functions; we run MSK, so failure reasoning matters more than broker tuning)
  • One reliability or platform change you drove through a team that didn't report to you and hadn't asked for it
  • Enough production time to have owned reliability outcomes rather than reliability tasks, which usually means 5+ years building and operating distributed systems in AWS
  • Infrastructure as Code in practice, using CloudFormation and SAM or transferable depth in Terraform or Pulumi
  • Hands-on experience instrumenting systems in monitoring tools such as Sumo Logic, Datadog, Prometheus, or Splunk, not just reading dashboards
  • Proven ability to debug production issues under pressure
  • An appetite for frontier AI models such as Claude, Codex, or Gemini
  • Values thoughtful, reliable system design over reactive hero efforts
  • Strong documentation habits to support long-term team clarity and system stability
  • Ability to clearly explain complex technical issues to non-technical stakeholders
  • Energized by breadth: comfortable holding several areas at once, going deep in whichever one is currently on fire, then handing it back as a standard and moving on
  • Bonus: chaos engineering or load testing as a practice you built, internal developer portal experience (Cortex, Backstage), test automation or ephemeral test environments, GitHub Actions at scale, LLM-backed tooling real engineers used daily

About CloudZero
CloudZero is the AI ROI Company. We built the financial control plane for AI: the system finance, IT, and engineering use to connect every AI dollar to the outcome it produced. Across every provider. In real time.
AI spend is the fastest-growing line on enterprise P&Ls and the least understood. Only 14% of CFOs can prove AI ROI today. CloudZero answers the question no one else can: what did it cost to produce this outcome, for this customer, on this model.
The largest cloud spenders on the planet already run on CloudZero, including Coinbase, Duolingo, DoorDash, and Shutterstock. We processed 14 trillion billing events in the last twelve months. We're the first listed partner on Anthropic's cost and usage API. We've raised over $119 million, including a $56 million Series C backed by leading venture capital firms.
Why Join Our Team?
At CloudZero, you'll find a collaborative, fast-moving environment where your work makes a direct impact. We're a team that values ownership, creativity, and curiosity - and we're tackling some of the most complex challenges in the cloud space. If you're excited by working with cutting-edge technology, driving meaningful outcomes, and growing with a company that's scaling fast, we'd love to hear from you!