Coinbase Software Engineer Onsite Coding Questions
55+ questions from real Coinbase Software Engineer Onsite Coding rounds, reported by candidates who interviewed there.
What does the Coinbase Onsite Coding round test?
The Coinbase onsite coding round is the core technical evaluation. Software Engineer candidates typically see 2-3 algorithm and data structure problems. Problems range from medium to hard difficulty, and interviewers evaluate both correctness and code quality.
Top Topics in This Round
Coinbase Software Engineer Onsite Coding Questions
Generate Random NFT
### 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
Coinbase Onsite SDE2 Interview Experience at Finhub Team
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
Coinbase Fulltime SDE Onsite Interview Experience and Outcome
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
Coinbase Staff-Level Software Engineer Onsite Interview Experience
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
Coinbase | Phone | Buy and sell offer
Exactly the same as: https://leetcode.com/discuss/interview-question/1198505/Coinbase-or-Onsite-or-SWE-Reject A way for users to buy and sell stocks match buyers with the lowest seler (<= buyer\'s price) match sellers with the highest buyer (>= seller\'s price) But instead...
#528 Random Pick with Weight
LeetCode #528: Random Pick with Weight. Difficulty: Medium. Topics: Array, Math, Binary Search, Prefix Sum, Randomized. Asked at Coinbase in the last 6 months.
LeetCode #588: Design In-Memory File System. Difficulty: Hard. Topics: Hash Table, String, Design, Trie, Sorting. Asked at Coinbase in the last 6 months.
## Problem: Banking System Coding Exercise (Multi-Currency + History Replay Follow-ups) The post mentions a "banking system" problem with follow-ups for multiple currency types and history replay, bu
## Problem: NFT Coding Exercise (Implement Core NFT Operations + Write Tests) The post only states it is an "NFT" problem and that you must write your own tests, but it does not specify required oper
You are given a set of transactions (or blocks) to include in a block. Each transaction has: - `id` - `fee` - `size` - dependencies: some transactions have a parent; selecting a transaction requires s
Implement a jump-boundary / collision-detection function for a Flappy Bird–like game. Given: - The bird’s current position and velocity (or position only) - Obstacles (pipes) with their positions and
## Problem: In-Memory DB Variant — Add User-based locking You are implementing a simplified **in-memory database** storing `key -> record`. This variant introduces **users** and a **lock** mechanism
## Problem: In-Memory DB Variant — Track per-key operation counts and return Top N keys You are implementing a simplified **in-memory database** that stores data as `key -> record`. In this variant,
## Problem: Flappy-Bird-like Autopilot With Coins as Jump Budget You are given a simplified side-scrolling jumping game. You must implement a **policy** that decides whether to `jump` at each time st
## Drone Food Delivery: Simulate “Nearest Forward Station” and Compute Total Distance You need to simulate a drone delivery system that moves a package from position `0` to `target`. All positions li
## Problem You are generating NFT metadata. You are given `K` attribute categories (e.g., `Ears`, `Eyes`, `Hat`), each with a list of candidate values. ### Part A: Generate all combinations Generate
## Problem You are given `N` log lines (strings). Each line follows the format: ``` <timestamp> <thread_id> <level> <message> ``` - `timestamp`: an ISO-8601 time string, e.g. `2024-01-01T10:00:00Z`
Filter and Pagination
Implement an API that supports filtering and pagination. The API should return a data collection based on filter criteria and paginate the results by specified page number and items per page.
Pagination Problem
Given a collection of items, design a pagination function that displays `k` items per page, and return the list of items on the `n`th page. Assume there may be multiple pagination criteria, you need t
Design and implement a function to perform block mining on a given set of transactions. Each transaction has a unique ID and other necessary attributes. Implement two functionalities: one for independ
What to Expect in the Coinbase Onsite Coding Round
The Coinbase Software Engineer Onsite Coding round has a specific calibration purpose distinct from other rounds in the loop. Across 55+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.
Reports tagged with the Onsite Coding round at Coinbase show recurring patterns in difficulty and topic distribution. The Onsite Coding round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.
How To Prepare for This Specific Round
Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.
Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.
Onsite Coding Round Timing and Format
The Onsite Coding round at Coinbase typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.
Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.
Common Failure Modes in This Round
Reports tagged "no hire" at Coinbase Software Engineer Onsite Coding commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.
The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.
See All 55 Questions from This Round
Full question text, answer context, and frequency data for subscribers.
Get Access