← Commure Interview Insights

Commure·Frontend Engineer·Onsite - System Design / Architecture·Senior

SeniorPrefer not to say
May 2026

Summary

System design round at Commure for a frontend engineer role, which was a bit unexpected given the title. The question was deep on backend territory: payments, concurrency, booking state machines. Not a typical frontend interview.

Questions Asked (1)

Q1

Design a patient appointment booking system where users browse provider timeslots, select one, and pay through a third-party payment service. Cover the data model, concurrency handling, payment integration, booking lifecycle, and how you'd reconcile failures between booking state and payment state.

System DesignAPI & IntegrationsData Modeling
Author's notes

This was a lot to unpack.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and constraints, then walk through the high-level architecture and data model. Focus on the frontend perspective: how the UI handles concurrency, payment integration, and failure reconciliation. Emphasize user experience and state management.

Pro tip: Demonstrate awareness of real-world payment edge cases like double bookings and payment failures, and propose idempotency keys and optimistic UI updates with rollback to ensure a smooth user experience.

1. Clarify Requirements and Scope

Ask questions to understand user scale, payment provider, and real-time constraints. Define the core user flow: browse, select, pay, and confirmation.

2. Design Data Model and API

Outline entities like Provider, Timeslot, Booking, and Payment. Define RESTful endpoints for fetching timeslots, creating bookings, and processing payments.

3. Handle Concurrency and Booking Lifecycle

Discuss strategies like optimistic locking or temporary holds to prevent double bookings. Define booking states: pending, confirmed, cancelled, expired.

4. Integrate Payment and Reconcile Failures

Explain payment flow with third-party service, including idempotency and webhooks. Describe how to reconcile mismatches between booking and payment states.

5. Address Frontend Implementation

Detail UI state management, loading states, error handling, and optimistic updates. Ensure accessibility and responsiveness.

Key Points to Mention

  • Idempotency keys to prevent duplicate payments and bookings
  • Optimistic UI updates with rollback on failure for better UX
  • Webhook handling for asynchronous payment confirmation
  • Temporary timeslot holds to manage concurrency
  • Booking state machine (pending, confirmed, cancelled, expired)
  • Reconciliation strategies: periodic sync, manual resolution, and user notifications

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