← Back to Directory

Coinbase interview notes, page 19 of 21

Large Enterprises

Most of these Coinbase write-ups come from Software Engineers (122), then Data Scientists (41) and Product Managers (25). The most reported rounds are the technical phone screen (112), the system design round (31), the product sense round (25) and the online assessment (11).

210 interview notes · updated Jul 2026

Coinbase·Software Engineer·Technical Phone Screen

Jul 2026
Coinbase coding screen with a combinatorics problem that sounds deceptively simple until you start thinking about scale. Pretty algorithmic for a crypto company but not surprising given their engineering bar.
  • Given a set of NFT attribute categories (like ear, eye, background), each with multiple possible values, generate all possible NFT designs by computing the Cartesian product across categories. How do you handle cases where the total number of combinations is too large to fit in memory?

“I went straight to recursion, which worked fine for the basic case.”

View Post

Coinbase·Software Engineer·Online Assessment (OA)

Jul 2026
Coinbase OA for a software engineer role, Flappy Bird variant where you write a jump strategy for a dog navigating a map with coins. The interface pairs you with an AI assistant that generates code, and there's a visual autopilot mode that shows your strategy in action. I found out about the autopilot way too late and burned a ton of time staring at failing unit tests that didn't make much sense on their own.
  • Write a strategy function that decides when a character should jump, given a map with a ceiling boundary, a ground boundary, and coins scattered around. Jumping costs a coin, and you lose if you hit the ceiling, hit the ground, or run out of coins.

“The three loss conditions threw me off at first.”

View Post

Coinbase·Software Engineer·Onsite - Behavioral / Leadership

Jul 2026
Interviewed for an EM role at Coinbase. Just one behavioral question from what I can tell, the kind that sounds broad but actually has a pretty specific answer they're fishing for.
  • Tell me about a time when something you did had organization-wide impact.

“I had an answer ready but partway through I realized it was more team-level than org-level and kind of scrambled to reframe it.”

View Post

Coinbase·Product Manager·Onsite - Product Sense / Strategy

Jul 2026
PM interview at Coinbase, one question about diagnosing a DAU drop. Pretty standard metrics investigation prompt but crypto adds some wrinkles worth thinking through.
  • You're the PM for Coinbase and DAU has dropped 10%. How do you investigate?

“I jumped straight to segmentation (platform, region, user cohort) which felt right, but I forgot to ask about the timeframe first and that probably hurt me.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jul 2026
Coinbase coding round focused on extending a recipe management system with version history and rollback. The design angle made it feel more like a mini system design problem than a pure coding question, which I wasn't fully prepared for.
  • You're given a recipe management system with basic CRUD and search operations. Extend it to support full version history and rollback: every mutating operation should record a version snapshot, and you need to implement getVersionHistory and rollback methods.
  • What are the storage trade-offs between storing full snapshots per version versus storing an operation log and replaying up to a target version?

“The coding part wasn't the hard part.”

View Post

Coinbase·Software Engineer·Onsite - System Design / Architecture

Jul 2026
Coinbase system design round for a software engineer role. The whole thing was basically one giant question about building an online bank account opening system, and they wanted you to go deep on pretty much every layer of it.
  • Design an end-to-end online bank account opening workflow, including APIs for starting, saving, submitting, and resuming an application.
  • How would you handle KYC/AML and sanctions checks within this workflow, and how do you decide which steps are synchronous versus asynchronous?
  • How would you prevent duplicate accounts from being created?
  • How would you provide real-time application status updates to users?
  • Walk me through your approach to document upload and verification in this system.
  • How would you design the data model for applicants and their applications, and how do you handle PII security including encryption and access control?
  • How would you implement audit trails for this system?
  • How would you handle failure scenarios and retries, especially for external service calls like KYC providers?
  • How would you implement rate limiting and fraud or risk scoring in this workflow?
  • How would you scale this system to handle millions of applications per day across multiple geographic regions?

“I started with the happy path and drew out the state machine for an application going from draft to submitted to approved.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jul 2026
Coinbase software engineering interview with a coding round focused on building out a food-delivery analytics module. Three interconnected tasks, each layering on more complexity. Pretty design-heavy for what felt like a coding screen.
  • Given a user's coordinates and a target menu item, find the restaurant(s) offering the lowest price for that item. Break ties by Euclidean distance to the user and return the restaurant id and distance.
  • For a given time window, compute total revenue, total order count, and average order value across all orders that fall within that range.
  • For a given time window, return the top K orders by total price and the top K items by total quantity sold. You need to specify your tie-breaking rules, data structure choices, and time complexity.

“The price filtering part was straightforward but I fumbled the tie-breaking logic at first.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jul 2026
Two-part coding interview for a Software Engineer role at Coinbase. First problem was grid pathfinding with a BFS/bitmask twist, second was an event processing design question with idempotency requirements. Pretty dense for a single session.
  • Given a 2D grid representing a restaurant with a starting position, empty cells, obstacles, and food items, find the shortest path from the start to a single specified food cell. Return -1 if unreachable.
  • Extend the grid problem: now there are up to 12 food items and the waiter must collect all of them starting from S, in any order, minimizing total steps. Describe your algorithm, its complexity, and implement it.
  • Design and implement a function that processes a stream of order events (NEW, FILL, CANCEL) and returns the final state of each order, including total quantity and filled quantity.
  • How do you guarantee idempotency in the event processor when the same logical event (same eventId) can arrive multiple times due to at-least-once delivery?
  • What are the time and space complexities of your event processing solution in terms of number of events and number of distinct orders?

“Classic BFS, nothing tricky here.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jul 2026
Coinbase technical screen with a pretty gnarly combinatorics problem about NFT generation. Not your typical coding question, it pushed into system design territory fast.
  • You're generating NFTs randomly where each NFT is one value chosen per attribute category (like ear, eye, background). How do you guarantee no duplicates are produced across a large generated set?

“I started with the hash set approach because it felt obvious, track each tuple you've seen and reject on collision.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jul 2026
Coinbase SWE interview had me extending a basic banking system with deferred payment scheduling. Pretty meaty design problem for a single coding round, more interesting than the usual LeetCode grind.
  • You have a basic banking system with users, balances, deposits, and transfers. Extend it to support scheduled payments: implement schedulePayment(from_user, to_user, amount, execute_at) that queues a transfer for a future time and returns a unique payment ID, and cancelPayment(payment_id) that cancels a pending payment and returns whether it succeeded.

“The baseline system was handed to me, so the real challenge was figuring out the right data structures for the scheduling layer.”

View Post