Coinbase Interview Questions — Page 6

Coinbase·Software Engineer·Technical Phone Screen

May 2026

Coinbase software engineer interview that went deep on extending a toy bank system. The problem starts simple enough but the follow-up questions about scheduling and cancellation are where things get interesting.

You're given an in-memory bank system with basic operations already implemented. Extend it to support scheduled transfers: a way to queue a transfer for a future timestamp, and a way to cancel one that hasn't fired yet. Walk through your design.
What happens if the source account doesn't have enough funds at the time the scheduled transfer actually executes?
How do you handle calling cancelScheduled on a transfer that has already executed?
How do you ensure tick is idempotent, meaning calling it multiple times with the same timestamp doesn't re-apply transfers?

“The core part wasn't bad.”

View Post

Coinbase·Software Engineer·Onsite - System Design / Architecture

May 2026

Coinbase system design round for a Software Engineer role, focused entirely on building a comment component in React. The scope was way broader than I expected, covering everything from pagination to optimistic UI to accessibility to live chat scenarios.

Design and implement a reusable React comment component that supports submitting new comments and deleting existing ones.
How would you implement backend-driven pagination with infinite scroll? Walk through scroll detection, deduplication of requests, detecting end-of-list, and empty state handling.
How do you model and surface the different loading and error states in this component, such as initial load, loading more, submitting, and deleting?
What strategies would you use to prevent duplicate comment submissions, both on the client and server side?
Describe how you'd implement optimistic UI for posting and deleting comments, including rollback on failure and conflict resolution.
How would you make this component work in two very different contexts: a standard video details page and a high-throughput live chat or danmaku feed? What changes in terms of architecture, state management, and performance?
What accessibility considerations apply to this component, and how would you approach testing it across unit, integration, and mocked network layers?

“Seemed like the easy warmup but they kept pushing on the interface design.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

May 2026

Coinbase backend interview focused on a meaty pagination problem in Java. The question had enough layers to it that you could spend the whole session just on the core design, and then they still hit you with a follow-up on cursor-based vs offset approaches.

Implement a pagination system in Java for a query result set. Given a data source (possibly a streaming or aggregation query) and a page size, support fetching results page by page with stable ordering, consistent behavior when the underlying data shifts, and without loading everything into memory at once.
Extend your pagination solution to work over a derived or aggregated query. Then discuss the trade-offs between offset-based and cursor-based pagination.

“This is the kind of question that looks manageable until you actually think about ties in the sort order.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

May 2026

Coinbase software engineer interview with a multi-part in-memory database design problem. The question kept growing with each layer and I felt like I was always one step behind the requirements.

Design and implement an in-memory key-record store where each record maps string fields to integer values. Support set, get, and delete operations, where deleting the last field in a record removes the record entirely.
Extend the database to track how many times each key has been referenced across all operations, then implement a topN function that returns the N most-accessed keys, breaking ties alphabetically.
Add user-aware locking to the database: any user can modify an unlocked key, but once a key is locked by a specific user, only that user can make changes. Implement set, delete, lock, and unlock operations that respect this constraint.

“The basic CRUD layer felt straightforward and I got through it fine.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

May 2026

Coinbase coding screen where they had me build a recipe management system from scratch, data model and all. Pretty straightforward if you know your hash maps, but designing the model yourself adds a wrinkle most people don't expect.

Design and implement a recipe management system supporting add, update, get, and delete operations. You define the data model yourself and should aim for O(1) time complexity where possible.

“The CRUD part was fine, a hash map keyed by recipe id and you're basically done.”

View Post

Coinbase·Software Engineer·Recruiter / HR Screen

May 2026

Reached out with some questions about a software engineer role at Coinbase and ended up going deep on recruiter communication stuff, specifically around whether to disclose job changes and what background checks actually catch.

Should you proactively tell a recruiter if you recently left a job, or wait until they ask?
How do background checks verify your employment history, and what happens if something doesn't match what you told the recruiter?
How do you professionally bring up an employment gap or a performance improvement plan during the hiring process without tanking your chances?

“I went back and forth on this.”

View Post

Coinbase·Data Scientist·Technical Phone Screen

May 2026

Coinbase DS interview with a product estimation problem centered on a real-world scenario. Pretty open-ended, which I wasn't fully ready for. The QR code angle made it feel more grounded than a typical 'estimate X users' question.

A Coinbase Super Bowl ad shows a QR code linking to a promo. Estimate how many viewers actually scan and use it. Walk through your assumptions, any data sources you'd reference, and the full calculation.

“I started with Super Bowl viewership (around 100M) and worked down through layers: who has a phone out, who's actually paying attention during the ad, who bothers to scan, and who completes the promo.”

View Post

Coinbase·Product Manager·Onsite - Product Sense / Strategy

May 2026

PM interview at Coinbase, product sense round. Single design question, pretty focused on crypto-specific context which I wasn't fully prepared for.

How would you design price alert notifications for the Coinbase app?

“I went straight into the notification mechanics and missed the forest for the trees.”

View Post

Coinbase·Software Engineer·Technical Phone Screen

May 2026

Coinbase technical phone screen for a software engineer role, one meaty algorithmic problem that took up most of the time. The problem looked like a knapsack variant but with dependency constraints baked in, which made it way more interesting than a standard DP warmup.

Given a set of transactions each with a size and fee, where some transactions have parent dependencies forming a forest of trees, select a subset that fits within a block-size budget and maximizes total fee while respecting parent-before-child ordering.

“My first instinct was tree DP, which is technically correct but I fumbled explaining the complexity.”

View Post

Coinbase·Product Manager·Onsite - Product Sense / Strategy

May 2026

PM screen at Coinbase with a product sense question borrowed straight from Facebook's playbook. Pretty classic case framing but the metrics angle made it trickier than it looked.

Facebook is thinking about adding a seventh reaction to its existing set. How would you decide whether it's actually needed, and how would you measure whether it succeeded after launch?

“I went straight for user need segmentation and probably spent too long on that before getting to metrics.”

View Post