Software Engineer, Codex Cloud

OpenAI OpenAI · AI Frontier · San Francisco, CA · Applied AI

Software Engineer role focused on building the cloud-based runtime and orchestration layer for the Codex AI agent, enabling it to securely and reliably execute tasks, interact with codebases, and operate at scale for enterprise customers. This involves designing and implementing core platform capabilities, including container orchestration, sandboxed environments, identity and governance systems, and observability, to support agentic experiences.

What you'd actually do

  1. Shape the evolution of Codex itself by identifying how teams actually use (and break) AI-powered software engineering, and driving changes across product, infrastructure, and model behavior to make Codex a truly reliable teammate for organizations.
  2. Design customer-facing (across consumer and enterprise segments) software engineering experiences end-to-end to automate and empower engineers to safely build and deliver software to their customers.
  3. Build the core team and enterprise primitives that make Codex usable at scale including container orchestration, virtual machine provisioning/configuration, execution sandboxes, shared block storage, RBAC, admin and audit surfaces, usage, rate limits and pricing controls, managed configuration and constraints, and analytics that give teams and operators deep visibility into how Codex is being used.
  4. Design and own secure, observable, full-stack systems that power Codex across web, IDEs, CLI, and CI/CD, integrating with enterprise identity and governance systems (SSO/SAML/OIDC, SCIM, policy enforcement) and building data-access patterns that are performant, compliant, and trustworthy.
  5. Lead real-world deployments and launches by working directly with customers and GTM to roll Codex out across teams, using live usage and operational signals to rapidly iterate and turn messy, real-world feedback into scalable product and platform improvements.

Skills

Required

  • strong software engineering fundamentals
  • experience turning ideas into production-grade large-scale distributed systems
  • balancing speed, performance, costs, and user experience
  • experience with orchestration of scaled containerization and/or virtualization systems (e.g. Kubernetes, OCI)
  • proficient in one or more backend languages (e.g. Python, Go, Rust)
  • concurrency/distributed systems concepts
  • focus on reliability, observability, and security
  • building cross-cutting platform capabilities
  • experience with team/enterprise foundations such as identity and access (SAML/OIDC), SCIM, RBAC, audit/compliance logging, policy enforcement, and data governance controls
  • built developer tools and workflows (CLI/IDE/SDK), automation systems (triggers/scheduling), or integration platforms
  • working directly with users/customers (or alongside GTM/solutions teams)
  • translate messy, diverse requirements into opinionated implementations that scale
  • 0 -> 1 environments
  • navigate ambiguity
  • crisp product thinking to technical trade-offs

Nice to have

  • using AI-powered/agentic software development tools and are familiar with their strengths/weaknesses

What the JD emphasized

  • AI software engineer
  • agent harness
  • runtime/orchestration layer
  • secure, sandboxed environments
  • distributed systems substrate
  • large numbers of supervised AI agents
  • safely, reliably, and at scale interact with the world’s software
  • customer-facing software engineering experiences
  • container orchestration
  • virtual machine provisioning/configuration
  • execution sandboxes
  • RBAC
  • admin and audit surfaces
  • usage, rate limits and pricing controls
  • managed configuration and constraints
  • analytics
  • secure, observable, full-stack systems
  • enterprise identity and governance systems
  • SSO/SAML/OIDC
  • SCIM
  • policy enforcement
  • data-access patterns
  • performant, compliant, and trustworthy
  • real-world deployments and launches
  • working directly with customers
  • GTM
  • live usage and operational signals
  • scalable product and platform improvements
  • AI-powered/agentic software development tools
  • orchestration of scaled containerization and/or virtualization systems
  • Kubernetes
  • OCI
  • backend languages (e.g. Python, Go, Rust)
  • concurrency/distributed systems concepts
  • reliability, observability, and security
  • cross-cutting platform capabilities
  • product velocity
  • team/enterprise foundations
  • identity and access (SAML/OIDC)
  • SCIM
  • RBAC
  • audit/compliance logging
  • policy enforcement
  • data governance controls
  • developer tools and workflows (CLI/IDE/SDK)
  • automation systems (triggers/scheduling)
  • integration platforms
  • working directly with users/customers
  • GTM/solutions teams
  • 0 -> 1 environments
  • navigate ambiguity
  • crisp product thinking
  • technical trade-offs

Other signals

  • AI software engineer
  • agent harness
  • runtime/orchestration layer
  • secure, sandboxed environments
  • distributed systems substrate
  • large numbers of supervised AI agents
  • safely, reliably, and at scale interact with the world’s software
  • customer-facing software engineering experiences
  • container orchestration
  • virtual machine provisioning/configuration
  • execution sandboxes
  • RBAC
  • admin and audit surfaces
  • usage, rate limits and pricing controls
  • managed configuration and constraints
  • analytics
  • secure, observable, full-stack systems
  • enterprise identity and governance systems
  • SSO/SAML/OIDC
  • SCIM
  • policy enforcement
  • data-access patterns
  • performant, compliant, and trustworthy
  • real-world deployments and launches
  • working directly with customers
  • GTM
  • live usage and operational signals
  • scalable product and platform improvements
  • AI-powered/agentic software development tools
  • orchestration of scaled containerization and/or virtualization systems
  • Kubernetes
  • OCI
  • backend languages (e.g. Python, Go, Rust)
  • concurrency/distributed systems concepts
  • reliability, observability, and security
  • cross-cutting platform capabilities
  • product velocity
  • team/enterprise foundations
  • identity and access (SAML/OIDC)
  • SCIM
  • RBAC
  • audit/compliance logging
  • policy enforcement
  • data governance controls
  • developer tools and workflows (CLI/IDE/SDK)
  • automation systems (triggers/scheduling)
  • integration platforms
  • working directly with users/customers
  • GTM/solutions teams
  • 0 -> 1 environments
  • navigate ambiguity
  • crisp product thinking
  • technical trade-offs