Coinbase

Coinbase Software Engineer Interview Questions

102+ questions from real Coinbase Software Engineer interviews, reported by candidates.

102
Questions
6
Round Types
8
Topic Areas
2022-2026
Year Range

Round Types

Coding 50 OA 15 Phone Screen 5 Onsite 5 System Design 4 Recruiter 4

Top Topics

Questions

Query Pagination ## Problem Requirements Design a **transaction query system**. You need to build a tool that filters a list of financial transactions and shows the results in pages. The interviewer

In-Memory Database ## The Challenge You need to build an **in-memory key-field-value database**. Think of this like a nested HashMap. Each "key" holds a collection of "field-value" pairs. You will b

I recently appeared for Coinbase Interviews and wanted to share my experience. OA: Leetcode easy/medium questions. I don\'t remeber the questions correctly but they were straightforward with each part building on...

Had a bad interview experience at coinbase for the well-known reason (offer cancelled). Sharing the interview answers here. Iterater question and follow ups: class Iterater: def __init__(self, start, end, step): self.lst...

### Generate Random NFT You need to generate a random NFT dataset. Each NFT is uniquely identified by a string and there are no duplicates. Given an integer n, return a list of n unique NFTs. **Inpu

Had a 1 hr online assessment with coinbase for senior sde role. The level of complexity was insane. 1 question, design a game with autopilot enabled where the character passes through all the obstacle

I couldn't finish the IQ questions. I almost fell asleep while answering the personality questions. The coding questions were very similar to those at https://www.1point3acres.com/bbs/thread-1144645-1

I felt I tried very hard in the interview but still failed. Maybe I wasn't good enough. I interviewed with the Finhub team. BQ Round: Standard behavioral questions. They asked three questions: conflic

This post was last edited by Anonymous on 2025-9-30 14:56 The following content requires a score higher than 100. You can already view it. Coding 1: Log Filter I didn't finish answering the 3 question

The exam was on cloud storage systems, 90 minutes long, 4 levels. Level 1: Simple `add file(name, size)`, `copyFile(from, to)`, `getFileSize(name)`, `removeFile(name)`. The following content requires

The OA interview experience is here: https://www.1point3acres.com/bbs/thread-1145841-1-1.html The VO interview was with the FinHub team under the platform, a total of 4 rounds, spread over 2 days. Bot

System Design: Crypto Exchange Order System **Goal:** Design an order system for a crypto broker like Coinbase. This system sends user buy/sell orders to other exchanges (like Binance or Kraken). It

Mining Block ## Understanding the Problem In blockchain systems, miners pick transactions to put into a block. A block has a specific size limit (capacity). Each transaction has a specific size and

Task Management System ## System Overview You need to build a **task management system**. You will start with a simple version and add more features in four steps. Each task has three parts: 1. `tas

Cloud File System ## The Challenge Design an **in-memory cloud file system**. You need to handle files, search for them, manage user storage limits, and save backups. You will build this system in f

Recipe Manager Interview Question ## Problem Overview You need to build an **in-memory recipe management system**. The system must handle creating, reading, updating, and deleting (CRUD) recipes. Yo

System Design: Coinbase Explore Realtime Market Data Design the backend for [Coinbase Explore](https://www.coinbase.com/explore). This page displays a list of crypto assets. It shows realtime price

Food Delivery System ## Problem Summary You need to build a **food delivery system**. This system manages restaurants, menus, and user orders. It helps users find the cheapest food and the nearest r

Log File Parser ## Problem Overview The goal of this problem is to read a log file with a specific structure. You need to organize the log entries by their thread ID and filter them by time. This te

Interleave Iterator ## Overview In this problem, we will build a system to mix (interleave) numbers from different sources. We will do this in three steps: 1. Write a simple function to mix arrays.

What Coinbase Looks for in Software Engineer Interviews

Coinbase Software Engineer interviews are calibrated against the level and scope expected of the role. Across 102+ verified candidate reports on LeakCode, the consistent signals interviewers look for: clear problem decomposition before coding, explicit complexity reasoning, structured handling of edge cases, and the ability to articulate trade-offs between two reasonable approaches.

The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the solution. It is the path to the solution: did you ask clarifying questions, did you state your approach before coding, did you handle edge cases without prompting, and did you communicate your reasoning throughout. Reports tagged "no hire" frequently cite a working solution with poor communication; reports tagged "strong hire" cite clear thinking even when the final solution was incomplete.

How To Use This Question Set

Real interview reports are a calibration tool, not a memorization target. Companies update their question pools every 2-4 months; memorizing exact problems risks misleading you when the interviewer uses a variant. The high-leverage use: identify the patterns that appear repeatedly in Coinbase Software Engineer reports, practice those patterns on similar (not identical) problems, and use the reports to understand the interviewer's typical follow-up depth.

Filter the questions below by round type, difficulty, and recency. Focus first on reports from the past 6-12 months; older reports may reference questions that have since rotated out of Coinbase's pool. Reports tagged with quantified difficulty (e.g., "medium-hard") are higher-signal than reports without difficulty tags.

Round-by-Round Expectations

Coinbase Software Engineer loops typically span 4-6 rounds across phone screens and on-site or virtual on-site interviews. The structure varies by company: some run 1 recruiter screen + 1 technical phone + 3-4 on-site rounds; others run 1 recruiter screen + 1 OA + 4-5 on-site rounds. The recruiter screen is logistics and culture-light; the technical phone screen is medium-difficulty coding; the on-site loop covers coding, system design (at L4+ levels), and behavioral rounds.

Each round is designed to surface a specific signal. Coding rounds: correctness, code quality, complexity reasoning, communication. System design rounds: requirements clarification, design judgment, operational thinking. Behavioral rounds: ownership scope, leadership, ambiguity tolerance, conflict navigation. Strong candidates explicitly hit each signal dimension out loud during the round; weak candidates focus only on solving the prompt.

Common Interview Mistakes At This Combination

Reports tagged "no hire" at Coinbase Software Engineer commonly cite: jumping into code without clarifying requirements, coding silently for 10+ minutes without verbalizing approach, missing edge cases (empty input, single element, very large input, overflow), and producing a working solution that the candidate cannot explain or refactor when probed. Strong candidates avoid these patterns by following a consistent template: clarify, verbalize approach, code with narration, test with examples.

Behavioral and design rounds have their own failure modes. Behavioral: stories that use "we" instead of "I" diluting individual signal, stories with no quantified outcome, defensiveness when probed about failure. Design: not asking clarifying questions, not stating requirements out loud, designing for a single server when the prompt clearly implies scale, ignoring operational concerns (deployment, monitoring, rollback). These show up in roughly half of Coinbase Software Engineer interview retrospectives on LeakCode.

See All 102 Coinbase Software Engineer Questions

Full question text, answer context, and frequency data for subscribers.

Get Access