InterviewStack.io LogoInterviewStack.io

Data Management and API Design Questions

Designing how applications structure, expose, and consume data through APIs and backend systems. Covers API design principles for data endpoints, pagination, filtering and sorting, idempotency, versioning, rate limiting, schema design, normalization versus denormalization, consistency models, caching strategies, client side fetching patterns, and error handling. Includes considerations for data integrity across integrations, transactional boundaries, master data management, and how API decisions affect downstream consumers and performance.

MediumTechnical
36 practiced
Implement an in-memory idempotency key store in Python with methods put(key, response, ttl_seconds) and get(key). It must be thread-safe, support TTL-based eviction (lazy or periodic), and return the previous response if the same key is seen. Provide considerations for concurrency and extension to multi-process deployments.
EasyTechnical
36 practiced
Describe the trade-offs between normalization and denormalization when designing a database schema for API-backed services. For a read-heavy analytics endpoint that aggregates user actions, which approach would you choose and why? Discuss update complexity, storage cost, and query performance.
MediumSystem Design
42 practiced
Design a webhook delivery system that guarantees at-least-once delivery: include exponential backoff retry policies, a dead-letter queue for failing endpoints, HMAC signing of payloads, metrics on delivery success, and ways to avoid retry storms when downstream is overloaded.
HardSystem Design
48 practiced
Design a saga-based approach (or orchestration alternative) for a travel booking flow involving flight, hotel, and car reservations. Cover orchestrator responsibilities, compensation actions for each service, idempotency of saga steps, persistence of saga state, timeouts, and how to allow manual intervention in case of partial failures.
EasyTechnical
38 practiced
Compare authentication mechanisms used for APIs: API keys, OAuth2 (authorization-code and client-credentials), and JWTs. Discuss trade-offs in security, revocation, token rotation, and storage strategies for web and mobile clients.

Unlock Full Question Bank

Get access to hundreds of Data Management and API Design interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.