← Back to Directory

Coinbase interview notes, page 15 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·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Coinbase for a software engineer role. Two meaty questions that both required real examples, not just theory. Left feeling okay about it but not great.
  • Walk me through the most complex project you've led from start to finish. What made it complex, how did you break it down, what were the key risks, and what were the measurable outcomes?
  • Describe a situation where you solved the same problem using more than one approach. What alternatives did you consider, how did you weigh the trade-offs, what did you go with, and what did you learn from it?

“I had a decent example ready but fumbled the 'measurable outcomes' part.”

View Post

Coinbase·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
PM interview at Coinbase, got hit with a classic metrics decline question. Not much to report on format or outcome but the question itself was pretty meaty.
  • Netflix's click-through rate has dropped by 10%. How would you investigate and respond to this?

“I started with segmentation, which felt right, breaking it down by surface (home, search, browse), device type, user cohort.”

View Post

Coinbase·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Coinbase for a software engineer role, focused entirely on front-end architecture for a crypto trading platform. Pretty deep dive, way more breadth than I expected for a single session.
  • Walk through how you would design the front-end architecture for a retail cryptocurrency spot trading web app, covering the core screens: a market page with live order book and charting, portfolio and order management, and authentication with session handling.
  • How would you structure the WebSocket layer for real-time order book and trade feed updates, and how do you handle reconnections or degraded network conditions?
  • The order book can have hundreds of rows updating multiple times per second. How do you keep rendering performant without freezing the UI?
  • What reusable components would you build for a trading-specific design system, and how would you approach accessibility for something like an order book table or a price input field?
  • How would you handle security concerns on the front end, specifically around XSS, CSRF, and token storage for an authenticated trading app?
  • How would you approach testing this application across unit, integration, and end-to-end layers?

“This is a big open-ended question and I spent probably too long on stack choices before getting to the actual architecture.”

View Post

Coinbase·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Coinbase software engineer round that was basically one long iterator design problem with layers added on top. No IDE, no autocomplete, just you and a blank editor writing interfaces and tests from scratch. More involved than I expected for a single session.
  • Without using any built-in library types, define an iterator interface from scratch with at least hasNext() and next(), then implement two concrete classes that use it with different traversal behaviors.
  • On top of your iterator implementations, satisfy three additional requirements added one at a time during the interview, such as a peek() method, a filtering wrapper, or flattening multiple iterators together, while keeping each operation efficient.
  • Write unit tests from scratch covering each iterator and each added requirement, including edge cases like empty collections, single elements, and calling next() after the iterator is exhausted.

“I started with the interface fine, that part felt clean.”

View Post

Coinbase·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Coinbase ML Engineer interview where they dropped a messy Jupyter notebook in front of me and said go. One session, real data, binary classification, and a clock ticking in the background. Not a vibe check, they actually wanted working code.
  • Given a messy real-world tabular dataset in a live notebook, build a working end-to-end binary classification baseline: clean the data, split without leakage, train a model that handles mixed feature types, evaluate with an appropriate metric, and explain your choices.

“The part that tripped me up first was the identifier columns.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jun 2026
Coinbase software engineer interview with a coding round focused on designing a cursor-based paginator from scratch. The problem had more edge cases than it looked like at first glance and I probably underestimated it going in.
  • Design a pagination system that supports forward and backward navigation using cursors. You're given a sorted array of items and a page size. Implement getFirstPage(), getNextPage(cursor), and getPrevPage(cursor), each running in O(pageSize) time, and handle edge cases like partial last pages and navigating past the boundaries.

“I started by just using an integer index as the cursor which felt almost too simple, and the interviewer kept pushing on whether that was enough.”

View Post

Coinbase·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Interviewed for a PM role at Coinbase, got a product sense question that felt more like it belonged in a consumer tech loop than a crypto company.
  • What is the primary goal of Airbnb hosts when using the platform?

“Threw me a bit because I was deep in crypto prep mode and suddenly we're talking about Airbnb.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jun 2026
Coinbase software engineer interview with a multi-part object-oriented design problem. The problem built on itself across four stages, each adding more complexity. Pretty grueling but the progression felt deliberate rather than random.
  • Design a task management system where tasks have a unique ID, name, and priority. Implement create, get, and update operations.
  • Extend the system to support listing the top N tasks by priority overall, and also the top N tasks by priority that contain a specific substring in their name.
  • Add a user model with a quota (max active tasks). Allow assigning a task to a user with a TTL, where the same task can be assigned to multiple users and a user can hold multiple tasks. Implement a way to list a user's currently active assignments.
  • Add a complete-task operation that takes a timestamp. If a task has multiple assignments, complete the one with the earliest start time. Assignments past their TTL are expired and cannot be completed. Also implement listing a user's expired assignments as of a given time.

“Straightforward enough to start.”

View Post

Coinbase·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Coinbase ML engineer interview with a very hands-on neural network math question. No fluff, they just handed you a small network with explicit weights and asked you to grind through the arithmetic layer by layer.
  • Given a small fully connected neural network with specific weights and biases and sigmoid activations, compute the forward pass step by step, showing the pre-activation values (z = Wx + b) and the activated outputs (a = sigmoid(z)) for each layer.

“This looked straightforward until I started second-guessing my sigmoid approximations mid-calculation.”

View Post

Coinbase·Data Scientist·Technical Phone Screen

Jun 2026
Coinbase data scientist interview that went deep into probability theory. The whole session was basically a single extended question on binomial/Poisson models with a bunch of sub-parts, which I wasn't expecting to be so math-heavy for a DS role.
  • For n independent users each linking a wallet with probability p, derive the probability that at least one user links and the probability that exactly k users link. Cover edge cases like p=0, p=1, large n, and the small-p large-n Poisson approximation.
  • Derive the expected number of users who link a wallet. Be explicit about where independence is and isn't required.
  • For small p and large n, give the Poisson approximation for P(at least one user links), then derive the first-order error term including its direction.
  • With p=0.30 and n=5, compute P(at least one user links), P(exactly 2 users link), and the expected number of links.
  • Two users A and B have independent linking probabilities of 0.40 and 0.60. Compute P(A or B), P(A and B), and P(A and B given A or B).
  • If independence between users A and B is not assumed, but you know P(A or B)=0.70 with marginals 0.40 and 0.60, what is the feasible range for P(A and B)? Then give the corresponding range for P(A and B given A or B), and explain what dependence structure produces each boundary.

“The binomial formula itself was fine but I fumbled the edge cases a bit.”

View Post