Razorpay Kafka Interview Questions 2026
Published July 22, 2026 · Updated July 22, 2026
5 real Kafka interview questions asked at Razorpay. Upvoted by engineers who cleared the loop. Covers System Design, Technical rounds.
5 questions
189 engineers asked
262 upvotes
Company: Razorpay
Technology: Kafka
All Kafka Questions Asked at Razorpay
Razorpay
Hard
System Design round
KafkaRedisPostgreSQL
Design Razorpay's payment retry system.
When a payment fails due to a transient error (bank timeout, network blip), how do you retry safely without double-charging the customer?
Cover: idempotency keys, exponential backoff with jitter, dead-letter queues, and reconciliation with bank statements.
↑ 72 upvotes · 71 engineers asked this · SDE2
Razorpay
Hard
System Design round
KafkaPostgreSQLRedis
Design Razorpay's payout system (RazorpayX). Businesses send bulk payouts to thousands of vendor accounts simultaneously. Cover: batching, bank API rate limits, real-time status tracking, and failure handling.
↑ 61 upvotes · 39 engineers asked this · SDE2
Razorpay
Hard
Technical round
PostgreSQLJavaKafka
How do you implement a distributed ledger for financial transactions? Explain double-entry bookkeeping in code, why you never update a balance directly, and how you use event sourcing to reconstruct the current balance from a transaction log.
↑ 56 upvotes · 35 engineers asked this · SDE2
Razorpay
Hard
System Design round
KafkaRedisPostgreSQL
Design Razorpay's dashboard for merchants. A merchant wants to see real-time revenue, transaction success rates, and refund trends. How do you aggregate millions of transactions into live charts with under 5-second latency?
↑ 49 upvotes · 30 engineers asked this · SDE2
Razorpay
Medium
Technical round
3-6 yearsKafka
Kafka guarantees message order within a partition but not across partitions. For a payments system, why does this matter, and how would you key messages to preserve per-account ordering?
↑ 24 upvotes · 14 engineers asked this · SDE2
Practice these questions with AI feedback
Get instant grading on your answers, identify your weak areas, and generate a personalised 14-day study plan — all free.
Build my study plan →
Kafka Questions at Other Companies
Browse by company
Frequently asked questions
Design Razorpay's payment retry system.
Design Razorpay's payment retry system.
When a payment fails due to a transient error (bank timeout, network blip), how do you retry safely without double-charging the customer?
Cover: idempotency keys, exponential backoff with jitter, dead-letter queues, and reconciliation with bank statements.
Design Razorpay's payout system (RazorpayX). Businesses send bulk payouts to thousands of vendor accounts simultaneously. Cover: batching, bank API rate limits, real-time status tracking, and failure handling.
Design Razorpay's payout system (RazorpayX). Businesses send bulk payouts to thousands of vendor accounts simultaneously. Cover: batching, bank API rate limits, real-time status tracking, and failure handling.
How do you implement a distributed ledger for financial transactions? Explain double-entry bookkeeping in code, why you never update a balance directly, and how you use event sourcing to reconstruct the current balance from a transaction log.
How do you implement a distributed ledger for financial transactions? Explain double-entry bookkeeping in code, why you never update a balance directly, and how you use event sourcing to reconstruct the current balance from a transaction log.
Design Razorpay's dashboard for merchants. A merchant wants to see real-time revenue, transaction success rates, and refund trends. How do you aggregate millions of transactions into live charts with under 5-second latency?
Design Razorpay's dashboard for merchants. A merchant wants to see real-time revenue, transaction success rates, and refund trends. How do you aggregate millions of transactions into live charts with under 5-second latency?
Kafka guarantees message order within a partition but not across partitions. For a payments system, why does this matter, and how would you key messages to preserve per-account ordering?
Kafka guarantees message order within a partition but not across partitions. For a payments system, why does this matter, and how would you key messages to preserve per-account ordering?