Skip to content
dronacharya.ai

AlphaGrep

InternshipQuant and financeSoftware

Built from 1 candidate report with 2 first-hand accounts, covering 2026-27.

Hiring process

Roles: QR & T Intern

2026-27 · Internship

  1. 1

    Resume shortlist

    Direct shortlist (no online test)
    eliminatory

    No test was held; candidates went straight to interviews. Both accounts think a CPI around 9 was the criterion, but they are unsure.

  2. 2

    Technical interview

    Interview 1: language depth, DSA and design
    Google Meet50 minhard

    C++ internals · virtual pointers · CRTP · vectors and maps internals · move semantics · universal references · smart pointers · C++11 vs C++17 · Python monkey-patching · endianness · DSA with follow-up · design · previous internship

    Accounts differ: one saw language-trivia heavy round led by a researcher, the other a DSA plus design round. Duration 50 min from one account. Includes introduction and previous internship discussion.

  3. 3

    Technical interview

    Interview 2: probability and C++ fundamentals
    Google Meet40 minmedium

    probability · trading puzzles · mental math · leverage · stack vs heap · RAII · object lifetime · constructors and destructors · endianness

    Order of rounds differs between accounts. Time split reported: 10 min introduction, 25 min probability and C++, 5 min candidate questions.

  4. 4

    Technical interview

    Interview 3: low-level design or finance maths rapid fire
    Google Meet35 minmedium

    low-level design · asynchronous order handling · code quality · arbitrage · hedging · leverage · P&L · speed multiplication

    One account describes a single long low-level design question using the whole round; the other describes a 15 minute math rapid-fire. Duration 35 min from one account.

Advice from candidates

15 pieces of advice, in their own words. Names removed.

  • Be ready for an in-depth discussion of cpp or Python (depending on the role you have applied for).

    interview · 2026-27

  • Take a minute to think about the best way to solve each of the questions. Questions will be pretty easy, but if you take the most straightforward approach, you’ll end up doing a lot of calculations. So take some time to think about the best way to solve the problem. The interviewers will also expect you to think of some smart way that doesn’t involve a lot of calculations.

    interview · 2026-27

  • They were also looking at code quality along with correctness; just keep an eye on time since this was a long question and took the entire interview.

    interview · 2026-27

  • As [friend] said, it's really difficult to read some of the interviewers. They don’t react much to right or wrong answers. Just be confident with whatever you are answering.

    interview · 2026-27

Loading the other 11…

Question patterns reported

The kind of problem, not the problem itself. Our practice questions are written to match these patterns.

  • Technicalsingle-line fix for loop counter reset trick in C++
  • Technicalwrite function to detect machine endianness
  • Technicalone DSA problem with follow-up, then a design question
  • Technicalstandard probability puzzles needing a clever low-calculation route
  • Technicaltrading scenario puzzles with concept explained in interview
  • Technicaldesign order manager processing acknowledgements asynchronously
  • Technicalnumerical questions from supplied finance definitions, plus two-digit multiplication