Build a User Management CRUD Flow with React and Next.js

Read the full interview experience this question came from →

Quick Overview

Build a complete React and Next.js user-management flow with validated CRUD endpoints. Cover authoritative responses, draft state, mutation failures, edit conflicts, and a clear path to search and pagination.

Build a User Management CRUD Flow with React and Next.js

Company: DoorDash

Role: Software Engineer

Category: Software Engineering Fundamentals

Difficulty: medium

Interview Round: Onsite

Implement a user-management interface with React and Next.js, including backend endpoints for creating, reading, updating, and deleting user records. Complete the basic UI-to-backend flow before extending it with search and pagination. ### Constraints and Clarifying Questions The data model may be simplified. Choose and state a minimal record schema, validation rules, persistence approach, and router style. Search and pagination are extensions rather than prerequisites for a working CRUD demonstration. This exercise's reported round did not allow AI assistance; do not assume generated code is required. ### What a Strong Answer Covers A coherent record contract, HTTP operations, server validation, form and list state, error handling, and verification of each mutation through a subsequent read. Explain the limitations of any in-memory demonstration store. ### Follow-up Questions - How would two clients avoid silently overwriting each other's edits? - How would search and pagination preserve a stable ordering?

Overview: Build a complete React and Next.js user-management flow with validated CRUD endpoints. Cover authoritative responses, draft state, mutation failures, edit conflicts, and a clear path to search and pagination.

Read the full DoorDash Software Engineer interview experience this question came from

DoorDash logo
DoorDash
Oct 27, 2026
mediumSoftware EngineerOnsiteSoftware Engineering Fundamentals
0
0

Implement a user-management interface with React and Next.js, including backend endpoints for creating, reading, updating, and deleting user records. Complete the basic UI-to-backend flow before extending it with search and pagination.

Constraints and Clarifying Questions

The data model may be simplified. Choose and state a minimal record schema, validation rules, persistence approach, and router style. Search and pagination are extensions rather than prerequisites for a working CRUD demonstration. This exercise's reported round did not allow AI assistance; do not assume generated code is required.

What a Strong Answer Covers Guidance

A coherent record contract, HTTP operations, server validation, form and list state, error handling, and verification of each mutation through a subsequent read. Explain the limitations of any in-memory demonstration store.

Follow-up Questions Guidance

  • How would two clients avoid silently overwriting each other's edits?
  • How would search and pagination preserve a stable ordering?