← Back to Directory

OpenAI interview notes, page 22 of 67

Mid-sized

Most of these OpenAI write-ups come from Software Engineers (460), then Machine Learning Engineers (137) and Backend Engineers (23). The most reported rounds are the technical phone screen (335), the system design round (229), the onsite coding round (32) and the behavioral / leadership round (22).

667 interview notes · updated Jul 2026

OpenAI·Machine Learning Engineer·Technical Phone Screen

May 2026
OpenAI ML Engineer round focused entirely on gradient-based optimization and PyTorch autograd. Pretty deep technically, more math-on-the-board than I expected for a coding round.
  • Derive backpropagation by hand for a small network with one or two hidden layers using sigmoid or ReLU activations, a softmax output, and cross-entropy loss. Walk through the forward pass, then apply the chain rule backward to compute the weight and bias gradients at each layer.
  • Implement the forward pass and a manual backward pass in NumPy for a small neural network, then verify your computed gradients match what PyTorch autograd produces.
  • Explain the correct usage of PyTorch autograd: when to call backward(), what happens to gradients across training iterations without zero_grad(), and what detach() and torch.no_grad() are actually doing.
  • Identify and explain common PyTorch autograd bugs: forgetting to zero gradients, performing in-place operations on leaf tensors, and trying to call backward on a computation graph that has already been freed.
  • How does gradient checking via finite differences work, and when would you use it?
  • Why do vanishing and exploding gradients happen, and how do weight initialization strategies like Xavier or He initialization help address them?
  • What problems do BatchNorm and LayerNorm solve during training, and how do they interact with the gradient flow?

“This took way longer than I wanted.”

View Post

OpenAI·Software Engineer·Onsite - System Design / Architecture

May 2026
OpenAI system design round for a software engineer role. The whole thing centered on designing a video generation system similar to Sora, and they pushed hard on failure modes and flaky worker behavior rather than the happy path.
  • Design a large-scale AI video generation system similar to Sora. How would you architect it end to end, and what happens when workers in your processing pipeline become unstable or fail?

“The high level design part felt manageable but they very quickly steered toward the ugly stuff.”

View Post

OpenAI·Software Engineer·Technical Phone Screen

May 2026
OpenAI SWE interview that went deep on transformer internals, specifically building a decoder block with KV caching for autoregressive generation. Pretty technical and unforgiving if you haven't actually implemented one before.
  • Implement a transformer decoder block that uses a KV cache to speed up autoregressive generation. Walk through how shapes evolve per decoding step, what the memory cost looks like, and how you'd verify correctness against a naive full recompute.

“This one has a lot of surface area and I didn't pace myself well.”

View Post

OpenAI·Software Engineer·Technical Phone Screen

May 2026
OpenAI SWE interview with a PyTorch debugging and implementation problem. Pretty hands-on, they gave you a spec and expected working code plus the ability to spot classic training loop bugs.
  • Implement a 2-layer MLP in PyTorch for binary classification, write a full training loop, and fix any bugs in provided code (e.g. missing zero_grad, shape mismatches, wrong loss function usage).

“This was more involved than I expected for a single question.”

View Post

OpenAI·Machine Learning Engineer·Technical Phone Screen

May 2026
OpenAI ML engineer interview that was basically a numpy coding session. You get handed an ML puzzle and have to implement it from scratch, so if your linear algebra is rusty you're going to have a bad time.
  • Implement a linear (dense) layer in numpy that handles a batched input, including the matrix multiply and bias addition. Be precise about shapes at every step.
  • How would you extend the linear layer implementation to support other layer types, such as activation functions or attention?
  • Discuss numerical stability concerns in your implementation. Where could things go wrong and how would you address it?

“This is the core of the whole interview.”

View Post

OpenAI·Software Engineer·Onsite - Coding / Algorithms

May 2026
OpenAI software engineer coding round with a multi-part problem. Got through most of it but ran out of time before fully finishing the last part I attempted, which stung a bit.
  • Solve the 'plant infection' multi-part coding problem, which progressively builds in complexity across several parts.

“Got through parts 1-3 fine and was close on part 4, but time ran out before I could debug the failing test cases.”

View Post

OpenAI·Software Engineer·Onsite - System Design / Architecture

May 2026
Went through a system design round at OpenAI for a software engineer role and got completely blindsided by the topic. No relevant work background, prep had faded, and I left pretty sure I tanked it.
  • Design a video streaming service from scratch.

“I had nothing.”

View Post

OpenAI·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at OpenAI for a software engineering role. The whole session was basically one big deep-dive into video storage infrastructure, covering everything from upload to CDN delivery. Dense and exhausting.
  • Design the storage system for a large-scale video publishing platform like YouTube, covering the full lifecycle from upload to delivery.

“This was the whole interview basically.”

View Post

OpenAI·Software Engineer·Technical Phone Screen

May 2026
OpenAI coding round with a simulation problem that kept getting harder. The base infection spread question was manageable but then they added recovery and immunity mechanics and I had to rethink basically everything mid-interview.
  • Given a grid where infected cells spread to all 8 neighbors each day, and each infected cell recovers and becomes permanently immune after exactly D days, simulate the process and return how many days until the grid reaches equilibrium.

“The first version of this problem felt fine, standard BFS-style spread.”

View Post

OpenAI·Machine Learning Engineer·Onsite - Behavioral / Leadership

May 2026
Interviewed for an ML Engineer role at OpenAI. The round was heavily focused on how you perform under pressure, not just whether you can solve the problem but how you communicate while doing it. Left feeling like I probably over-explained the technical bits and under-explained the tradeoffs.
  • Tell me about a time you had to ship a technical solution under serious time pressure. How did you structure your work, communicate the tradeoffs you were making, and still make sure the output was actually correct?
  • If you had to present that work in a 5 to 10 minute walkthrough, what would you prioritize showing, how would you handle tough follow-up questions, and what would you have done differently if you'd had more time?

“This is where I think I lost some points.”

View Post