OpenAI
Software Engineer, Product Velocity
About this role
Join OpenAI's ChatGPT Velocity team as an experienced infrastructure engineer to optimize the entire developer and deployment pipeline for ChatGPT services. You'll reduce friction across local development, build systems, CI, and production, turning developer pain into measurable, durable systems improvements.
What you'll do
- Reduce local development startup and iteration latency through optimization and tooling improvements
- Improve Bazel and build system performance including caching, reproducibility, and observability
- Enhance CI reliability and merge throughput by reducing flaky tests and unrelated failures
- Build automation agents to help PRs progress through rebasing, conflict resolution, and CI triage
- Make deploy pipelines more self-healing and reduce manual intervention requirements
- Establish metrics for impact measurement like commit-to-prod latency and developer-reported pain
What they're looking for
- Large-scale developer infrastructure and build systems
- CI/CD pipeline design and optimization
- Bazel, Buildkite, Kubernetes, or equivalent systems
- Distributed systems debugging and troubleshooting
- Python or TypeScript backend development
- Production reliability and observability practices
- Cross-team communication and stakeholder management
- Monorepo tooling and workflows
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
OpenAI
OpenAI builds AI infrastructure and products, including large-scale data center campuses for AI computing and generative AI applications for enterprise customers. The company is hiring civil engineers, project engineers, electrical design engineers, data center R&D engineers, and AI deployment engineers to expand its infrastructure capabilities and help customers deploy AI solutions.
View all jobs at OpenAILikely interview questions
- Tell us about a time you significantly reduced build times or CI latency in a large monorepo—what was the bottleneck and how did you measure success?
- How would you approach diagnosing a flaky test in a complex distributed system, and what strategies have you used to prevent recurring failures?