OpenAI·Mobile Engineer·Onsite - System Design / Architecture
Jun 2026
System design round at OpenAI for a mobile engineer role. The question was one big sprawling prompt about quota handling for a GPT chat product, which sounds focused until you realize it touches API contracts, client UX, content-type billing, and edge cases all at once.
- Design the full error-handling flow for when a free-tier user hits their message quota on a GPT chat service. This includes the API contract (HTTP status, error codes, retry-after headers, upgrade hints), how the server tells quota exhaustion apart from rate limiting, idempotency, client-side UI behavior, how different content types (text, image, voice, file) consume quota differently, and edge cases like mid-stream responses getting cut off.
“This felt like four questions stapled together and I kind of panicked at the scope.” The rest of the author's notes on Mobile 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