Back to Jobs

Cloud Observability and Monitoring Engineer

Not Disclosed

Job Description & Details

This is a heavy-duty cloud observability role where you will design and build unified monitoring across AWS, Azure, and GCP. If you enjoy wrangling telemetry, taming multi-cloud complexity, and automating everything through Terraform, this gig gives you the ownership to do it right.

What You'll Actually Be Doing

You'll spend your days building the visibility layer that keeps massive multi-cloud architectures from turning into black boxes. Your core duties include designing end-to-end dashboards, setting up smart alerting rules that don't trigger alert fatigue, and configuring robust log, metric, and trace pipelines. You'll be collaborating closely with security and platform engineering teams to ensure every new cloud landing zone ships with baked-in observability.

The Core Tech Stack

Tight Terraform expertise is non-negotiable here since all infrastructure and monitoring configs must deploy via code. You need deep, native fluency in at least one major cloud provider (AWS, Azure, or GCP) combined with battle-tested experience in enterprise observability tools like Datadog, Dynatrace, Prometheus, or Splunk. Proficiency with CI/CD engines like Jenkins and GitHub Actions is mandatory for keeping automated pipelines humming.

Interview Expectations

Expect the hiring team to present a real-world scenario where a distributed application is throwing intermittent 500 errors across a hybrid architecture, and they'll want to hear your step-by-step methodology for isolating the root cause using traces and logs. They are secretly testing whether you rely on brute-force troubleshooting or if you take a systematic, telemetry-driven approach to incident response.

Application Advice

Skip the generic system administrator talking points and focus your resume squarely on your Infrastructure as Code and observability wins. Highlight specific instances where you used Terraform to automate monitoring rollouts or tuned noisy alert thresholds in tools like Datadog or Prometheus. Make sure keywords like 'Telemetry', 'Terraform', and 'Multi-cloud' stand out clearly to get past the automated ATS filter.