Skip to main content

OpenAI

Software Engineer, Productivity - Model Performance

San Francisco$230k–$385kfulltimemidAdded 1 month ago

About this role

Join OpenAI's Model Performance team as a Software Engineer focused on developer productivity. You'll design and improve CI/CD pipelines, testing workflows, and infrastructure tooling to help engineers work faster and more reliably on large-scale model training and inference systems.

What you'll do

  • Improve development workflows and reduce friction in testing, debugging, and deployment processes
  • Design and maintain CI/CD, release, validation, and testing pipelines
  • Build developer tools that enhance reliability, iteration speed, and engineering confidence
  • Partner with engineers to identify and address workflow bottlenecks
  • Contribute to performance-critical infrastructure supporting training and inference systems
  • Enhance developer experience for Python-heavy codebases and performance-oriented infrastructure

What they're looking for

  • CI/CD systems and pipelines
  • Developer infrastructure and tooling
  • Python programming
  • Test automation and infrastructure
  • Build and release workflows
  • PyTorch ecosystem (highly relevant)
  • C++ or Rust (nice-to-have)
  • Large-scale system design
Apply with Autofill

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 OpenAI

Likely interview questions

  • Walk us through a time you identified and fixed a systemic bottleneck in a CI/CD pipeline or testing workflow. What was the impact?
  • How would you approach designing a testing infrastructure to support a large-scale, performance-critical codebase? What tradeoffs would you consider?