hirly

Cloudzero

Senior CloudOps Engineer

Boston, MA

Apply through hirly

hirly scores this role against your resume, shows its reasoning, then writes a resume and cover letter for it and fills the application with you. Free to start — no card required.

hirly's read of this role

Seniority
Senior
Country
US
Work mode
Remote-friendly
First seen by hirly
2 Sept 2026

Derived automatically from the posting. Sign up to see how the role scores against your own resume.

the posting

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!

Is this role actually a fit for you?

hirly answers with a score and its reasoning, then writes the resume and cover letter if you decide to go for it.

Score it against my resume
Senior CloudOps Engineer at Cloudzero — hirly