Staff Engineer, Cloud Platform

📋 Job Overview

All roles at JumpCloud® are Remote unless otherwise specified in the Job Description. We're hiring a Staff Engineer to join JumpCloud's Cloud Platform organization, with a focus on observability and FinOps. You'll own the questions that matter most as we scale toward 99.99% availability: can we see what's happening across the platform, how fast do we recover when something breaks, can we survive a regional outage, and are we spending enough to run it all? This is a hands-on staff role.

🏢 About JumpCloud®

JumpCloud® is the AI-powered unified IT management platform designed to secure the modern workforce. By consolidating identity, device, and access management, JumpCloud provides intelligent, secure IT that scales from human users to autonomous AI agents. We help organizations around the globe eliminate complexity and turn AI risk into an optimized advantage, ensuring the right people and agents have secure access to the right resources at all times.

🎯 The Role

We're hiring a Staff Engineer to join JumpCloud's Cloud Platform organization, with a focus on observability and FinOps. You'll own the questions that matter most as we scale toward 99.99% availability: can we see what's happening across the platform, how fast do we recover when something breaks, can we survive a regional outage, and are we spending enough to run it all? This is a hands-on staff role. You'll set the technical direction for observability, incident management, disaster recovery, and cloud cost, write the code and AI-driven automation that make it real, and work closely with engineering, customer support, finance, and leadership.

✅ Key Responsibilities

• Set the technical direction for observability across JumpCloud's cloud platform: metrics, logs, traces, and events, on AWS and GCP.
• Build and run our observability stack (Datadog, Prometheus, Grafana, OpenTelemetry), including standard instrumentation libraries and collectors that teams adopt by default.
• Define SLIs, SLOs, and error budgets with service owners, and build the dashboards and burn-rate alerts that hold us to a 99.99% SLA.
• Cut alert noise. Make sure every page is actionable, routed to the right owner, and backed by a runbook.
• Shorten detection and recovery times (MTTD and MTTR) by improving tracing, correlation, and incident tooling.
• Manage observability cost itself: cardinality, log volume, sampling, and retention, so visibility grows without the bill growing with it.
• Own cloud cost visibility: tagging standards, cost allocation by team and service, and showback reports that engineers actually read.
• Find and deliver savings through right-sizing, autoscaling, spot capacity, storage tiering, idle-resource cleanup, and data-transfer reduction.
• Shape our commitment strategy (Savings Plans, Reserved Instances, committed-use discounts) with finance, based on real usage data.
• Build automation and guardrails, such as budget alerts, anomaly detection, and policy-as-code checks, that catch waste before it ships.
• Define unit economics, like cost per customer or per device, and make cost a normal input to design reviews.
• Partner with finance on forecasting and budgeting, and explain cloud spend clearly to leadership.
• Own the incident management process end to end: severity levels, on-call rotations, escalation paths, communication, and the tooling behind them.
• Lead major incidents as incident commander or senior escalation point, and keep customers and leadership informed.
• Run root cause analysis (RCA) for significant incidents, and drive the follow-up actions to completion so issues don't repeat.
• Build AI agents that correlate alerts, logs, traces, and recent changes to find the likely root cause automatically.
• Build self-healing automation and AI agents that detect and fix known issues before they escalate or reach customers, with safe guardrails and human approval where it matters.
• Measure and improve incident health over time: MTTD, MTTR, repeat incidents, and on-call load.
• Own JumpCloud's business continuity (BCP) and disaster recovery (DR) strategy for the cloud platform.
• Define RTO and RPO targets with product and leadership, and design the architecture to meet them.
• Design and build the DR site and recovery environment across AWS and GCP, including data replication, backups, failover, and failback.
• Plan and run regular DR tests and failover drills, document the results, and close the gaps they reveal.
• Keep DR runbooks, recovery automation, and BCP plans current, and support audit and customer requests for evidence.
• Write production-quality Go or Python for tooling, exporters, data pipelines, and automation.
• Work closely with customer support teams: turn support tickets and escalations into monitoring, alerts, and fixes, and give support the visibility they need to answer customers quickly.
• Partner with product engineering teams on reliability, recoverability, and cost-aware design.
• Write design docs, review architecture across engineering, and mentor engineers on observability and cost-aware design.

📌 Required Qualifications

• 10+ years of software engineering experience, with at least 4 years in platform, SRE, or infrastructure roles running 24/7 SaaS systems at scale.
• Observability depth: You've designed and run observability at scale with Datadog, Prometheus, Grafana, or OpenTelemetry. You know the trade-offs between different approaches and tools.

⭐ Desirable Experience

• Experience with cloud cost management tools and practices (FinOps).
• Experience with incident management and disaster recovery planning.
• Experience with AI-driven automation and self-healing systems.
• Experience with AWS and GCP cloud platforms.
• Experience with Go or Python programming languages.

🎁 Benefits

Competitive salary and benefits package.

🛂 Visa & Eligibility

No visa sponsorship or work authorization information provided.