← Coinbase Interview InsightsFrontend Engineer

Coinbase·Frontend Engineer·Take-home Assignment·Intermediate

IntermediatePrefer not to say
Apr 2026Remote

Summary

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.

Questions Asked (1)

Q1

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.

Technical Trade-offsSystem DesignAPI & Integrations
Author's notes

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

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and constraints, then outline a component API that separates presentation from data fetching. Describe the component structure, including empty state handling and optional callbacks, and explain how it can be extended for future API-driven data and reordering. Emphasize trade-offs and design decisions that support scalability and maintainability.

Pro tip: Demonstrate foresight by discussing how you would handle asynchronous data loading and state management without over-engineering, and mention specific patterns like render props or hooks that align with Coinbase's React-based stack.

1. Clarify Requirements and Constraints

Ask questions to understand the expected data shape, performance needs, and integration points. Confirm whether the component should be controlled or uncontrolled, and how reordering should be triggered.

2. Define the Component API

Specify props such as items, renderItem, onItemClick, emptyState, and onReorder. Ensure the API is intuitive and allows for future extensions like loading states or pagination.

3. Design the Component Structure

Outline the component hierarchy, including a container for state management and a presentational list. Describe how to handle empty state and optional callbacks without cluttering the main logic.

4. Plan for Future Extensibility

Explain how to abstract data fetching (e.g., using hooks or HOCs) and integrate reordering (e.g., via drag-and-drop libraries) without rewriting the component. Discuss separation of concerns.

5. Discuss Trade-offs and Testing

Highlight trade-offs between flexibility and simplicity, and mention testing strategies for empty state, callbacks, and reordering. Emphasize accessibility and performance considerations.

Key Points to Mention

  • Prop-based API design with clear naming and TypeScript interfaces for type safety
  • Empty state handling with customizable fallback UI
  • Optional callbacks like onItemClick and onReorder for flexibility
  • Separation of data fetching from presentation using hooks or container components
  • Integration with drag-and-drop libraries for reordering (e.g., react-beautiful-dnd)
  • Accessibility considerations (ARIA roles, keyboard navigation) and performance optimizations (virtualization for large lists)

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.