OpenAI·Software Engineer·Onsite - System Design / Architecture
Jun 2026
System design round at OpenAI for a software engineer role, focused almost entirely on building a multi-tenant online IDE. The question was deep and wide, covering isolation, quotas, secrets, cold-start performance, and editor architecture. Left feeling like I only scratched the surface on half the topics.
- Design a multi-tenant online IDE where users can write and execute code in the browser. How do you isolate compute, file systems, and network between tenants, and how do you enforce per-tenant resource quotas to prevent noisy-neighbor problems?
- How would you handle per-tenant secrets and configuration in this kind of platform, where each org might have different environment variables, credentials, or runtime configs?
- How do you scale the platform to support thousands of concurrent tenants while keeping sandbox cold-start times low?
- Walk through the editor-side architecture at a high level. How does the language server protocol integration work, how do you sync files, and how do you stream terminal output back to the browser?
“This is where I spent most of the time and also where I fumbled most visibly.” The rest of the author's notes on Software Engineer interview at OpenAI, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.
View Post