Design a payment ledger with idempotent operations — Freshworks interview
Reported in Freshworks interview loops. Critical design topic focused on correctness under retries and failures.
Interview atlas
Explore 1,385 curated Q&As across 124 employers — filter by career stage, round, or company.
Reported in Freshworks interview loops. Critical design topic focused on correctness under retries and failures.
Reported in Freshworks interview loops. System design interview around indexing, ranking, and freshness.
Reported in Freshworks interview loops. System design problem testing reliability, fan-out, and channel abstraction.
Reported in Ola interview loops. Object model design for template rendering and channel-specific formatting.
Reported in Ola interview loops. System design topic around edge caching, invalidation, and latency.
Reported in Ola interview loops. System design exercise emphasizing control plane and low-latency reads.
Reported in Ola interview loops. Observability architecture interview question for platform roles.
Reported in Ola interview loops. Critical design topic focused on correctness under retries and failures.
Reported in Ola interview loops. System design interview around indexing, ranking, and freshness.
Reported in Ola interview loops. System design problem testing reliability, fan-out, and channel abstraction.
Reported in Razorpay interview loops. Object model design for template rendering and channel-specific formatting.
Reported in Razorpay interview loops. System design topic around edge caching, invalidation, and latency.
Reported in Razorpay interview loops. System design exercise emphasizing control plane and low-latency reads.
Reported in Razorpay interview loops. Observability architecture interview question for platform roles.
Reported in Razorpay interview loops. Critical design topic focused on correctness under retries and failures.