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

Citadel Quant Interview Questions India 2026

Citadel and Citadel Securities interviews probe game theory, probability, and optimal decision-making at a high bar, reflecting a top-tier hedge fund and market maker.

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

Questions12
Rounds3
Intense3 of 12
FrameworkOptimal play and price
Try it · Citadel question 1 of 10
Standard

Reverse a linked list in O(1) extra space. Then explain when you'd use this in production.

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

Expect game-theory problems with optimal play (the coins-from-either-end game solved with dynamic programming), geometric and combinatorial probability (the broken-stick triangle problem), and expected-value games with optimal-stopping rules (a die game with a re-roll). Interviewers reward candidates who set up the recurrence or region argument cleanly, state their strategy explicitly, and compute a fair price with confidence. For quant-developer roles, strong coding and algorithms are tested alongside. Practise optimal-play reasoning, geometric probability, and stating decision rules precisely under questioning.

Practice questions

  1. 01

    Reverse a linked list in O(1) extra space. Then explain when you'd use this in production.

    Standard
    Practise
  2. 02

    What is the difference between a class and an object? Give an example.

    Warm-upTCS Ninja/Digital tracks lean heavily on CS fundamentals: OOP, OS, DBMS, SQL basics. Expect rapid-fire Q's, not deep dives.
    Practise
  3. 03

    Write a SQL query to find the second-highest salary in a department.

    Warm-up
    Practise
  4. 04

    What is normalisation in databases? When would you de-normalise?

    Warm-up
    Practise
  5. 05

    What's the difference between a stack and a queue? Give a real-world use case for each.

    Warm-up
    Practise
  6. 06

    Given a stream of integers, design a data structure that returns the median in O(log n).

    Intense
    Practise
  7. 07

    You have a service that's slow only on Tuesdays. Walk me through how you'd debug.

    StandardGoogleyness: structured debugging, hypothesis-driven, instrumentation-first.
    Practise
  8. 08

    Here's 200 lines of payment-processing code with several intentional bugs. Find them and explain the production impact of each.

    IntenseStripe's signature 'bug bash' round. Off-by-one, race conditions, wrong error handling, edge cases in money math. Communicating impact > finding all bugs.
    Practise
  9. 09

    Explain webhooks vs. polling for a developer who has never built a payment integration. You have 4 sentences.

    StandardStripe values writing clarity above almost everything. Length-constrained explanation tests prioritisation of ideas.
    Practise
  10. 10

    Walk me through Razorpay's fraud-detection model. How would you reduce false positives without increasing chargeback losses?

    IntenseRazorpay ML rounds tie model decisions to ₹ impact, chargeback cost vs. blocked-good-txn cost. Pure ML answers without business framing fail.
    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 Citadel recruitment process has 4 stages: Apply or get sourced; online assessment or recruiter screen → Probability and game-theory round → Technical and algorithms rounds (for quant-developer roles) → Final rounds with the desk, then offer.

Citadel typically conducts 3 interview rounds: Round 1 (45-60 min): probability and expected-value round with games; Round 2 (45-60 min): game-theory and optimal-play problems; Round 3 (45-60 min): algorithms and data-structures round for quant-developer roles, or deeper quant for research roles.

HireStepX recommends the Optimal play and price framework for this type of interview: Set up recurrences or region arguments cleanly, state your optimal strategy explicitly, and price games with confidence under a demanding interviewer.

TCS Ninja/Digital tracks lean heavily on CS fundamentals: OOP, OS, DBMS, SQL basics. Expect rapid-fire Q's, not deep dives.

Googleyness: structured debugging, hypothesis-driven, instrumentation-first.

Stripe's signature 'bug bash' round. Off-by-one, race conditions, wrong error handling, edge cases in money math. Communicating impact > finding all bugs.

Game theory with optimal play (dynamic-programming games), geometric and combinatorial probability (the broken-stick problem), and expected-value games with optimal-stopping rules.

For quant-developer and software roles, yes. Expect algorithms and data-structures rounds alongside the probability and game-theory questions, at a high difficulty bar.

Practice

Rehearse the room before you enter it.

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