Software Development · San Francisco, CA

Hybrid Full-time

Software Engineer, Product Velocity

OpenAI · San Francisco, CA · Posted Sep 28, 2026

This posting comes from OpenAI. Confirm the details on their site before applying.

Overview

The ChatGPT Velocity team owns the health of the end-to-end developer and deploy loop for ChatGPT-facing services. Our mission is to help ChatGPT engineers ship confidently with a fast, lightweight development cycle and a trusted path to production. ChatGPT development depends on a long chain: local environments, Bazel builds, CI, tests, merges, release candidates, deploys, synthetics, alerts, and production health.

Responsibilities

  • Reduce local development startup and iteration latency for ChatGPT engineers
  • Improve Bazel and build performance for local machines, devboxes, and CI, including cache effectiveness, reproducibility, disk usage, remote cache behavior, and observability into invalidations.
  • Improve CI reliability and merge throughput by reducing unrelated failures, tail latency, flaky or mis-owned tests, quarantine friction, and repeated manual reruns.
  • Build agents that help PRs make forward progress: rebasing, conflict resolution, CI triage, safe reruns, owner routing, and clear identification of external blockers.
  • Make deploy pipelines more self-healing, especially when transient alerts, known-bad clusters, recovered synthetics, stale RCs, or noisy gates should not require human babysitting.
  • Improve deploy observability so engineers can quickly tell where a change is, what is blocking it, whether the signal is trustworthy, and who owns the next action.
  • Establish lightweight metrics for before-and-after impact, such as commit-to-prod latency, deploy-window throughput, CI tail latency, local bootup time, failure rates, manual interventions, false-positive gates, and developer-reported pain.

Requirements

  • Have strong experience with large-scale developer infrastructure, build systems, CI/CD, deployment systems, or production reliability.
  • Can debug across local machines, devboxes, remote caches, monorepos, service dependencies, auth systems, and distributed deploy pipelines.
  • Are comfortable with systems like Bazel, Buildkite, Kubernetes, Temporal, Python/TypeScript services, GitHub workflows, and large monorepo tooling, or can ramp quickly on equivalents.
  • Think in product loops as much as systems loops: you care whether developers can understand and trust the workflow, not just whether a subsystem is technically healthy.
  • Know how to replace repeated manual intervention with policy-backed automation while preserving production safety.
  • Communicate well across teams and can turn ambiguous "this is slow/broken/flaky" reports into crisp owners, hypotheses, metrics, and shipped fixes.
  • Prefer practical measurement over vibes, while still knowing that developer frustration is often the first signal of a real systems problem.
  • Are energized by high-leverage work where a small improvement can save hundreds of engineering hours.

Preferred qualifications

  • Experience improving developer experience in a very large monorepo.
  • Experience with remote execution, remote caching, hermetic builds, or cache reproducibility.
  • Experience designing CI quarantine, test ownership, merge queue, or auto-revert systems.
  • Experience with progressive delivery, canary/preview/stable deploy pipelines, synthetics, alert quality, and deploy-manager style workflows.
  • Experience building agent-assisted developer workflows, such as automated PR babysitting, CI triage, or conflict resolution.
  • Familiarity with security and access-control constraints around secrets, internal auth, VPN/exit-node networking, and local development.

Great fits start here.

Whether you're looking for your next role or your next team member, give people and possibilities a place to meet.