← Back to Directory

Coinbase interview notes, page 1 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·Data Scientist·Technical Phone Screen

Feb 2025
Coinbase data science interview with a meaty causal inference question built around a Super Bowl ad scenario. One question, but it had about six sub-problems packed inside it. Not a casual screen.
  • CoinFactory ran a 60-second Super Bowl ad with a QR code on Feb 9, 2025. Walk through how you'd estimate the incremental sign-ups attributable to that ad in the first 48 hours, including your identification strategy, data sources, deduplication approach, a back-of-the-envelope calculation with specific numbers provided, and how you'd validate the final estimate.

“This was a lot.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Apr 2026
Coinbase software engineer interview with a Flappy Bird coding problem that sounds goofy but actually has some real depth to it once you get past the naive solution.
  • Implement a function that decides whether a Flappy Bird character should flap its wings on a given frame, using the bird's current position, velocity, and gravity along with upcoming pipe gap locations. The solution is graded against 20 test cases of increasing difficulty.

“Started with the obvious thing: if the bird is below the center of the next gap, flap.”

View Post

Coinbase·Frontend Engineer·Technical Phone Screen

Apr 2026
Did a frontend technical round at Coinbase where they had me build a dropdown component from scratch. Pretty standard UI component challenge but there's more depth to it than you'd expect going in cold.
  • Build a reusable dropdown component, covering both controlled and uncontrolled usage patterns.

“I underestimated this.”

View Post

Coinbase·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Got a product sense question at Coinbase that was framed around Facebook's reactions feature. Pretty classic PM case but I wasn't expecting it from a crypto company.
  • You're the PM for Facebook's reactions feature. How would you go about improving it?

“I went straight into listing feature ideas which was probably the wrong move.”

View Post

Coinbase·Machine Learning Engineer·Technical Phone Screen

Apr 2026
Coinbase ML engineer interview with a coding question focused on implementing a bagging classifier from scratch. Pretty straightforward if you know ensemble methods, but the details around bootstrap sampling and aggregation can trip you up if you're fuzzy on the mechanics.
  • Implement a bagging (bootstrap aggregating) classifier. A base classifier is provided. Given training data X and labels y, train multiple base classifiers each on a bootstrap sample of the data, then aggregate predictions on new inputs via majority vote. You need to implement fit(X, y) and predict(X).

“The core idea isn't hard but I spent too long second-guessing the bootstrap sampling part.”

View Post

Coinbase·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Interviewed for a PM role at Coinbase, and the question they asked was about food delivery apps.
  • What is your favorite food ordering app?

View Post

Coinbase·Software Engineer·Technical Phone Screen

Apr 2026
Coinbase backend interview, one meaty coding question that looked like a simple parsing problem but kept growing. They pushed pretty hard on edge cases and scalability, which I wasn't fully ready for.
  • Given a list of raw log lines where each line contains a thread ID and a timestamp mixed in with other text, group the lines by thread ID and return each group sorted by timestamp. Be prepared to discuss robust string parsing, handling malformed lines, and how you'd approach very large inputs.

“Started fine, wrote a basic split-and-sort and they seemed okay with it.”

View Post

Coinbase·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Coinbase focused entirely on designing the Explore page. Dense question with a lot of moving parts, probably more than I expected going in.
  • Design the Coinbase Explore page, covering what users see, the data model, ranking and personalization, price data freshness, caching, API contract, mobile vs web considerations, and graceful degradation under load or partial failures.

“This thing is basically five questions stitched into one.”

View Post

Coinbase·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Coinbase for a software engineer role, focused entirely on designing the 'Explore' feature you see in the app for browsing crypto assets. Pretty deep dive, covered a lot of ground in one session.
  • Design the Coinbase Explore feature: an in-app surface where users can browse curated crypto asset lists like trending, top movers, new listings, and themed categories.
  • How would you design the data model to support browsing categories, asset metadata, and real-time price and volume information?
  • Walk through your caching strategy for a feature like this that needs low read latency globally and handles very high read QPS.
  • How would you design the price feed ingestion pipeline to keep asset prices and volume data fresh across the platform?
  • How would you build the ranking logic behind a 'trending' list, and how do you handle personalization on top of that?
  • How do you reconcile editorial curation with algorithmic ranking? What happens when a human-curated list conflicts with what the algorithm would surface?
  • What consistency guarantees would you target for editorial content versus real-time price data, and why?

“This is the core question and it sprawls fast.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Apr 2026
Coinbase software engineer interview with a brutal coding question that involved building out a key-value store with user-based locking. Spent way too long on it and still didn't get all the test cases passing.
  • Implement a key-value store with user-based locking: support setByUser, deleteByUser, lock, and unlock operations, where only the user who locked a key can modify it.

“Spent over 50 minutes on this and still had 4 test cases failing at the end.”

View Post