Software Engineer, Identity InfrastructureActive$230K–$325K

The opportunity

The Identity Infrastructure Engineering team builds the identity and access systems that OpenAI’s researchers, engineers, and internal teams rely on to protect critical systems and data.

What you'll do

  • Design and implement secure access proxies, gateways, and credential brokers: that provide narrowly scoped, auditable access to infrastructure and internal services while reducing standing privileges..

  • Integrate identity and access policy across clients, proxies, and target: systems so approved permissions take effect promptly and access expires or is revoked when required. Ensure correct behavior when policy is stale or sessions remain active.

  • Build observability that explains the end-to-end access path: latency, errors, saturation, authorization decisions, and identity attribution, without leaking credentials.

  • Engineer safe multi-region rollouts, canaries, rollback, failover, and: recovery. Validate changes with realistic test environments, load tests, and failure testing.

  • Keep core access services reliable, performant, and maintainable. Own: production support, maintenance, upgrades, and incident recovery; ship durable fixes that reduce recurring failures, alert noise, and manual work.

  • Make secure access easy to adopt through reusable APIs, client tooling,: diagnostics, and self-service workflows. Lead migrations that preserve critical workflows, with tested rollback and recovery paths and clear ownership across Infrastructure, Security, and SRE.

What they're looking for

  • Have built and operated production backend, proxy, networking, or: infrastructure services with demanding scale or availability requirements.
  • Have practical networking depth and can reason about HTTP, TCP, TLS, DNS,: routing, and load balancing across real request paths.
  • Can explain how you handled performance bottlenecks, partial failures,: multi-region deployment, or a difficult production change in a system you personally built.
  • Understand authentication, authorization, least privilege, trust boundaries,: credential handling, and the consequences of an access-control failure.