Quant developer vs quant researcher: which seat suits you

The split in one sentence

Researchers decide what should be true about the market; developers make sure the machine behaves exactly as intended when real money depends on it.

Daily work

A researcher's week is dominated by data preparation, hypothesis testing and arguing about whether a result is real. A developer's week is dominated by system design, performance work, correctness under failure, and the unglamorous business of making other people's code fast and safe.

Both are technical. Only one of them will be asked to explain a p-value under pressure.

Interviews diverge early

• Research. Probability, statistics, model design, and a deep discussion of your own past work. Expect open-ended questions with no clean answer.
• Development. Data structures, memory, concurrency, and often live coding in C++. Expect precise questions with a right answer.

Our interview lab separates the two so you are not preparing for the wrong exam.

Pay and progression

Research pay is more variable and more directly tied to strategy performance. Development pay is more stable and, at the senior end in low-latency engineering, extremely competitive. Neither is the junior of the other.

Moving between them

The common move is developer to researcher, usually by demonstrating research work informally before asking for the seat. The reverse move happens less often, because production engineering is a distinct craft that takes years to build.

Whichever direction interests you, look at live vacancies for both and read the skills each is actually asking for.