Director of Engineering, Compute
Temporal is hiring a Director of Engineering, Compute for a remote role open to applicants in United States. It pays $214k-$352k a year and Level rates it ; you can apply on Level.
Level's read on this job
- Level rates this role Builds AI ●●●●: the job is building AI systems.
- The posting lists this role as remote.
- Tools and skills the posting cites include OpenAI, Cursor and Lovable.
- Level files it as an executive role.
- Level lists 69 other open roles at Temporal.
AI in this role
Director of Engineering leading the compute platform layer that powers high-scale AI agents and LLM workloads.
Director of Engineering, Compute
Companies at the frontier of the AI revolution run on Temporal. OpenAI runs on Temporal, handling millions of requests. Cursor runs its cloud coding agents on Temporal at over 50 million actions a day across 7M+ workflows, and more than a third of the pull requests its users merge now come from those agents. Lovable, Abridge, and Hebbia build their agents on it too. In the last year alone, AI-native companies executed 1.86 trillion actions on Temporal Cloud, and the curve is still bending upwards. Backed by a recent $300M Series D at a $5B valuation, we are building the durable execution layer the agentic era depends on.
The Compute team owns the layer all of that runs on. We are looking for a Head of Engineering to lead the effort to make any aspects of Temporal's compute invisible to our customers, allowing them to focus on application layer innovation, while we handle the compute muck. This is a rare, build-the-foundation mandate: the compute substrate that the world's most demanding AI workloads will run on. We want a leader who has operated compute at planet scale, thinks in fleets, goodput, and cost-per-unit-of-compute, and pairs that with the operational rigor to run a service that frontier-AI companies bet production on.
What You'll Do
Strategic direction for Compute: Own the strategy and standards of excellence for the compute layer that the world's agents run on, across design, delivery, and operations. Build a culture of ownership, quality, and customer-first decision-making.
Technical leadership: Lead, hire, and grow a high-ownership team; roll up sleeves, ready to do deep into the trenches, by staying close to design docs and code, rather than managing from a distance. Coach engineers, level them up, and clear the friction that slows them down.
Roadmap & trajectory: Drive the arc from today's compute toward the next-generation of compute platforms. Ground prioritization in customer and design-partner feedback, and turn ambiguous, fast-moving requirements into predictable, iterative delivery.
Operational excellence: When you run frontier AI in production, reliability is the product. Own operations, run on-call and incident response, and drive blameless postmortems and the systemic fixes that prevent recurrence.
Technical depth: Guide the hard architectural decisions for large-scale, multi-tenant compute, where technical concerns cut across workload isolation and security, scheduling, fleet efficiency / utilization / goodput, and performance, while ensuring the platform is reliable and efficient for the workloads that depend on it.
Capacity, supply & economics: Own utilization, capacity and supply planning, and the cost-per-unit-of-compute and margin profile of the fleet, across CPU compute today and accelerated compute ahead.
Cross-team & customer execution: Partner with leadership, Product, SDK, UX/DX, Security, and design-partner customers to align priorities and unblock delivery. Communicate progress, tradeoffs, and risk clearly to technical and non-technical audiences alike.
What You'll Bring
Proven experience leading software engineering teams that build and operate large-scale compute platforms or fleets, with strong operational practices.
15+ years in software and/or infrastructure engineering, including 10+ years of people management and demonstrated ownership of delivery and live-site outcomes.
Deep distributed-systems and compute infrastructure depth, with the hands-on judgment to guide architecture and execution rather than from a distance.
Experience operating multi-tenant compute that other people's production workloads depend on.
Bachelor's degree in Computer Science or related field, or equivalent practical experience; advanced degree a plus.
Excellent communication skills, with the ability to partner across engineering, product, and leadership and fold customer feedback into the roadmap.
Strong leadership, coaching, and performance management; ability to grow engineers and build a healthy, accountable, high-ownership team.
Excellence in execution: planning, prioritization, and delivering iterative milestones in an ambiguous, fast-moving environment while managing unplanned work.
Fleet thinking: utilization, goodput, capacity and supply planning, and cost discipline as first-class engineering concerns.
Live-site reliability craft: on-call, incident management & response, and postmortem-driven continuous improvement.
Strong command of the building blocks of a compute platform: multi-tenant isolation and security, scheduling, and resource management.
Ability to review and raise the bar on technical artifacts (design docs, code reviews) across a distributed-systems codebase.
Nice to Have
MicroVMs and virtualization (Firecracker, gVisor, Edera) or managed-compute primitives (AWS Fargate, GCP Cloud Run, AWS Lambda), and/or Kubernetes internals.
Building serverless or hosted-compute products from 0 to 1, including the rapid-delivery-vs-durable-platform tradeoffs that come with it.
Multi-cloud delivery across AWS and GCP.
Cold-start, warm-pool, and scheduling/latency optimization for on-demand compute.
Agent sandboxes, secure execution of untrusted code, or other AI-agent infrastructure.
GPU / accelerated compute: fractional GPUs (MIG, MPS, time-slicing), GPU scheduling, training vs. inference fleets, and multi-tenant GPU isolation.
---
The ideal candidate is a strategic thinker with a hands-on approach, energized by building the compute foundation the AI era runs on. They are comfortable shaping a space that doesn't fully exist yet, obsessed with reliability when customers bet production on it, default to working backwards from customers, and balance the speed to ship 0-to-1 against the durable design a planet-scale platform demands.
Temporal Technologies is an Equal Opportunity Employer. Temporal Technologies does not discriminate on the basis of race, religion, color, sex, gender identity, sexual orientation, age, non-disqualifying physical or mental disability, national origin, veteran status, or any other basis covered by appropriate law. All employment is decided on the basis of qualifications, merit, and business need. We embrace and celebrate differences and diversity.
Temporal is committed to providing access, equal opportunity, and reasonable accommodation for individuals with disabilities in employment, its services, programs, and activities. If you need to request a reasonable accommodation, please let your Recruiter know so we can assist.
How we rate this
Director of Engineering, Compute at Temporal rates 85 out of 100 for how much of the daily work is AI. That makes it Builds AI (AI Level 4 of 4). The level is about AI in the job, not seniority.
Builds AI. The job is building AI systems.
- ●●●● Builds AI80 to 100
- ●●●○ Works on AI60 to 79
- ●●○○ Uses AI40 to 59
- ●○○○ Little AI0 to 39
Levels come from how often the tools, models and workflows of the role are named in the posting itself. Open the description and count.
Prepare for this job
Built from this posting and from similar jobs on Level.
Skills and AI tools this role asks for
Questions you could be asked
- Tell me about a project where distributed systems was part of your work. What did you do?
- Tell me about a project where compute infrastructure was part of your work. What did you do?
- Tell me about a project where engineering management was part of your work. What did you do?
- Tell me about a project where fleet management was part of your work. What did you do?
- Walk me through how you've used OpenAI in your day-to-day work.
Adapt your resume
- List these exact terms on your resume: Distributed Systems, Compute Infrastructure, Engineering Management, Fleet Management, and OpenAI. An applicant tracking system matches the wording, not the idea.
- Attach one line of real, concrete experience to at least one of them. A tool named with nothing behind it rarely survives a human read.
- Lead with what you built, trained or shipped. This role is judged on the AI system itself, not the tools around it.
Want an expert to read your CV for this job?
Free. Send your CV and the role you want next. We reply by email within 2 to 4 business days.
Get new remote software engineering jobs (Builds AI ●●●●) by email
One email a week with the new remote software engineering jobs (Builds AI ●●●●), each rated for how much AI is in the work. No recruiter spam, unsubscribe in one click.
Free. One email a week. Unsubscribe in one click.
Similar roles
Software Engineering roles that build AI, at other companies.
What kind of AI work fits you?
Answer 12 practical questions in about three minutes. Get a simple profile, the work it points to, and live roles to explore next.
Find my next step