← OKX Interview Insights

OKX·Software Engineer·Technical Phone Screen·Senior

Senior
Apr 2026

Summary

Second round at OKX, and they wanted a full project deep-dive on something different from what I'd covered before. The technical follow-ups were real, not just surface-level nods.

Questions Asked (1)

Q1

Walk us through a past project in depth: what was the problem, what design decisions did you make, what was your specific contribution, what challenges came up, and what was the actual impact?

System DesignTechnical Trade-offsProduct Strategy
Author's notes

This was a second project they asked about, so I couldn't just recycle what I'd said in the previous round.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a project that aligns with Okx's domain (e.g., high-frequency trading, matching engine, or scalable infrastructure) and structure your answer using a clear narrative arc: context, problem, your role, design decisions with trade-offs, challenges, and quantified impact. Emphasize the 'why' behind your decisions and how you measured success, while keeping the story concise and focused on your individual contributions.

Pro tip: Quantify impact with metrics that matter to Okx, such as latency reduction, throughput increase, or cost savings, and explicitly connect your design choices to business outcomes like improved user experience or revenue.

1. Set the Context and Problem

Briefly describe the project, the team, and the specific problem you were solving. Explain why it mattered to the business or users, and what constraints existed (e.g., time, scale, regulatory).

2. Outline Design Decisions and Trade-offs

Walk through the key architectural or technical choices you made, alternatives you considered, and why you chose your approach. Highlight trade-offs in performance, scalability, maintainability, or cost.

3. Detail Your Specific Contribution

Clearly state your role and what you personally did—whether it was designing a component, writing critical code, leading a team, or making a pivotal decision. Avoid vague 'we' statements.

4. Discuss Challenges and How You Overcame Them

Describe 1-2 significant obstacles (technical, organizational, or external) and the actions you took to resolve them. Show problem-solving and adaptability.

5. Quantify Impact and Reflect on Learnings

Share measurable results (e.g., reduced latency by X%, increased throughput by Y%) and tie them to business goals. Briefly mention what you learned and how it applies to future work.

Key Points to Mention

  • Specific technologies and architectures used (e.g., microservices, Kafka, Redis, Kubernetes) and why they were appropriate.
  • Trade-offs made between consistency, availability, and partition tolerance (CAP theorem) or latency vs. throughput.
  • Your individual ownership and leadership, such as driving a design review or mentoring teammates.
  • Challenges like scaling to millions of users, handling peak loads, or debugging production issues.
  • Quantified impact: e.g., reduced API response time from 200ms to 50ms, saved $X in infrastructure costs, increased conversion by Y%.
  • Alignment with Okx's values or tech stack, such as experience with high-performance systems or blockchain technologies.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.