← OKX Interview Insights

OKX·Software Engineer·Technical Phone Screen·Senior

Senior
Apr 2026

Summary

Had a technical round at OKX where the whole thing was basically one long project deep-dive. No leetcode, no trivia, just them picking apart everything I'd built.

Questions Asked (1)

Q1

Walk me through a past project end-to-end: the problem you were solving, how you designed the system or model, the technical decisions you made and why, what you personally contributed, what got hard, and what the outcome actually was.

System DesignTechnical Trade-offs
Author's notes

This took up the entire interview and I still feel like I rushed the impact section at the end.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Select a project where you owned a significant technical component and can clearly articulate the problem, your design choices, and the measurable impact. Structure your answer as a narrative that highlights the 'why' behind each decision, the challenges you overcame, and the results, while keeping it concise and focused on your personal contributions.

Pro tip: Quantify the impact with concrete metrics (e.g., latency reduction, cost savings, user growth) and be ready to discuss alternative approaches you considered and why you rejected them—this shows depth and trade-off thinking.

1. Set the Context and Problem

Briefly describe the project's background, the specific problem it addressed, and why it mattered to the business or users. Keep it to 2-3 sentences to set the stage.

2. Explain Your Design and Technical Decisions

Outline the system or model architecture you designed, focusing on the key technical choices you made and the reasoning behind them (e.g., trade-offs between consistency and availability, choice of algorithms, etc.).

3. Highlight Your Personal Contribution

Clearly state your role and what you personally built or led. Use 'I' statements to distinguish your work from the team's, and emphasize any unique challenges you solved.

4. Discuss Challenges and How You Overcame Them

Describe the hardest part of the project—whether technical, organizational, or ambiguous—and explain how you navigated it. This demonstrates problem-solving and resilience.

5. Share the Outcome and Learnings

Conclude with the measurable results (e.g., performance improvements, cost savings, user adoption) and reflect on what you learned or would do differently next time.

Key Points to Mention

  • The specific problem and its business impact (e.g., revenue, user experience, scalability).
  • Key technical decisions and trade-offs (e.g., choosing a particular database, framework, or algorithm and why).
  • Your individual contributions and leadership (e.g., designing a module, mentoring others, driving decisions).
  • Challenges faced and how you resolved them (e.g., scaling issues, tight deadlines, cross-team dependencies).
  • Quantifiable outcomes (e.g., reduced latency by X%, saved $Y, increased conversion by Z%).
  • Lessons learned or what you would do differently (shows growth and self-awareness).

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