Design Slack.

"Overall, I’d rate the process as smooth and structured, with four rounds in total: two technical rounds focused on SQL and DSA, one system/design round, and one hiring manager discussion. The expectations were clear in advance, interviewers were punctual, and the questions were well aligned with the role. What went well was the depth and relevance of the SQL and design problems, which gave me a fair chance to showcase my experience with data pipelines and large-scale systems. What could have been better was more clarity on the evaluation criteria and faster post-interview communication, as the waiting period between rounds felt a bit long"

"Interview was smooth and relatively easy compared to other processes, interviewer was nice and helpful enough."

"I got sourced by a contractor first and then handed off to an actual OpenAI recruiter, which was a little unusual but pretty smooth. The process was a recruiter screen, then a first technical screen with one system design and one coding round, then a virtual onsite with only two more technicals plus behavioral, cross-functional behavioral, and a project deep dive. What stood out most was that the coding wasn't really LeetCode-shaped even though that was the prep guidance I got. The whole loop felt much more practical and scale-heavy than expected, and the project deep dive was easily the most probing part because they kept asking what I actually did and why. My main takeaway was that they want strong generalist problem solvers more than people who just memorize interview patterns."