← Back to Directory

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

Jun 2026
Coinbase data scientist interview with a single deep-dive question on wash trading detection. The whole thing was basically one extended case study and it went places I wasn't fully prepared for.
  • Design an end-to-end analytics system to detect and quantify wash trading on BTC-USD and low-liquidity altcoin pairs on a centralized exchange. Cover feature engineering from order and trade logs, graph-based methods to infer shared account control, threshold-setting with precision/recall trade-offs, backtesting with synthetic injected wash trades and any enforcement ground truth, a daily risk score with confidence intervals and calibration, and how you'd surface flagged cases to Compliance without penalizing legitimate market makers.

“This was a beast.”

View Post

Coinbase·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Coinbase for a software engineer role, basically one big question about a project you're proud of. Felt like a lot to cover in one answer and I probably tried to say too much.
  • Walk me through a project you're most proud of: what was the problem, what did you own, what were the hard technical and non-technical challenges, what trade-offs did you make, what was the measurable impact, and what would you change looking back? Also touch on how you worked with others and handled any conflict.

“This is basically five questions crammed into one and I did not pace myself well.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jun 2026
Coinbase software engineer interview with a multi-part coding problem centered on building an in-memory file storage system from scratch. The problem kept growing with each new operation added, which was the whole point I think.
  • Design and implement an in-memory cloud storage service supporting user creation with capacity limits, file add/get operations, and capacity updates with automatic eviction of the largest files.
  • Extend the storage service with COMPRESS_FILE and DECOMPRESS_FILE operations that rename files, halve or double their sizes, and enforce constraints like suffix checks and capacity validation on decompression.

“The first few operations felt manageable.”

View Post

Coinbase·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
PM interview at Coinbase where I got a product metrics question about Airbnb's homepage. Pretty standard product sense round but the cross-company framing threw me a little.
  • What success metrics would you define for Airbnb's homepage?

“I went straight for booking conversion and blanked on the awareness/discovery side for longer than I'd like to admit.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jun 2026
Coinbase software engineer interview focused on extending an in-memory banking system, specifically around tracking spending and building a top spenders query. Pretty design-heavy for what felt like a coding round, lots of back-and-forth on tradeoffs.
  • You're given an in-memory bank system with addAccount, deposit, and transfer operations. Extend it to track total outflows per account, then implement a topSpenders(n) function that returns the top n accounts by total spending with a defined tiebreaker.
  • What are the tradeoffs between maintaining a running per-account spending total versus computing it on demand, and how would you support efficient top-n queries as the number of accounts scales?

“The core implementation wasn't too bad.”

View Post

Coinbase·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Interviewed for a PM role at Coinbase and got a classic product prioritization question. Pretty standard stuff for crypto/fintech but the product choice matters a lot here.
  • Pick any product and walk me through how you would prioritize new features for it.

“I picked something I knew well instead of trying to impress them with a crypto-native product, which in retrospect was probably the right call.”

View Post

Coinbase·Software Engineer·Onsite - Product Sense / Strategy

Jun 2026
Coinbase PM interview, one question about token listing process. Pretty open-ended, more strategic than I expected for a consumer-focused role.
  • You're the PM of the Coinbase consumer app. Walk through how you'd decide which new tokens to add to the platform.

“This one pulled in way more dimensions than I initially gave it credit for.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jul 2026
Coinbase software engineer interview with a multi-level coding problem centered on building an NFT minting and management system from scratch. The problem escalated across three levels, from basic ownership tracking to transfers to royalty calculations, and you had to define your own test cases and parse input yourself.
  • Implement a basic NFT minting system where you can mint an NFT with a creator and metadata, look up the current owner, and list all NFTs owned by a given user.
  • Add transfer functionality so ownership can move between users, with validation that only the current owner can initiate a transfer, and maintain a full transfer history per NFT.
  • Extend the transfer system to support a sale price, where the original creator automatically receives a royalty percentage from every secondary sale, the seller gets the remainder, and balances are tracked per user with proper error handling.

“First level felt manageable.”

View Post

Coinbase·Data Scientist·Technical Phone Screen

Jul 2026
Coinbase data science interview with two meaty case questions back to back. One was a classic estimation problem, the other a revenue diagnostics exercise. Nothing too exotic but the depth expected was real.
  • Estimate how many users would register on a platform after a Super Bowl ad airs. Walk through your funnel assumptions and justify each number.
  • Retail revenue has dropped. Walk through how you'd diagnose the problem and give specific example scenarios that could explain the decline.

“I started with total viewership and worked down through awareness, site visits, and finally registration conversion.”

View Post

Coinbase·Software Engineer·Onsite - System Design / Architecture

Jul 2026
Coinbase system design round for a software engineer role. The whole session was basically one big question about frequency tracking at scale, and they kept pulling the thread on every answer I gave.
  • Design a data structure that handles a high-volume stream of events (like account IDs from new account openings) and supports inserting items, querying the current top-K most frequent items, and optionally querying top-K over a sliding time window. Walk through your algorithm choices, complexity tradeoffs, and how you'd scale this across a distributed system.

“This was basically the entire interview compressed into one question.”

View Post