← Coinbase Interview InsightsFrontend Engineer

Coinbase·Frontend Engineer·Technical Phone Screen·Senior

SeniorPrefer not to say
May 2026

Summary

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.

Questions Asked (1)

Q1

Build a reusable dropdown component. Walk through your design decisions and what a production-ready version would require.

System DesignTechnical Trade-offsAPI & Integrations
Author's notes

The coding part is almost secondary here.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and constraints (e.g., single vs multi-select, accessibility, theming) before diving into design. Then walk through the component architecture, covering API design, state management, and extensibility. Finally, discuss production concerns like accessibility, performance, testing, and integration with design systems.

Pro tip: Emphasize accessibility from the start—mention ARIA roles, keyboard navigation, and focus management—as this is often overlooked and highly valued at companies like Coinbase. Also, tie decisions to real-world trade-offs (e.g., controlled vs uncontrolled components) to show senior-level thinking.

1. Clarify Requirements and Constraints

Ask questions to understand the expected use cases, such as single/multi-select, search, grouping, and whether it needs to be controlled or uncontrolled. Consider constraints like accessibility standards, theming, and integration with existing design systems.

2. Design the Component API

Define a clear and flexible API, including props for options, value, onChange, placeholder, and customization. Decide between controlled and uncontrolled patterns, and consider composition (e.g., using compound components) for extensibility.

3. Outline Implementation Details

Discuss state management (e.g., open/close, highlighted index, selected values), event handling (click, keyboard, blur), and rendering strategy (e.g., portal for dropdown menu). Mention performance optimizations like virtualization for large lists.

4. Address Accessibility and Internationalization

Detail how you would implement ARIA attributes (e.g., role='listbox', aria-activedescendant), keyboard navigation (arrow keys, Enter, Escape), focus trapping, and screen reader support. Also consider RTL support and localization.

5. Discuss Production-Readiness

Cover testing (unit, integration, visual regression), documentation, theming, and integration with design systems. Mention monitoring, error boundaries, and performance metrics. Also discuss versioning and backward compatibility.

Key Points to Mention

  • Accessibility: ARIA roles, keyboard navigation, focus management, screen reader support
  • Controlled vs uncontrolled component patterns and their trade-offs
  • Performance optimizations: virtualization, memoization, lazy loading
  • Extensibility: compound components, render props, or slots for custom rendering
  • Testing strategy: unit tests with React Testing Library, integration tests, visual regression
  • Integration with design systems and theming (e.g., CSS-in-JS, CSS variables)

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