The opportunity
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.
What you'll do
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.
What they're looking for
- 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.
- 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.
