Staff Software Engineer, Compute (Temporal Cloud)
United States (Remote)
$170k–$274k a yearRemoteLead & above
Job details
- United States (Remote)
- Remote
- $170k–$274k a year (posted by the company)
- Full-time · Lead & above
- Engineering
- Posted 11 days ago
Sponsorship history
Past filings by Temporal Technologies in public government data. Not a promise of sponsorship.
- Filed 6 H-1B LCAs in FY2025
Full job description
Role Summary
Temporal powers durable execution for the world’s most demanding AI and enterprise systems. The Compute team at Temporal makes that durability feel effortless by building the managed compute primitives that run workers and other execution systems across Temporal Cloud.
We’re solving a hard platform problem: make compute transparent, elastic, safe-by-default, observable, and multi-cloud — without turning customers into infrastructure operators. We build platform primitives that span a variety of execution environments (e.g., serverless-style runtimes, containerized fleets, and customer-controlled deployments). Our work sits at the intersection of control plane + data plane: scaling decisions, isolation boundaries, multi-tenant safety, and production-grade observability. If you’ve built autoscaling systems, multi-tenant platforms, or cloud infrastructure, you’ll find a lot to love here.
See the "Compute team" link to read more --> Compute team
What You'll Do
Invent
- Create new managed compute primitives that feel first-class in Temporal Cloud: crisp abstractions, clean APIs, and an extension story across compute providers.
- Design self-optimizing autoscaling systems (signals, backstops, debouncing, guardrails) that scale worker fleets safely and predictably.
- Define the Open Source Server ↔ Cloud boundary for compute capabilities, keeping the architecture cohesive and maintainable.
Own
- Architect, build, and operate services on the hot path of task execution where performance and correctness are customer-visible.
- Deliver real-world cloud integrations (e.g., customer-account execution): IAM boundaries, secure credentials handling, networking constraints, quotas, and failure modes.
- Make operability a feature: SLOs, tracing/metrics, load and failure testing, incident reviews, and continuous hardening.
- Ship end-to-end: API design, rollout strategy, backwards compatibility, and long-term maintenance.
Teach
- Raise the bar through design docs, strong reviews, pragmatic technical leadership, and mentorship.
- Lead through influence across teams (Server, SDKs, Security, Control Plane) to land coherent platform changes.
