Skip to main content

OpenAI

Software Engineer, Safety Engineering

San Francisco (Remote)$185k–$385kfulltimemidAdded today

About this role

Join OpenAI's Safety Engineering team to build full-stack internal tools that improve model safety and reliability. You'll work at the intersection of product engineering, data, and AI—partnering with researchers and policy teams to create scalable systems for identifying and addressing safety issues in production models.

What you'll do

  • Develop end-to-end internal tools focused on model safety, particularly for vulnerable-user protections like mental health
  • Partner with Safety Systems researchers and policy creators to translate workflows into product solutions
  • Build full-stack experiences for core safety workflows including data labeling, failure case analysis, and insight surfacing
  • Optimize applications for usability, speed, and scale to accelerate safety issue resolution
  • Migrate successful internal safety workflows into external-facing products for developers

What they're looking for

  • JavaScript and React
  • Full-stack web development
  • Backend programming (Python preferred)
  • Relational databases (Postgres/MySQL)
  • Product-driven development mindset
  • Cross-functional collaboration with researchers
  • AI/ML domain interest
  • Iterative, fast-moving environment experience
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

  • Describe a time you built an internal tool that significantly improved team velocity—what made it successful?
  • How have you approached understanding domain-specific workflows when building products for specialized teams?