How do trading firms actually read a resume?

Hi ​everyone,

I found our community about a month ago and have been working through it since.

​I​ want to share a little bit about myself. I'm a backend/infra engineer, currently employed full-time, trying to move into quant dev​eloper. I've read plenty of threads on what to study and how to prepare for interviews, and that part is genuinely well covered by now. What I can't find anywhere is the layer before it​ on how trading firms actually read a resume, and what gets someone with a pure backend background past the screen in the first place. That's where I'm stuck. The first quant role feels like a wall, and I'll be honest, I'm a bit lost about which side of it to push on.

So my question. Beyond studying and shipping side projects, what else actually counts? Certs, competitions, a specific kind of role to take first? And if it's experience, how do people build that while holding a full-time job? Any tips, any advice?

Hope to hear sharing from everyone

reddit.com
u/Useful-Strain-7088 — 14 days ago

How do trading firms actually read a resume?

Hi ​everyone,

I found your community about a month ago and have been working through it since.

​I​ want to share a little bit about myself. I'm a backend/infra engineer, currently employed full-time, trying to move into quant dev​eloper. I've read plenty of threads on what to study and how to prepare for interviews, and that part is genuinely well covered by now. What I can't find anywhere is the layer before it​ on how trading firms actually read a resume, and what gets someone with a pure backend background past the screen in the first place. That's where I'm stuck. The first quant role feels like a wall, and I'll be honest, I'm a bit lost about which side of it to push on.

So my question. Beyond studying and shipping side projects, what else actually counts? Certs, competitions, a specific kind of role to take first? And if it's experience, how do people build that while holding a full-time job? Any tips, any advice?

Hope to hear sharing from everyone

reddit.com
u/Useful-Strain-7088 — 14 days ago

How do trading firms actually read a resume?

Hi ​everyone,

I found your channel and community about a month ago and have been working through it since.

​I​ want to share a little bit about myself. I'm a backend/infra engineer, currently employed full-time, trying to move into quant dev​eloper. I've read plenty of threads on what to study and how to prepare for interviews, and that part is genuinely well covered by now. What I can't find anywhere is the layer before it​ on how trading firms actually read a resume, and what gets someone with a pure backend background past the screen in the first place. That's where I'm stuck. The first quant role feels like a wall, and I'll be honest, I'm a bit lost about which side of it to push on.

So my question. Beyond studying and shipping side projects, what else actually counts? Certs, competitions, a specific kind of role to take first? And if it's experience, how do people build that while holding a full-time job? Any tips, any advice?

Hope to hear sharing from everyone

reddit.com
u/Useful-Strain-7088 — 14 days ago
▲ 0 r/quant

SWE background (backend/infra), built a C++20 market-data feed recovery project, looking for technical feedback

Working on a project that separates three concerns: a seeded fault injector that damages a market-data feed (drop, reorder, A/B line divergence), a recovery client that detects gaps and repairs them via retransmission or snapshot rebuild, and a mock venue that speaks the real wire protocols so the client isn't tested against a stub. Repo: https://github.com/hungtruongOwolf/deterministic-feed-recovery

The interesting failure mode: a client can deliver every message with correct sequence counts and still reconstruct the wrong order book, if retransmitted repairs are applied in arrival order instead of sequence order. Fixing that meant the recovery layer has to number everything it hands upstream, not just the transport layer.

Two questions on the architecture:

  1. Is separating fault injection / recovery / mock venue into independent components the right decomposition for this kind of problem, or is there a cleaner way to structure it that avoids the coupling I'm running into between the arbiter and the gap tracker?
  2. For the recovery-side testing, is there a better way to validate "book after repair equals book with no loss" than diffing against an oracle replayed from the undamaged original? Right now it's checked at the price-level per run, curious if there's a more rigorous invariant people use here.
u/Useful-Strain-7088 — 18 days ago