OpenAI Machine Learning Engineer interview questions

92 Machine Learning Engineers have shared notes from their OpenAI interviews, with the questions they were asked in each round. That is 22% of the 413 OpenAI interview notes on Screna AI.

92 Machine Learning Engineer interview notes

OpenAI·Machine Learning Engineer·Onsite - System Design / Architecture

Jun 2026
Did a system design round for an ML Engineer role at OpenAI. The focus was on version control for systems, which I wasn't expecting to be the whole thing.
  • How would you design a version control system for machine learning models and related system components?

“I kind of froze for a second because I expected something more ML-specific, like feature stores or training pipelines.”

View Post

OpenAI·Machine Learning Engineer·Onsite - System Design / Architecture

Jun 2026
OpenAI MLE interview that centered entirely on a system design coding problem around credit tracking. The problem sounds deceptively simple but there's a lot of nuance in the data structure choice and the expiry logic that they really want you to think through out loud.
  • Design and implement an in-memory GPU credit tracking system with three operations: granting credits to a user with an expiration timestamp, consuming credits while auto-expiring stale ones (oldest-expiring first), and querying a user's non-expired balance at a given timestamp.
  • What are the trade-offs between using a min-heap, a plain Python list, and a sorted container for the earliest-expiry lookup, and what is the time complexity of each operation under each approach?

“The core of the whole interview.”

View Post

OpenAI·Machine Learning Engineer·Technical Phone Screen

Jun 2026
OpenAI ML engineer interview, got a pretty theoretical question about nearest neighbor search that pushed into implementation territory fast.
  • If you switched from L2 to L1 distance, how would you implement a 1-nearest-neighbor classifier using a neural network?

“Tripped me up a bit because the neural network framing felt like a weird wrapper around what's basically a distance computation problem.”

View Post

OpenAI·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Got a fairly niche ML question from what seemed like an OpenAI technical screen. Just the one question but it was the kind that made me realize I'd been thinking about entropy in a way that only works when you have all the data upfront.
  • If logits are arriving in a streaming fashion, block by block, how would you compute entropy in an online manner?

“I fumbled the start because my brain went straight to the standard entropy formula and then I had to back up and actually think about what 'online' means here.”

View Post

OpenAI·Machine Learning Engineer·Onsite - System Design / Architecture

Jun 2026
Deep-dive round at OpenAI for an MLE role, focused entirely on a past search system project. They pushed hard on embedding design choices and wanted you to actually defend your decisions, not just describe them.
  • Why would you use a hash-based representation for item IDs in a search system instead of something like a learned embedding from a language model? When is each approach actually appropriate?

“This is the kind of question that sounds straightforward until you're in it.”

View Post

OpenAI·Machine Learning Engineer·Technical Phone Screen

Jun 2026
OpenAI ML engineer round with a pretty gnarly theory question that felt like a homework problem but in real time. The whole thing was about reimplementing 1-nearest-neighbor as a pure neural net forward pass, no training allowed. Conceptually fun but I definitely fumbled the tensor dimension stuff under pressure.
  • How would you express 1-Nearest-Neighbor classification as a neural network forward pass (inference only, no training), where every operation is a linear layer followed by an activation, and the network outputs the label of the nearest training example given a query vector?

“This one wrecked me a little.”

View Post

OpenAI·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Interviewed for an ML Engineer role at OpenAI and got a grid simulation problem that was basically a beefed-up version of Rotting Oranges with two extra parameters and a whole new death mechanic. Harder than I expected for a coding round.
  • Given a grid with infected ('X'), healthy ('.'), and immune ('I') cells, simulate daily spread of infection. Add two parameters: k (the minimum number of infected neighbors that triggers severe infection) and n (days after severe infection before a plant dies). Return the number of days until the simulation stabilizes and the total count of dead plants.

“This is LC 994 but they kept bolting on rules until it barely resembled the original.”

View Post

OpenAI·Machine Learning Engineer·Technical Phone Screen

Jun 2026
OpenAI ML Engineer interview, second round was a pure coding problem focused on implementing a classical ML algorithm from scratch with strict NumPy-only constraints. Short round but the constraint made it trickier than expected.
  • Implement 1-Nearest Neighbor classification using L2 distance. No for-loops; vectorized NumPy only.

“The core algorithm is simple enough but the no-loop constraint is where people trip up.”

View Post

OpenAI·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Interviewed for an ML Engineer role at OpenAI and got a deep type inference question that felt more like a PL theory exam than anything ML-adjacent. Surprised me a bit but it was actually pretty interesting to work through.
  • Given an AST for a small toy language where nodes represent literals, variables, function calls, or composite expressions, implement a recursive function that infers the type of each expression. Your solution should handle nested expressions, type propagation through function returns, and raise clear errors on type mismatches. Also discuss how you'd extend the system to support generics and union types, and analyze the time complexity relative to AST size.

“This one took me a second to orient to.”

View Post

OpenAI·Machine Learning Engineer·Technical Phone Screen

Jun 2026
OpenAI ML Engineer interview with a noisy data / annotation quality problem. The setup was pretty open-ended and the interviewer kept peppering in conceptual questions throughout, which made it feel less like a clean coding exercise and more like a running conversation about ML fundamentals.
  • You're given a labeled dataset where annotator quality varies. First establish a baseline by training the provided model, then design and apply your own approach to clean the data and improve post-training performance.
  • What are precision, recall, and F1, and when would you prioritize one over the others?

“The open-endedness is what gets you.”

View Post