Coinbase Interview Questions — Page 5

Coinbase·Data Scientist·Technical Phone Screen

May 2026

Coinbase data scientist interview had at least one question that was more of a manual computation exercise than anything conceptual. You basically have to do neural network math by hand, layer by layer, which I was not expecting at this level.

Given a small neural network's weights, biases, and activation functions, manually compute the output for a specific input vector by walking through each layer's matrix multiplication, bias addition, and activation step.

“I knew the mechanics but doing it by hand under pressure is a different thing.”

View Post

Coinbase·Product Manager·Onsite - Product Sense / Strategy

May 2026

PM interview at Coinbase with a product sense question about social features. Pretty open-ended, which I wasn't fully prepared for.

How would you go about adding social features to the Coinbase platform?

“I fumbled the opening on this one.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

May 2026

Coinbase backend interview focused on extending a key-value store with TTL support. The design space was broader than I expected and the discussion went pretty deep into trade-offs I hadn't fully thought through beforehand.

You're given an in-memory key-value store with store, read, and scan operations. Extend it to support per-key TTL, where reads and scans ignore or remove expired keys. Walk through your design.
Compare lazy expiration on access versus a background sweeper thread for purging expired keys. What are the memory and latency trade-offs?
Where would you store the expiry timestamp for each key, and why? Inline with the value, or in a separate structure like a min-heap keyed by expiry time?

“I jumped straight to lazy expiration because it felt obvious.”

View Post

Coinbase·Software Engineer·Onsite - System Design / Architecture

May 2026

Coinbase software engineer interview that went deep into system design for a banking system. Four parts, each one building on the last, and by the end I was pretty much designing a mini fintech backend from scratch. The scope was bigger than I expected.

Design and implement an in-memory banking system with CreateAccount and Transfer operations. Your solution needs to handle validation for nonnegative amounts, sufficient funds, account existence, and atomic balance updates. How do you make transfers idempotent using transaction IDs?
Add a query to return the top K accounts by total outgoing transfer volume. What data structures do you use, and what are the time and space complexity tradeoffs for both updates and queries?
Implement a Purchase operation that awards 2% cashback credited exactly 24 hours after the purchase. How do you structure pending rewards, schedule the credit posting, and ensure the processing is idempotent and crash-safe?
Design a MergeAccount operation that combines two accounts: transfer balances and transaction history to the primary account, redirect future operations from the duplicate ID, and reconcile pending cashback and any overlapping transaction IDs.

“The idempotency part is where I stumbled.”

View Post

Coinbase·Frontend Engineer·Onsite - System Design / Architecture

May 2026

System design round at Coinbase for a frontend engineer role, entirely focused on building a crypto trading platform from scratch. It was one of the more exhaustive design interviews I've done, covering everything from component APIs to WebSocket throttling strategies.

Walk through your tech stack choices for a cryptocurrency trading platform: framework, state management, build tooling, and styling. Why those choices?
How would you structure the pages of the platform? Think market overview, trading pair detail, portfolio and open orders, and account pages.
Break down the reusable components you'd build: price ticker, order book panel, candlestick chart, order form, toast/alert system, and a virtualized trade history table. For each, describe the props API and implementation approach.
How do you handle real-time data from WebSockets in a frontend app? Cover subscription management, throttling or batching updates to avoid frame drops, and optimistic UI for order submission.
What cross-cutting concerns would you design for across the whole platform? Things like theming, internationalization, accessibility, error states, and authenticated vs guest views.
Deep dive: how would you implement the order book panel specifically to handle hundreds of price level updates per second without degrading performance?

“I went with React plus Zustand for state because Redux felt like overkill to justify in real time.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

May 2026

Coinbase software engineer interview with a multi-level in-memory system design coding problem. The whole thing was structured as an incremental build, starting simple and getting more complex as you go. Pretty classic for this kind of role but the versioning level tripped me up more than I expected.

Design and implement basic CRUD operations for an in-memory recipe store: add, update, get, and delete, with clear behavior defined for edge cases like missing records.
Implement a case-insensitive recipe search by name and a list function that sorts recipes by name or size, with a defined tie-breaking rule.
Add user management to the system with an addUser operation. Define what happens on duplicate userId.
Add version history and rollback support so that every mutating operation creates a new version and the system can be restored to any prior version by version ID.

“Started fine, picked a hashmap keyed by recipeId and just rejected duplicates on add rather than overwriting.”

View Post

Coinbase·Data Scientist·Technical Phone Screen

May 2026

Coinbase data science interview with a probability modeling question that felt more like a stats exam than anything I'd done before. The scenario was about feature adoption and they walked through three parts back to back, each building on the last.

You're modeling wallet feature adoption where each of n users independently adopts with probability p. Walk through: (a) the expected number of adopters, (b) the probability that at least one user adopts, and (c) given that at least one adopts, the probability that exactly two users adopt.

“Part (a) was fine, np, done.”

View Post

Coinbase·Frontend Engineer·Take-home Assignment

May 2026

Take-home OA for a frontend role at Coinbase. The task was to build a reorderable list component with up/down controls, accessibility requirements, and proper state/event handling. Pretty scoped but there were enough edge cases to trip you up if you weren't careful.

Build a reorderable list UI component in a frontend framework of your choice. Each item should have up/down controls that swap it with its neighbor, with the boundary items' controls disabled. The component should handle empty state, emit change events to the parent, use stable keys for item identity, and meet accessibility standards including keyboard support and focus management.

“The swap logic itself is trivial, like three lines.”

View Post

Coinbase·Software Engineer·Onsite - System Design / Architecture

May 2026

Coinbase SWE interview focused almost entirely on designing an in-memory order stream service, which sounds straightforward until they start piling on follow-ups about state machines, idempotency, and concurrency. It was a long session and I left unsure whether I'd covered enough depth on the data structure choices.

Design an in-memory order stream service supporting add, delete, pause, and resume operations. Define the order schema and valid state transitions, and make sure all operations are idempotent.
What data structures would you use to support efficient lookups both by order_id and by user_id, and what are the time and space complexity tradeoffs?
As a follow-up: implement a delete_all_by_user operation that removes all orders for a given user_id. How does this change your design?
How would you extend this service to support persistence and handle concurrent access if required?
Walk through example test cases that would validate the correctness of your implementation, including edge cases.

“I started with the schema and worked outward, which felt right.”

View Post

Coinbase·Software Engineer·Onsite - Behavioral / Leadership

May 2026

Behavioral round for a software engineer role at Coinbase, with a pointed follow-up question about why you haven't been promoted yet. Pretty standard until it wasn't.

Walk me through your career trajectory so far and what you've done to actively pursue a promotion.
You've delivered strong projects but haven't been promoted. What feedback have you received that explains that gap, and what are you doing about it?

“I had a decent answer ready for the general trajectory part but stumbled when they pushed on what I'd actually done to seek promotion.”

View Post