Coinbase Frontend Engineer Interview Questions

Coinbase·Frontend Engineer·Onsite - System Design / Architecture

Jul 2026

Staff-level frontend interview at Coinbase centered around a deep technical presentation of a past project. You draw an architecture diagram live and walk through it with senior engineers asking follow-ups the whole way. Pretty intense if your project doesn't have enough meat on it.

Walk us through a past project you owned, including the business problem, your architecture decisions, and the measurable impact you delivered.
What were the major technical tradeoffs you made during the project, and would you make the same calls again?
Describe a significant failure, incident, or constraint you hit during the project and how you handled it.
How did you collaborate with other teams, and how did you handle disagreements or misaligned priorities?
If you could redo this project from scratch, what would you change about the architecture or your approach?

“This is basically the whole interview.”

View Post

Coinbase·Frontend Engineer·Take-home Assignment

Jun 2026

Coinbase sent over a take-home for a frontend role, basically a full mini-app with a reusable list component, API fetching, reordering controls, tests, accessibility, the works. More involved than I expected for a take-home but it was a pretty clear spec at least.

Build a list component app in React, Vue, or Angular that fetches items from an API on mount and on demand, handles loading and error states, and prevents stale responses from overwriting newer state when requests overlap or the component unmounts.
Implement per-item up/down reordering controls that swap an item with its neighbor, with the first item's up and last item's down disabled. Use stable keys to preserve item identity across renders.
Write unit and component tests covering rendering, data fetching, reordering behavior, and edge cases like empty state and boundary items.
Structure the app with clear separation between data fetching logic and presentation components, and ensure the UI is accessible (keyboard navigable, proper aria-labels, focus management) and responsive.

“The abort/cleanup part is where I spent most of my time.”

View Post

Coinbase·Frontend Engineer·Technical Phone Screen

Jun 2026

Coinbase frontend round where they gave me a partially built React blog app and asked me to wire up a form for adding new posts. Pretty focused exercise, more about clean state management than anything algorithmic.

You're given a React app that displays a list of blog posts loaded from a local JSON file. Add a textarea that lets users write and submit a new post, appending it to state so the list updates immediately without a page reload.

“The core of it was keeping the textarea as a controlled input and making sure the list re-rendered from the same state slice rather than some parallel array.”

View Post

Coinbase·Frontend Engineer·Onsite - System Design / Architecture

Jun 2026

System design round at Coinbase for a frontend engineering role. The whole thing was centered on designing a production-grade trading UI, which sounds scoped but actually opens up into a pretty sprawling conversation across state management, real-time data, security, and more. Came away feeling like I covered the basics but probably left some depth on the table.

Design the frontend architecture for a production trading system UI, covering areas like market charts, order book, trade history, order entry, balances, open orders, and execution status.
What framework and rendering strategy would you choose for this trading UI, and why?
How would you manage state across all the different panels in a trading interface?
How would you handle real-time data flowing into the UI from the backend, for things like live price feeds and order book updates?
How would you approach error handling and loading states across the different sections of the trading UI?
What performance and reliability considerations matter most in a frontend trading system?
What security concerns are specific to a trading UI and how would you address them on the frontend?
How would you approach testing and observability for this kind of frontend system?

“This is the kind of question where you feel okay for the first five minutes and then realize how many angles they can pull on.”

View Post

Coinbase·Frontend Engineer·Take-home Assignment

May 2026

Coinbase frontend take-home that looked straightforward on paper but had a few gotchas buried in the requirements. The core task was building a list component that fetches from an API, but the real test was whether you'd handle the edge cases properly.

Build a reusable list UI component (React, Vue, or Angular) that fetches its data from an HTTP endpoint on mount and on demand, with loading, error, and empty states, stable keys, and correct handling of race conditions and unmount cleanup.

“The empty state and loading spinner are the easy part.”

View Post

Coinbase·Frontend Engineer·Technical Phone Screen

May 2026

Coinbase frontend round focused almost entirely on one meaty React/state-management problem. It felt less like a coding screen and more like a design discussion with code attached, which I wasn't fully prepared for.

You're building a blog app that pulls posts and users from separate APIs. Each post has a like count and a most-recent-like timestamp. How do you sort posts by likes descending, breaking ties by recency, and keep that order correct after adds and deletes?
For posts authored by the current logged-in user, how would you render a delete button that removes the post from local state while maintaining correct sort order?
How do you handle keying in a dynamically sorted list to avoid rendering issues when items move positions?

“I jumped straight into useMemo and felt pretty good about it, but they pushed back asking whether I'd just sort on every render instead.”

View Post

Coinbase·Frontend Engineer·Take-home Assignment

May 2026

Take-home assignment for a frontend role at Coinbase. Build a list component with empty state, a clean prop API, and enough styling to not look embarrassing. Pretty scoped exercise but there are a few details that can trip you up if you're not thinking about extensibility.

Build a reusable list UI component that renders an array of items, handles an empty state, exposes a clean prop API with optional callbacks, and is structured to support future API-driven data and reordering.

“The empty state tripped me up more than I expected.”

View Post

Coinbase·Frontend Engineer·Take-home Assignment

May 2026

Take-home OA for a frontend role at Coinbase. The task was to build a reorderable list component with up/down controls, accessibility requirements, and proper state/event handling. Pretty scoped but there were enough edge cases to trip you up if you weren't careful.

Build a reorderable list UI component in a frontend framework of your choice. Each item should have up/down controls that swap it with its neighbor, with the boundary items' controls disabled. The component should handle empty state, emit change events to the parent, use stable keys for item identity, and meet accessibility standards including keyboard support and focus management.

“The swap logic itself is trivial, like three lines.”

View Post

Coinbase·Frontend Engineer·Onsite - System Design / Architecture

May 2026

System design round at Coinbase for a frontend engineer role, entirely focused on building a crypto trading platform from scratch. It was one of the more exhaustive design interviews I've done, covering everything from component APIs to WebSocket throttling strategies.

Walk through your tech stack choices for a cryptocurrency trading platform: framework, state management, build tooling, and styling. Why those choices?
How would you structure the pages of the platform? Think market overview, trading pair detail, portfolio and open orders, and account pages.
Break down the reusable components you'd build: price ticker, order book panel, candlestick chart, order form, toast/alert system, and a virtualized trade history table. For each, describe the props API and implementation approach.
How do you handle real-time data from WebSockets in a frontend app? Cover subscription management, throttling or batching updates to avoid frame drops, and optimistic UI for order submission.
What cross-cutting concerns would you design for across the whole platform? Things like theming, internationalization, accessibility, error states, and authenticated vs guest views.
Deep dive: how would you implement the order book panel specifically to handle hundreds of price level updates per second without degrading performance?

“I went with React plus Zustand for state because Redux felt like overkill to justify in real time.”

View Post

Coinbase·Frontend Engineer·Technical Phone Screen

Apr 2026

Coinbase frontend round, one meaty coding question about building a blog app that pulls from two APIs and stitches the data together client-side. More design discussion than I expected for a frontend screen.

You're building a blog app in React. Posts come from a GET /posts endpoint and include an authorId. Users come from a separate GET /users endpoint. How do you fetch and render each post with the correct author name, and show 'you' for posts belonging to the logged-in user?
How would you cache the users list, and what's your approach to loading and error states for both API calls?

“I jumped straight into fetching both endpoints in parallel with Promise.all, which felt right, then building a lookup map from userId to display name before rendering.”

View Post