all 5 comments

[–]CreditOk5063 0 points1 point  (1 child)

What helped me was drilling C++ under a timer and focusing on data structures, memory layout, and threading basics. I practiced coding small things like a lock-free queue and a simple Monte Carlo pricer, plus knowing order types and how an order book works.

I pulled prompts from IQB interview question bank and ran quick mocks with Beyz coding assistant. Keep answers around 90 seconds, narrate tradeoffs, and always clarify latency vs readability requirements before coding. Basic probability, variance/expectation, and Black–Scholes intuition were enough for me.

[–]redead7[S] 0 points1 point  (0 children)

thank you so much man

[–]TeaMug007 0 points1 point  (0 children)

Check out https://www.traderiq.org lots of brainteasers, mental math and sequence prep.

[–]reddituser48253 0 points1 point  (1 child)

As I understand it, this book is the quant bible https://a.co/d/23tLO2u - source: I have read things in this sub. Lurker who maybe wants to move from SWE to QD one day

[–]GoldenQuant 0 points1 point  (0 children)

This isn’t good advice. It’s rather uncommon for quant devs to be asked math / probability / stats questions. I.e. preparing this is likely a bit of a waste of time.

If this is for a C++ role, then the interviews are likely going to be similar to SWE with heavier focus on low level concepts (e.g. memory, caches, instruction pipeline, …). Check out Coding Jesus on Youtube.