Skip to main content

OpenAI

Full Stack Software Engineer, OpenAI Edu

San Francisco (Remote)$230k–$385kfulltimemidAdded 1 month ago

About this role

Join OpenAI's Education team as a Full Stack Engineer to build AI-powered learning products for schools, universities, and learners worldwide. You'll own projects end-to-end across the stack, working with learning scientists and cross-functional partners to create education experiences grounded in real learning outcomes.

What you'll do

  • Build and ship full-stack product experiences for OpenAI's education offerings
  • Own projects from ideation and technical design through launch and iteration
  • Collaborate with learning scientists to translate educational goals into product decisions
  • Partner with design, data, and cross-functional teams on user experience quality
  • Define engineering foundations, patterns, and technical direction for the education team
  • Contribute to both consumer and B2B education product experiences

What they're looking for

  • TypeScript and React
  • Backend languages (Python, Go, Rust, or similar)
  • Distributed systems concepts
  • Relational databases (Postgres/MySQL)
  • Full-stack web development
  • Product-driven development mindset
  • Production reliability and performance optimization
  • Interest in AI/ML
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 full-stack project you've owned end-to-end, from ideation through launch. What was your decision-making process, and how did you handle trade-offs between frontend and backend?
  • Tell us about a time you worked with non-technical stakeholders (like product, design, or domain experts) to translate requirements into technical solutions. How did you navigate conflicting priorities?