Deutsche Bank's system-design rounds weigh auditability and regulatory reporting alongside correctness.
In 2026 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.
About Deutsche Bank India
Deutsche Bank India (Pune, Mumbai) is a key technology and operations hub for the German bank's global investment banking, transaction banking, and technology infrastructure. Pune TDI (Technology Development and Innovation) is DB's largest India site.
Online coding assessment
Technical coding round on DSA
System-design round on settlement, reporting, or audit
Hiring-manager round, then offer
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.
Sourced from 2+ candidate post-mortems. Hit Practice to answer any one with AI voice feedback.
2 more questions. Sign up to unlock all
Sign up free: unlock all questionsThe 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
To answer this question well, HireStepX recommends the Append-Only-and-Auditable approach: 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 Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Append-Only-and-Auditable approach: 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 Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Append-Only-and-Auditable approach: 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 Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Append-Only-and-Auditable approach: 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 Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Append-Only-and-Auditable approach: 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 Ground your answer in a specific real example from your own experience.