← Back to Directory

Coinbase interview notes, page 8 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

May 2026
Coinbase SWE interview with a coding problem that had a specific constraint I wasn't expecting. The twist on the standard knapsack setup threw me off a bit.
  • You have N transactions, each with an ID, a size, and a fee. Given a block with a fixed size capacity, choose which transactions to include in order to maximize the total fee collected.

“Looked like a classic knapsack at first and I started mentally reaching for a heap-based approach.”

View Post

Coinbase·Software Engineer·Onsite - System Design / Architecture

May 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 done your prep there you'll recognize it immediately.
  • Design a crypto brokerage platform.

“It's a known question if you've been lurking the right prep forums, which I had.”

View Post

Coinbase·Data Scientist·Technical Phone Screen

May 2026
Coinbase data scientist interview that went deep on ML fundamentals. They had me implement K-Means from scratch and wanted the full picture, not just the happy path.
  • Implement K-Means clustering from scratch without using any ML libraries. Walk through centroid initialization, the assignment step, the update step, convergence, and how you'd handle edge cases like empty clusters.

“This was more involved than I expected for a phone screen.”

View Post

Coinbase·Software Engineer·Online Assessment (OA)

May 2026
Did the Coinbase SWE online assessment and got the worker salary problem. Java was a rough choice for this one, took way longer than it should have.
  • Solve the worker salary optimization problem.

“Java was probably the wrong call here.”

View Post

Coinbase·Frontend Engineer·Take-home Assignment

May 2026
Take-home assignment for a frontend role at Coinbase. Build a list component with empty state, a clean prop API, and enough styling to not look embarrassing. Pretty scoped exercise but there are a few details that can trip you up if you're not thinking about extensibility.
  • Build a reusable list UI component that renders an array of items, handles an empty state, exposes a clean prop API with optional callbacks, and is structured to support future API-driven data and reordering.

“The empty state tripped me up more than I expected.”

View Post

Coinbase·Data Scientist·Technical Phone Screen

May 2026
Probability and stats question for a data scientist role at Coinbase. Pretty textbook stuff but the conditional probability part at the end tripped me up more than I expected.
  • If n users each independently link a crypto wallet with probability p, what is the expected number of users who link their wallet?
  • What is the probability that at least one of the n users links their wallet?
  • Given that at least one of two specific users A or B links a wallet, what is the probability that both of them do?

“This one was fine.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

May 2026
Coinbase software engineering interview with a coding round focused on state machine design for a trading order system. Pretty domain-specific but the core logic wasn't too bad once I stopped overthinking it.
  • Design and implement an in-memory order management component for a crypto trading system. Orders can be in states NEW, ACTIVE, PAUSED, CANCELLED, or FILLED. Implement pause, resume, and cancel operations that enforce valid state transitions and return success or failure accordingly.

“The state machine part was actually pretty clear once I drew it out.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

May 2026
Coinbase SWE interview with a coding round that had a pretty rough second question. The problem statement was vague upfront and I ended up getting something running but with bugs still in it.
  • Given a set of items with fees, sizes, and dependencies on other items, select an optimal subset to maximize some objective while respecting those dependencies.

“No input/output examples at the start, which threw me off more than I expected.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

May 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 interviewer just watches you propose everything and pushes back on your choices.
  • Design the API and class structure for a generic pagination system. You decide the interface, the pagination strategy, and how it handles edge cases like out-of-range pages or data changing mid-traversal.

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

View Post

Coinbase·Data Scientist·Technical Phone Screen

May 2026
Coinbase data scientist interview with a meaty SQL question built around a user transaction table. The scenario felt very on-brand for a crypto company where cross-region activity actually matters. One question but it had several moving parts, so it took up most of the session.
  • Given a user transaction table with adoption dates and transaction records across regions, compute the overall adoption rate and transaction rate for a date range, calculate time-to-first-transaction in days for each adopted user, and identify cross-region transactions where the transacted region differs from the user's first transaction region.

“This looked manageable at first glance and then I started writing it and realized I had three separate problems duct-taped together.”

View Post