How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a medium difficulty System Design question, commonly asked during Onsite rounds at Airtable.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at Airtable during technical interviews.

Design an async API with idempotency | Airtable Interview Question

Q: Design an async API with idempotency

This question evaluates a candidate's competency in designing asynchronous HTTP APIs with idempotency guarantees, focusing on job lifecycle, durable data models, messaging/queue behavior, and handling partial failures and retries.

System Design: Asynchronous API Call With Idempotency

Design an HTTP API that triggers a long-running operation (seconds to minutes) against downstream systems (e.g., charge a payment, generate a report, provision resources). The API must be asynchronous and must guarantee idempotency so that client retries do not duplicate work.

Requirements

Client calls an endpoint to start a job.
The request may be retried due to timeouts, network errors, or 5xx responses.
The system must not execute the operation more than once for the same logical request.
Provide a way for clients to check job status and fetch the result.

Considerations

High QPS, multiple instances, at-least-once delivery in messaging.
Partial failures (DB commit succeeds but enqueue fails, or vice versa).
Exactly-once semantics are not assumed.

Describe:

API endpoints and request/response shapes
Data model
Queue/worker flow
How idempotency is enforced (including edge cases and TTL)
Observability and operational concerns

System Design: Asynchronous API Call With Idempotency

Requirements

Client calls an endpoint to start a job.

The request may be retried due to timeouts, network errors, or 5xx responses.

The system must not execute the operation more than once for the same logical request.

Provide a way for clients to check job status and fetch the result.

Considerations

High QPS, multiple instances, at-least-once delivery in messaging.

Partial failures (DB commit succeeds but enqueue fails, or vice versa).

Exactly-once semantics are not assumed.

Describe:

API endpoints and request/response shapes

Data model

Queue/worker flow

How idempotency is enforced (including edge cases and TTL)

Observability and operational concerns

Design an async API with idempotency

Quick Overview

System Design: Asynchronous API Call With Idempotency

Requirements

Considerations

Solution

Comments (0)

Design an async API with idempotency

Quick Overview

System Design: Asynchronous API Call With Idempotency

Requirements

Considerations

Solution

Comments (0)