OpenAI Software Engineer Interview Experience — Ran Out of Time on the Coding Part, Rejected

OpenAI·Software Engineer·Jul 2026
Technical ScreenRejectedmedium

I only prepared for less than three weeks in practice and then just went in. It really was too rushed.

coding: rectangle id + count_at + remove + O(1) heavy read for count_at and O(U+1) for add/remove operations;
I didn't have time to finish part 3 at the end, which is extremely frustrating.

SD: online typing game
I went through the standard flow and covered all the read and write paths. I made some changes according to the scale and handled the infra edge cases.
I talked about some trade-offs of stateful design, latency-critical design, fairness, and the details of service recovery.
I honestly think there was nothing seriously wrong with the design. If I got rejected, it was probably because of the really awful coding.

A few thoughts on preparing for OAI:
You should leave yourself about a month to go through the question bank. The h2h question bank is now suffocatingly big. Not all of it needs to be written out once, but for your own peace of mind, starting early helps your mindset. Old questions won't show up, and I noticed that new questions roll out every month. Also, the coding has a very high speed requirement, so if you heavily rely on LLM coding day to day, pay attention to your coding speed.

Published

Curated and edited by PracHub

Practice the questions from this interview

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
OpenAI
Role
Software Engineer
Rounds
Technical Screen
Outcome
Rejected
Difficulty
medium
Interview date
Jul 2026
Questions from this interview
2 questions

Related interview experiences

Explore more interview rounds, questions, and outcomes.

Browse interview experiences