Coinbase Interview Questions — Page 14

Coinbase·Software Engineer·Online Assessment (OA)

Jun 2026

Coinbase sent me an OA-style problem that was way more interesting than the usual leetcode grind. You're basically building a Flappy Bird agent that has to decide frame-by-frame whether to jump, which sounds fun until you're staring at physics constants and pipe gap windows trying to not overthink it.

Implement a Flappy Bird agent class with a method that decides each frame whether the bird should jump, using forward simulation and safety margins to avoid pipes and screen boundaries.

“My first instinct was to just hardcode some threshold on the bird's y-position relative to the pipe gap center, which technically works but falls apart on edge cases near the floor.”

View Post

Coinbase·Data Scientist·Technical Phone Screen

Jun 2026

Probability question for a Data Scientist role at Coinbase, focused on a wallet risk scenario. Pretty conceptual, not a lot of coding involved.

What statistical assumption must hold for you to multiply individual event probabilities together to get the combined probability of all events occurring?

“The answer is independence, which I knew, but the way it was framed around a real wallet risk scenario made me second-guess myself for a second.”

View Post

Coinbase·Software Engineer·Online Assessment (OA)

Jun 2026

Coinbase SWE online assessment on CodeSignal, a four-level task scheduler problem where each level adds new requirements on top of the last. The kind of OA where you can't just brute-force your way through because the later levels assume your earlier code is solid.

Design and implement a multi-level task scheduler: starting with basic add, get, and cancel operations, then layering in prioritization and listing, then user assignment with quotas, and finally completion tracking with overdue detection.

“Four levels, each building on the previous.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jun 2026

Interviewed at Coinbase for what seemed like a backend or infrastructure-adjacent role. One question about network signal propagation, which felt like it was testing systems thinking more than anything else.

How long does it take for a signal to propagate from one computer to every other computer in a network?

“I went straight to broadcast latency and started talking about network topology.”

View Post

Coinbase·Software Engineer·Onsite - System Design / Architecture

Jun 2026

Coinbase system design round focused entirely on a real-time streaming problem around branch account openings. Pretty intense for a single question but they kept pushing on edge cases and distributed extensions the whole time.

Given a stream of account-opening events with branch ID, user ID, and timestamp, design a system to compute the top-K branches by number of openings for both all-time and a sliding window of the last T minutes. The system should support near real-time ingestion, queries at any time, and updates in O(log K) or better. Also address late or out-of-order events, memory constraints, and trade-offs between exact and approximate methods. Extend to a distributed setup and analyze complexity.

“This was the whole interview, basically.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jun 2026

Coinbase SWE interview built around an in-memory file system problem split into four progressive parts, each unlocking only after you pass all test cases for the previous one. The structure is clever but unforgiving if you paint yourself into a corner early.

Design and implement an in-memory file system across four progressive parts: starting with basic file and directory creation plus read/write, then directory listing with sorted output and recursive mkdir, then move and delete with correct path semantics, and finally advanced features like hard links, snapshots, permissions, or file-size queries by prefix.

“The gating mechanic tripped me up more than the actual coding.”

View Post

Coinbase·Data Scientist·Technical Phone Screen

Jun 2026

Coinbase data scientist interview with a probability-focused statistics problem. Three parts, escalating in difficulty, and the conditional expectation at the end was where things got interesting.

Given n users who each independently use a feature with probability p, what is the probability that at least one user uses the feature?
Given the same setup, what is the probability that a specific user (user 1) used the feature, conditional on knowing that at least one user used it?
As an extension: what is the expected number of users who used the feature, given that at least one user used it?

“Classic complement trick.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jun 2026

Coinbase SWE interview with a two-part coding problem around block mining and transaction selection. The dependency constraint part was the real test and I felt underprepared for the graph angle it took.

You're building a block from a transaction pool. Given a block size limit, how do you select a subset of independent transactions that maximizes total fees?
Now each transaction can declare parent transactions as dependencies. A transaction can only be included in a block if all its ancestors are also included. How do you redesign the selection algorithm to respect these dependency constraints while still maximizing fees?

“Pretty standard knapsack framing once you see it.”

View Post

Coinbase·Product Manager·Hiring Manager Screen

Jun 2026

Prep material for a Coinbase PM interview covering the classic opening trio: background, motivation, and five-year plan. No outcome info shared, just a framework for thinking through answers before the real thing.

Tell me about yourself.
Why do you want to work at Coinbase specifically?
Where do you see yourself in five years?
Which Coinbase product or user journey would you most want to improve, and why?
What part of crypto or financial products do you think is hardest for mainstream users to trust?
What is a product lesson from a past role that you think transfers well to this kind of work?

“The tricky part isn't the question, it's resisting the urge to just read your resume out loud.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

Jun 2026

Coinbase software engineering interview that went pretty deep into a system design coding problem. It was one of those sessions where the question keeps growing the longer you talk, which I was not fully prepared for.

Given an in-memory banking system with accounts, deposits, transfers, spending tracking, and scheduled transfers, implement a mergeAccounts function that folds one account into another. Specifically: combine balances, carry over pending scheduled outflows and historical spending totals, close the source account so future operations on it fail, and return the resulting balance.
What should happen to in-flight scheduled transfers that referenced the account being closed during a merge? Should they be rewired to the surviving account or cancelled outright, and how do you keep all the underlying indexes consistent?

“The basic merge felt doable at first.”

View Post