PracHub
QuestionsPremiumLearningGuidesCheatsheetNEWCoaches
|Home/Software Engineering Fundamentals/Whatnot

Synchronize Shared Data Across Two Lists

Last updated: May 14, 2026

Quick Overview

This question evaluates state management, data synchronization across multiple views, handling of asynchronous data fetching with loading and error states, and maintaining a single source of truth for shared items in a mobile UI.

  • medium
  • Whatnot
  • Software Engineering Fundamentals
  • Software Engineer

Synchronize Shared Data Across Two Lists

Company: Whatnot

Role: Software Engineer

Category: Software Engineering Fundamentals

Difficulty: medium

Interview Round: Technical Screen

Build a small mobile app with two list screens that fetch and display data. Some items may appear in both lists. Each item has at least: - `id` - `title` - `status` - `updatedAt` Requirements: - Fetch initial data for both list screens from a mock API or repository. - Render both lists independently. - Allow the user to update an item from either list screen, such as changing its `status` or `title`. - If the same item appears in both lists, an update made in one list must be reflected in the other list without requiring a full app restart. - Handle loading and error states. - Avoid maintaining two inconsistent copies of the same item. - Be prepared to explain your state-management approach and how you would allocate time during a 45-minute implementation interview.

Quick Answer: This question evaluates state management, data synchronization across multiple views, handling of asynchronous data fetching with loading and error states, and maintaining a single source of truth for shared items in a mobile UI.

Whatnot logo
Whatnot
Jan 24, 2026, 12:00 AM
Software Engineer
Technical Screen
Software Engineering Fundamentals
0
0

Build a small mobile app with two list screens that fetch and display data. Some items may appear in both lists.

Each item has at least:

  • id
  • title
  • status
  • updatedAt

Requirements:

  • Fetch initial data for both list screens from a mock API or repository.
  • Render both lists independently.
  • Allow the user to update an item from either list screen, such as changing its status or title .
  • If the same item appears in both lists, an update made in one list must be reflected in the other list without requiring a full app restart.
  • Handle loading and error states.
  • Avoid maintaining two inconsistent copies of the same item.
  • Be prepared to explain your state-management approach and how you would allocate time during a 45-minute implementation interview.

Solution

Show

Comments (0)

Sign in to leave a comment

Loading comments...

Browse More Questions

More Software Engineering Fundamentals•More Whatnot•More Software Engineer•Whatnot Software Engineer•Whatnot Software Engineering Fundamentals•Software Engineer Software Engineering Fundamentals
PracHub

Master your tech interviews with 7,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.