Coinbase Software Engineer interview questions

57 Software Engineers have shared notes from their Coinbase interviews, with the questions they were asked in each round. That is 73% of the 78 Coinbase interview notes on Screna AI.

57 Software Engineer interview notes

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·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·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·Software Engineer·Technical Phone Screen

Jun 2026
Coinbase SWE interview with a fully open-ended OOD problem where you design a pagination system from scratch, no guardrails, no prescribed interface. The kind of question that feels manageable until you realize you have to justify every single decision you make.
  • Design the API and class structure for a pagination system over a generic collection. You define the interface, the tradeoffs, and justify every choice including cursor vs offset pagination, page size limits, stable ordering, filtering and sorting support, error handling for out-of-range pages or mid-traversal data changes, and how the abstraction works over both in-memory and backed collections.

“The open-endedness is the whole point and also the hardest part.”

View Post

Coinbase·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Coinbase system design round focused on extending a key-value store with TTL support. The question had a lot of moving parts and the discussion went pretty deep into expiration strategies and memory trade-offs.
  • You have an in-memory key-value store with store, read, and scan operations. Extend it to support per-key TTL: store(key, value, ttl) should set an expiry, and reads and scans should not return expired keys. Walk through your design.
  • What are the trade-offs between lazy expiration on access versus running an active background thread that periodically purges expired keys?
  • During a scan over a range of keys, should expired keys be silently skipped in the results, or should the scan also evict them as a side effect?
  • Where should you store the expiry timestamp for each key: inline with the value, or in a separate structure like a min-heap ordered by expiry time?

“I started with lazy expiration because it felt simpler to reason about.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jun 2026
Coinbase software engineer interview with a coding round focused on building a small in-memory banking system. Pretty straightforward on the surface but the follow-up on concurrency is where things got real.
  • Design and implement an in-memory bank system with addAccount, deposit, and transfer operations. Handle invalid inputs and accounts that don't exist.
  • How would transfer behave under concurrent access, and what data structure choices support that?

“Started with a plain hashmap mapping account IDs to balances, which felt obvious enough.”

View Post