Expect prompts on a trade-settlement system that moves securities and cash and must be regulator-reportable, a regulatory-reporting pipeline ingesting data from many source systems that handles late or corrected data, and an immutable audit-log service supporting fast point-in-time queries. Interviewers reward append-only event logs, clear settlement state machines, and read-optimised, tamper-evident audit storage. The regulatory context makes correctness, traceability, and handling of corrections first-class design concerns rather than edge cases you mention at the end.
Recruitment process
Online coding assessment
Technical coding round on DSA
System-design round on settlement, reporting, or audit
Hiring-manager round, then offer
Interview rounds
Round 1 (60-90 min): online coding assessment
Round 2 (45-60 min): coding round on data structures and algorithms
Round 3 (45-60 min): system-design round on settlement, regulatory reporting, or audit logging
Round 4 (45 min): behavioral and hiring-manager round
Append only and auditable framework
Use append-only event logs and clear state machines for settlement, handle late and corrected data explicitly, and make audit storage tamper-evident and read-optimised
Practice questions
01
Design a system to predict same-day delivery feasibility for a new pincode in tier-3 India.
2 more questionsCreate a free account to see the full set and practise any of them with scoring.Unlock all questions
Prep notes
How to walk in ready.
The typical Deutsche Bank India recruitment process has 4 stages: Online coding assessment → Technical coding round on DSA → System-design round on settlement, reporting, or audit → Hiring-manager round, then offer.
Deutsche Bank India typically conducts 4 interview rounds: Round 1 (60-90 min): online coding assessment; Round 2 (45-60 min): coding round on data structures and algorithms; Round 3 (45-60 min): system-design round on settlement, regulatory reporting, or audit logging; Round 4 (45 min): behavioral and hiring-manager round.
HireStepX recommends the Append only and auditable framework for this type of interview: Use append-only event logs and clear state machines for settlement, handle late and corrected data explicitly, and make audit storage tamper-evident and read-optimised.
Razorpay loves real production scenarios: payments failures, NPCI rate limits, settlement reconciliation. Be specific.
PhonePe engineering rounds are scale-obsessed: every answer should explicitly address throughput, latency, and cost at India scale.
Google SWE rounds prize first-principles thinking and explicit trade-off articulation. Always discuss what you're approximating.
A trade-settlement system that is auditable and regulator-reportable, a regulatory-reporting pipeline that handles late and corrected data, and an immutable audit-log service with fast point-in-time queries.