Coinbase Frontend Engineer interview questions

11 Frontend Engineers have shared notes from their Coinbase interviews, with the questions they were asked in each round. That is 14% of the 78 Coinbase interview notes on Screna AI.

11 Frontend Engineer interview notes

Coinbase·Frontend Engineer·Take-home Assignment

Jun 2026
Coinbase frontend take-home that looked manageable on paper but had enough moving parts to trip you up if you underestimated the scope. The prompt was well-written at least, no ambiguity about what they wanted.
  • Build a list component app with API data fetching, per-item reordering controls, loading/error states, and proper request cancellation on unmount or overlapping calls.
  • Implement 'up' and 'down' reordering controls per list item, with the boundary items' controls disabled, and use stable keys throughout.
  • Write unit and component tests covering rendering, data fetching behavior, reordering logic, and edge cases.
  • Structure the app with clear separation between data-fetching logic and presentation components, and ensure accessibility including keyboard navigation, aria labels, and focus management.

“The request cancellation piece is where I spent way too long.”

View Post

Coinbase·Frontend Engineer·Technical Phone Screen

May 2026
Coinbase frontend round that was heavier on architecture thinking than I expected. They gave me a blog app scenario and basically wanted me to defend every state management decision out loud.
  • You have a list of posts with like counts and like timestamps. How do you sort them descending by likes, breaking ties by most recent timestamp, and where does that logic live in your component tree?
  • How do you handle deleting a post from local state when there might be an in-flight fetch still pending for that same data?
  • What keying strategy do you use for a dynamically sorted and filtered list, and why does it matter here specifically?
  • After a post is added or deleted, how do you ensure the sort order stays correct without re-fetching everything from the API?

“I went straight to sorting on render and they pushed back almost immediately.”

View Post

Coinbase·Frontend Engineer·Take-home Assignment

May 2026
Take-home exercise for a frontend role at Coinbase. Build a reorderable list component with accessibility requirements. Pretty scoped but the a11y piece had more surface area than I expected.
  • Build a list UI component in a framework of your choice that lets users reorder items using per-item up and down controls, with proper empty-state handling and stable item identity across re-renders.
  • Ensure the reorderable list is fully accessible: keyboard operable, with appropriate aria-labels and focus management after each reorder action.

“The swap logic itself was straightforward, just slice and reassign.”

View Post

Coinbase·Frontend Engineer·Technical Phone Screen

May 2026
Did a frontend technical round at Coinbase where they asked me to build a dropdown component from scratch. Interesting exercise but the scope conversation was more important than the actual code.
  • Build a reusable dropdown component. Walk through your design decisions and what a production-ready version would require.

“The coding part is almost secondary here.”

View Post

Coinbase·Frontend Engineer·Take-home Assignment

May 2026
Coinbase frontend take-home where you build a list component that fetches from an API. Sounds straightforward but the race condition and cleanup requirements are where they're really testing you.
  • Build a reusable list UI component in a frontend framework of your choice that fetches its data from an HTTP API on mount, supports manual refresh, and handles loading and error states.
  • How do you handle race conditions from overlapping fetch requests, and ensure a component unmounting mid-request doesn't cause stale state updates?

“The basic rendering part took maybe 30 minutes.”

View Post

Coinbase·Frontend Engineer·Take-home Assignment

May 2026
Take-home assignment for a frontend role at Coinbase. Pretty straightforward brief: build a small React app that pulls from a local JSON file and renders blog posts. Nothing wild, but the emphasis on component structure made me second-guess my folder layout more than I expected.
  • Build a small React application that reads blog post data from a local JSON file and displays a list of posts, each showing its title and body. Pay attention to component structure and basic styling.

“I spent way too long debating whether to split things into a PostList and PostItem component or just keep it flat.”

View Post

Coinbase·Frontend Engineer·Technical Phone Screen

May 2026
Coinbase frontend round, basically a live coding exercise where you extend a small blog app. Pretty focused scope but there's more to think about than it looks.
  • You're given a small blog app that loads posts from a local JSON file. Add a text area so users can write and submit a new post, and make sure the new post shows up in the list immediately without a page reload.

“Seemed straightforward at first and then I started second-guessing my component structure.”

View Post

Coinbase·Frontend Engineer·Onsite - System Design / Architecture

May 2026
Did a domain deep dive round for a frontend role at Coinbase where you present a past project while drawing diagrams live. The scope you pick matters a lot, probably more than I expected going in.
  • Walk us through a previous project you worked on, presenting your design decisions while drawing out diagrams in real time.

“The thing nobody tells you is that the project you pick makes or breaks the whole thing.”

View Post

Coinbase·Frontend Engineer·Take-home Assignment

Apr 2026
Take-home exercise for a frontend role at Coinbase. Pretty standard list component build but the requirements around extensibility and clean API design made it more interesting than I expected.
  • Build a reusable list UI component that renders an array of items, handles an empty state, exposes a clean prop-based API with optional callbacks, and is structured to support future API-driven data and reordering.

“The empty state and stable keys stuff felt easy but I spent way too long second-guessing the public API shape.”

View Post

Coinbase·Frontend Engineer·Technical Phone Screen

Apr 2026
Coinbase frontend interview that centered on a React data-fetching problem. The question sounded straightforward but had enough moving parts to trip you up if you weren't thinking about performance from the start.
  • You're building a blog app that fetches posts and users from separate API endpoints. Each post has an authorId. How do you 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 while the data is in flight?
  • How do you avoid N+1 API lookups when resolving author names for a list of posts?

“My first instinct was to fetch users inside the post render loop, which is the exact wrong move.”

View Post