Skip to main content
HireStepX is now in Beta! Be among the first to practise smarter and get hired on proof.
System Design · Barclays

Barclays System Design Interview Questions 2026

Barclays's system-design rounds are payments-and-correctness focused.

By the HireStepX editorial team · How we source and label this

Questions12
Rounds4
Intense9 of 12
FrameworkIdempotent and restartable
Try it · Barclays question 1 of 10
Intense

Design a system to predict same-day delivery feasibility for a new pincode in tier-3 India.

Think of your answer first, then reveal how to structure it.
Practise this out loud

Expect prompts on a payment-processing system that transfers money reliably and never loses or double-sends it, a real-time fraud-detection pipeline that scores and flags transactions, and a restartable batch job that reconciles a day's transactions against clearing-house files. Interviewers reward idempotency, a state machine per transfer, reconciliation for every failure mode, and checkpointed restartable batch processing. Because the domain is money movement, hand-waving on failure handling does not survive; the interview rewards precise reasoning about exactly-once semantics and recovery.

Practice questions

  1. 01

    Design a system to predict same-day delivery feasibility for a new pincode in tier-3 India.

    IntenseFlipkart engineering loves India-specific constraints: pincode coverage, monsoon patterns, kirana partnerships.
    Practise
  2. 02

    We're seeing UPI failure rates spike at 9pm on weekends. How would you debug, and what's your hypothesis?

    IntenseRazorpay loves real production scenarios: payments failures, NPCI rate limits, settlement reconciliation. Be specific.
    Practise
  3. 03

    Walk me through how you'd build idempotency into a payment retry system. What happens if the network drops mid-callback?

    Intense
    Practise
  4. 04

    Design Swiggy Genie's matching algorithm. How does it differ from food-order matching?

    Intense
    Practise
  5. 05

    Walk me through how you'd architect transaction-level fraud detection for 100M daily UPI transactions.

    IntensePhonePe engineering rounds are scale-obsessed: every answer should explicitly address throughput, latency, and cost at India scale.
    Practise
  6. 06

    How would you build a recommendation engine that suggests bills the user is about to forget?

    Standard
    Practise
  7. 07

    Design a cashback-allocation system that prevents abuse without alienating genuine users.

    Standard
    Practise
  8. 08

    Design a system to detect duplicate documents at web scale. What's your approximation strategy?

    IntenseGoogle SWE rounds prize first-principles thinking and explicit trade-off articulation. Always discuss what you're approximating.
    Practise
  9. 09

    Design Amazon Prime's recommendation engine. How would you handle the cold-start for a new Prime member?

    Intense
    Practise
  10. 10

    Design a URL shortener like bit.ly. Walk me through database choice and scaling.

    Standard
    Practise
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 Barclays recruitment process has 4 stages: Online coding and aptitude assessment → Technical coding round on DSA → System-design round on a payments or reconciliation service → Hiring-manager round, then offer.

Barclays typically conducts 4 interview rounds: Round 1 (60-90 min): online coding and aptitude assessment; Round 2 (45-60 min): coding round on data structures and algorithms; Round 3 (45-60 min): system-design round on payments, fraud, or reconciliation; Round 4 (45 min): behavioral and hiring-manager round.

HireStepX recommends the Idempotent and restartable framework for this type of interview: Model each transfer as an idempotent state machine, reconcile every failure mode, and make batch jobs checkpointed and restartable so no money is lost or double-sent.

Flipkart engineering loves India-specific constraints: pincode coverage, monsoon patterns, kirana partnerships.

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 reliable payment-processing system, a real-time fraud-detection pipeline, and a restartable batch reconciliation job against clearing-house files.

Practice

Rehearse the room before you enter it.

Run a mock Barclays interview and get scored feedback on every answer.