> Markdown version of [/jobs/ext/3573159-lead-quantitative-developer](https://www.wearedevelopers.com/jobs/ext/3573159-lead-quantitative-developer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Lead Quantitative Developer

- **Company:** Pinely
- **Location:** Amsterdam, Netherlands
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, C++ (Programming Language), Python (Programming Language), Software Coding
- **Published:** October 4, 2026
- **Apply:** https://www.adzuna.nl/details/5737687845

## About the Role

* Strong mathematical and algorithmic thinking; solid grasp of statistics and probability;
 * Ability to write production-quality C++ and Python 3;
 * Experience delegating technical work - not just assigning tasks, but framing problems so others can own them;
 * Track record of growing junior and mid-level engineers;
 * Deep systems understanding: ability to navigate the full stack from model training and simulation through to production - and reason about how a change at one layer affects others;
 * Willingness to dive deep into market microstructure and strategy details;
 * Experience with or strong interest in ML/AI tooling in research workflows.

## Description

We're looking for a Lead Quantitative Developer to join one of our trading teams - someone who combines deep technical ownership with the ability to grow and lead people.
The team is intentionally small by design - close mentorship, no bureaucracy. Great leadership here means staying in the trenches, not stepping away from them.

We're building toward a research lab culture. That means: understanding why something works, not just making it work. Reducing vague problems to core uncertainties before writing code. Intellectual honesty - with yourself and in the code you review. And the courage to push back and own decisions when it matters.

What you'll do

 * Owning and evolving the team's strategy codebase with direct P&L impact;
 * Decomposing research and production problems into concrete, delegatable tasks with clear success criteria;
 * Growing QDs on the team - understanding their strengths, motivations, and career goals; giving regular feedback that amplifies rather than just corrects;
 * Prioritizing QD capacity across competing demands: research requests, production stability, infra timelines;
 * Driving alignment with infrastructure and research teams through influence, not hierarchy;
 * Accelerating the research cycle using in-house AI development tools - agentic coding assistants, end-to-end AI-driven workflows;
 * Independently building and shipping strategy improvements where engineering quality has direct trading impact.