← Coinbase Interview InsightsFrontend Engineer

Coinbase·Frontend Engineer·Technical Phone Screen·Intermediate

Intermediate
May 2026

Summary

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.

Questions Asked (1)

Q1

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.

Technical Trade-offsSystem DesignAPI & Integrations
Author's notes

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

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the requirements and constraints, then outline a component-based solution using controlled inputs and local state updates. Emphasize optimistic UI updates and discuss trade-offs between simplicity and scalability, such as when to introduce a backend or state management library.

Pro tip: Mention that you'd use a unique client-side ID (e.g., crypto.randomUUID()) for the new post to avoid key collisions and enable future features like editing or deletion. Also, discuss how you'd handle form validation and error states to ensure a smooth user experience.

1. Clarify requirements and constraints

Ask about the expected scale, whether posts need to persist across sessions, and if there are any design or library constraints. Confirm that the JSON file is static and the app is client-side only.

2. Design the component structure and state management

Decide where to hold the posts state (e.g., in a parent component) and how to pass down a callback to add a new post. Use controlled components for the textarea and form.

3. Implement the form and submission logic

Create a form with a textarea and submit button. On submit, validate the input, create a new post object with a unique ID and timestamp, and call the callback to update state.

4. Update the UI optimistically

Immediately prepend or append the new post to the local state so it appears in the list without a page reload. Optionally, simulate an API call and handle loading/error states.

5. Discuss trade-offs and next steps

Talk about the limitations of local-only updates (e.g., data loss on refresh) and how you'd evolve the solution with a backend, optimistic updates with rollback, or a state management library.

Key Points to Mention

  • Controlled components and form handling in React (or similar framework)
  • State management: lifting state up, using useState/useReducer, or context
  • Optimistic UI updates and reconciliation with server responses
  • Unique keys for list items to avoid rendering issues
  • Validation and error handling for user input
  • Trade-offs between local state and global state management solutions

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