Quantitative Developer (Greater Chicago Area)
Quantitative Developer (Greater Chicago Area)
Posted yesterday
SENIORITY
Senior
About the role
- Model implementation: Take pricing and risk models from traders and researchers and build fast, robust, concurrent, production-grade versions
- Concurrency design: Architect multicore systems with real shared-state concurrency and efficient synchronisation
- Performance optimisation: Squeeze throughput and latency out of numerical code through cache-aware data layout, memory reuse, and pragmatic speed versus precision trade-offs
- Full lifecycle ownership: Build, deploy, test and integrate your own systems
- What You BringDeep, demonstrable experience in multithreaded and concurrent C++ on Linux, with correct designs at high throughput and low latencyStrong command of synchronisation and interprocess communication primitives and when to use each
- A proven track record optimising numerical calculations for throughput and latencyStrong modern C++ and practical mastery of the build and deploy loop
- Experience implementing numerical methods and matrix decompositions
- Enough derivatives pricing knowledge to collaborate closely with the desk
- Someone pragmatic about resources who builds systems that run within real core and memory budgets
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
