Which seat to aim for
Quant development is the natural landing point: research infrastructure, data pipelines, simulation environments and the production path from signal to order. Low-latency engineering is the higher-paying and more specialised variant, and rewards systems, networking and hardware depth over breadth.
Research is a much harder pivot without a research credential, and is better approached after establishing yourself internally.
What transfers and what does not
Transfers well: C++ depth, performance work, distributed systems, data engineering at scale, and anything involving real-time constraints. Firms value engineers who have shipped systems where correctness and latency both mattered.
Transfers poorly: framework breadth, product engineering, and web-stack experience. These are not negatives, but they carry little weight in the assessment.
The interview gap to close
The main difference from a technology interview loop is the probability and statistics component, which is present even in engineering tracks, and the emphasis on low-level reasoning — memory layout, cache behaviour, and what the machine is actually doing. Most engineers underprepare for exactly these two areas.