Real, anonymous reports from people who interviewed for Software Engineer at Okx, newest first and distilled into what to expect across the loop.
My first round was a LeetCode-style coding question, and it felt pretty straightforward at the start. I got a Combination Sum problem, and the interviewer was friendly and easy to talk to, which lowered the pressure. The whole thing was focused on fundamentals of the coding approach rather than heavy theory.
The process I went through didn’t look like a traditional written test at all. Instead, it was structured as a series of conversational discussions, where the questions were mainly about things I’d done before and how I handled different situations.
The interview process typically begins with an HR screening that assesses background and fit, but experiences vary widely in terms of organization and clarity, with some candidates feeling it was transactional rather than evaluative.
Candidates can expect multiple technical rounds focused on coding, often using LeetCode-style problems that emphasize fundamental skills in languages like Java and concepts such as data structures and algorithms, with a generally supportive interview atmosphere.
In addition to coding, there are rounds dedicated to system design and practical problem-solving, where candidates discuss concepts like concurrency, operating systems, and low-latency systems, often requiring a solid understanding of real-world applications.
Behavioral interviews focus on past experiences and decision-making processes, with some candidates noting that these discussions can carry significant weight in the evaluation, often probing for alignment with company values and culture.
The overall interview process can vary in structure and communication quality, with some candidates experiencing smooth, well-coordinated flows while others faced chaotic scheduling and unclear expectations, impacting their confidence in the process.
Candidates often leave the process without an offer, reflecting on the challenges faced, including the need for consistent performance across multiple rounds and the sometimes unclear or shifting expectations regarding role requirements.
