← Back to Directory

Coinbase

Large Enterprises

Most of these Coinbase write-ups come from Software Engineers (57), then Frontend Engineers (11) and Machine Learning Engineers (6). The most reported rounds are the technical phone screen (45), the system design round (13), the online assessment (7) and the take-home assignment (5).

78 interview notes · updated Jun 2026

Coinbase·Software Engineer·Technical Phone Screen

Jun 2026
Coinbase coding screen with a combinatorics problem that sounds easy until you think about the output size. Decent problem, nothing too tricky if you've done recursive enumeration before.
  • Given a set of attribute categories (like ear, eye, background), each with multiple possible values, generate all possible NFT designs by computing the Cartesian product across categories. How would you implement this, and what happens when the output is too large to fit in memory?

“I went straight to DFS and it worked fine for the core implementation.”

View Post

Coinbase·Data Scientist·Technical Phone Screen

Jun 2026
Coinbase data scientist interview that went deep on ML fundamentals, specifically building a random forest from the ground up. No sklearn allowed, which honestly changes how you think about the problem. Walked away feeling like I understood the algorithm better than I did going in, even if I stumbled a bit on the complexity analysis.
  • Implement a Random Forest classifier from scratch without using any ML libraries. Walk through the full design: decision tree construction with a splitting criterion, bootstrap sampling, random feature selection at each split, and how you aggregate predictions across trees.
  • What are the key hyperparameters in a random forest and how do they affect model behavior and computational cost?

“This took up almost the entire session.”

View Post

Coinbase·Data Scientist·Technical Phone Screen

Jun 2026
Coinbase data scientist interview that went deep on ML fundamentals. They had me implement K-Means from scratch, no libraries, and actually talk through the math and tradeoffs. More rigorous than I expected for a DS role.
  • Implement K-Means clustering from scratch without using any ML libraries. Walk through centroid initialization, the assignment step, the update step, convergence criteria, and how you'd cap iterations. Also discuss time and space complexity and what happens when a cluster ends up empty.

“This was a lot to hold in my head at once.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jun 2026
Coinbase software engineer interview with a brutal coding question that ate up most of the session. The problem was way more involved than expected and I left with failing test cases, which didn't feel great.
  • Implement a key-value store with user-based locking: a user can lock a key, the locking user can still read and write to it, but other users are blocked from modifying it. You need to implement setByUser, deleteByUser, lock, and unlock.

“Spent over 50 minutes on this and still had 4 test cases failing at the end.”

View Post

Coinbase·Software Engineer·Online Assessment (OA)

Jun 2026
Coinbase OA for a software engineer role had an AI-assisted coding round where you had to implement a jump boundary function for a Flappy Bird game. The platform rendered the map live in the browser which was a nice touch. Passed 16 out of 20 test cases and still moved forward, so the bar wasn't all-or-nothing.
  • Implement the jump boundary function for a Flappy Bird game.

“Weird one to get in a coding assessment.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jun 2026
Coinbase software engineer interview focused on extending a toy bank system with scheduled transfers. Pretty deep on data structures and edge cases, more than I expected for what seemed like a coding round.
  • You're given an in-memory bank system with basic account operations already implemented. Add support for scheduling a future transfer between accounts, where the transfer executes at a specified time. What data structure do you use and why?
  • What should happen when a scheduled transfer's execution time arrives but the source account doesn't have enough funds?
  • How does canceling a scheduled transfer interact with transfers that have already executed? What does your cancelScheduled function return or do in that case?

“I went straight to a priority queue keyed by execution time and they seemed fine with that, but then they asked what happens if two transfers share the same timestamp and I fumbled around for a bit.”

View Post

Coinbase·Frontend Engineer·Take-home Assignment

Jun 2026
Coinbase frontend take-home that looked manageable on paper but had enough moving parts to trip you up if you underestimated the scope. The prompt was well-written at least, no ambiguity about what they wanted.
  • Build a list component app with API data fetching, per-item reordering controls, loading/error states, and proper request cancellation on unmount or overlapping calls.
  • Implement 'up' and 'down' reordering controls per list item, with the boundary items' controls disabled, and use stable keys throughout.
  • Write unit and component tests covering rendering, data fetching behavior, reordering logic, and edge cases.
  • Structure the app with clear separation between data-fetching logic and presentation components, and ensure accessibility including keyboard navigation, aria labels, and focus management.

“The request cancellation piece is where I spent way too long.”

View Post

Coinbase·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Coinbase system design round, extending a key-value store with snapshot and restore functionality. The problem sounds manageable until you realize how many edge cases live in the TTL handling and concurrency bits.
  • You're given an in-memory key-value store with per-key TTL support and range scan. Design a backup() and restore() API that captures a point-in-time snapshot including remaining TTLs, and can bring the database back to that state.
  • How would you represent the snapshot in memory? Walk through the trade-offs between a deep copy, copy-on-write, and an append-only mutation log.
  • What counts as 'state' in this system when taking a snapshot? What do you need to capture beyond just the key-value pairs?
  • How do concurrent writes interact with snapshot creation, and how do you define a consistency boundary for the snapshot?

“I went straight to deep copy because it felt safe and I could reason about it easily.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jun 2026
Coinbase software engineer interview that focused entirely on pagination, which sounds boring until you're 20 minutes deep explaining cursor-based vs offset-based tradeoffs and realizing you never actually thought hard about this before.
  • Given a list or stream of items and pagination parameters like page number, page size, and an optional sort key, implement a function that returns the correct page of results. Be ready to discuss 0-indexed vs 1-indexed pages, out-of-range handling, returning total count and total pages, and the scaling differences between offset-based and cursor/keyset-based pagination.

“Started fine with the basic slice logic but then they kept pulling the thread.”

View Post

Coinbase·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Redo interview at Coinbase for a software engineer role, same interviewer as before. The question was a crypto brokerage system design pulled straight from 1point3acres, so if you've been prepping from there you'll recognize it.
  • Design a crypto brokerage platform.

“Knew this one was floating around on prep forums so I'd at least skimmed it before going in.”

View Post

Coinbase interview guides

Online Assessment

8 Coinbase OA Reports 2026: Real SWE Questions & AI Coding

Coinbase interview FAQ

What rounds are in the Coinbase interview?

Candidates most often report a technical phone screen (45 write-ups), a system design round (13), an online assessment (7) and a take-home assignment (5).

What does the Coinbase technical phone screen cover?

Across 45 technical phone screen write-ups, the most tagged question topics are Technical Trade-offs (60 questions), Algorithms & Data Structures (52) and System Design (50).

What is asked in the Coinbase system design round?

Across 13 system design write-ups, the most tagged question topics are System Design (44 questions), Technical Trade-offs (35) and API & Integrations (12).

Coinbase interview guides by role

57 notes

Coinbase Software Engineer interview questions

11 notes

Coinbase Frontend Engineer interview questions