← Back to Directory

Coinbase interview notes, page 7 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 software engineer interview with two back-to-back coding problems, both more involved than I expected for a single session. The second one especially had enough moving parts that I was still mentally untangling it after the call ended.
  • Implement a function that updates a bird's vertical position for one game tick in a Flappy-Bird-style simulator, returning the new position, new velocity, and whether the bird is still within the playable area.
  • Design and implement a greedy block-building algorithm for a simplified cryptocurrency mining simulator, where transactions have fees, sizes, and parent dependencies that must be respected in ordering. Handle dependency cycles and discuss time complexity and caching strategies for large mempools.

“Seemed manageable at first.”

View Post

Coinbase·Data Scientist·Technical Phone Screen

May 2026
Coinbase data scientist interview with a probability-heavy stats problem centered on a wallet feature adoption scenario. Pretty theoretical, felt more like a grad school exam than a product interview, but the questions were at least well-structured.
  • If N users each independently adopt a wallet feature with probability p, what is the expected number of users who adopt it?
  • Using the same setup, compute the probability that at least one user adopts the wallet feature.
  • What core statistical assumption makes these calculations valid?
  • Given that at least one of two specific users adopted the feature, what is the probability that both of them did?

“Pretty standard if you remember linearity of expectation.”

View Post

Coinbase·Product Manager·Onsite - Product Sense / Strategy

May 2026
PM interview at Coinbase with a product design question borrowed straight from the Facebook playbook. Short round, one question, nothing crypto-specific about it.
  • What kind of travel product would you design for Facebook?

“Weird question to get at a crypto company but here we are.”

View Post

Coinbase·Software Engineer·Onsite - System Design / Architecture

May 2026
Coinbase system design round, one big question that sprawled across basically every hard distributed systems topic you can think of. The scope was genuinely intimidating and I'm not sure I covered even half of it well.
  • Design a crypto trading platform that routes client orders to third-party exchanges via a synchronous HTTP API, where fills and cancellations actually arrive asynchronously. Cover the overall architecture, order state machine, failure handling, traffic spikes, data consistency, optional multi-exchange routing, and client-facing APIs with observability.

“This question ate me alive a little.”

View Post

Coinbase·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Coinbase for a software engineer role, focused entirely on building a real-time crypto price feed at scale. Pretty deep technically, they wanted specifics on every layer from exchange ingestion all the way to what the browser does when it loses connection.
  • Design the Coinbase home page with real-time cryptocurrency price updates. Walk through the full pipeline from exchange data feeds to what the client renders.
  • Compare WebSocket, Server-Sent Events, and long-polling for streaming price updates to the client. What are the tradeoffs and when would you fall back?
  • How would you handle throttling and coalescing high-frequency price updates so the UI doesn't become unusable?
  • Describe a viewport-driven subscription model where clients only receive updates for the symbols currently visible on screen.
  • How do you scale the fan-out layer to support millions of concurrent connected clients?
  • What are your reconnect and replay semantics when a client drops and reconnects?
  • How does the client degrade gracefully when the streaming connection fails or the data becomes stale?

“This is the whole question, basically.”

View Post

Coinbase·Data Scientist·Technical Phone Screen

May 2026
Coinbase data scientist interview threw a classic logic puzzle at me that I thought I remembered from undergrad. I did not remember it as well as I thought.
  • You have 12 visually identical coins, one of which is counterfeit and either heavier or lighter than the rest (you don't know which). Using a balance scale and exactly three weighings, identify the counterfeit coin and determine whether it is heavier or lighter. Walk through the full decision tree.

“I'd seen this puzzle before and that almost made it worse because I half-remembered a solution and kept second-guessing myself.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

May 2026
Coinbase SWE interview with a meaty algorithmic design problem around NFT metadata generation. The question had multiple layers of constraints stacked on top of each other, which kept things interesting but also stressful.
  • Given a set of trait types (like background, eyes, hat), each with a list of valid values, and a target count N, write a function to generate N NFT metadata items. Then handle follow-up constraints: no repeated trait value within a single NFT, uniqueness of the full trait combination across all generated NFTs, and optional inclusion/exclusion rules between traits. Also explain your data structures, algorithm, complexity, and how you'd test it.

“This one had me feeling good for about two minutes and then the follow-ups started piling up.”

View Post

Coinbase·Software Engineer·Hiring Manager Screen

May 2026
Behavioral round at Coinbase with a hiring manager from a neighboring team. Pretty short, wrapped up in about 30 minutes. Standard stuff plus one question about AI usage that I wasn't fully expecting.
  • Standard behavioral questions about your past work and experience.
  • How do you use AI tools in your day-to-day engineering work?

“Nothing surprising here, ran through a couple situation-action-result style answers.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

May 2026
Coinbase SWE interview, algorithmic round focused on dynamic programming with a stock trading twist. The follow-up questions about fee variations and concurrent share holdings made it more interesting than your typical DP problem.
  • Given an array of daily stock prices and a transaction fee charged on each sale, find the maximum net profit you can make with unlimited transactions (buy then sell, one share at a time). Walk through your algorithm and give time and space complexity.
  • How would your solution change if the commission fee applied to both buying and selling instead of just selling? What if you could hold multiple shares at the same time?

“The DP formulation clicked pretty fast for me.”

View Post

Coinbase·Data Scientist·Onsite - Behavioral / Leadership

May 2026
Behavioral question for a Data Scientist role at Coinbase, heavy on compliance and ethics judgment. One question, but it had a lot of layers crammed into it.
  • Tell me about a time someone asked you to bend or skip a rule for the sake of speed, like a process, compliance, or data governance policy. How did you weigh the risk, loop in the right people, and keep things moving in a remote cross-functional environment? And if the request had come from an executive and touched something like immigration or payroll compliance, would you have handled it differently?

“This question is doing a lot of work at once.”

View Post