Anatomy of a Multi-Strat Pod Build-Out — How a New PM Hires Their First Five Quants

Most PMs arriving at a multi-strat platform bring their core research methodology but not their team. Non-solicitation and gardening-leave covenants typically prevent bringing former colleagues for 6–24 months depending on jurisdiction and seniority — UK senior quants often face 6–12 months, US senior quants and PMs frequently 12–24 months. The PM must therefore build a new team from scratch — or use contract resources for the first phase while permanent searches are in-flight.

The platform provides shared infrastructure (risk systems, execution connectivity, market data), so the PM is building the team layer above that. Typical timeline: months 1–2 in infrastructure and data setup (often contract engineers), months 3–6 in research ramp-up with the first permanent hire, months 6–18 scaling the team.

The first hire is almost always a senior researcher who can run independently and complement the PM's own research strengths. This hire is typically a retained permanent search.

What to offer: PhD-level base of £150k–£250k depending on seniority, meaningful discretionary bonus tied to pod P&L, and potential co-investment rights if the researcher is senior enough to have contributed material alpha.

The pod needs its own research infrastructure — a backtesting framework tuned to the PM's strategy type, data pipelines, and tooling for the research team. This is where contract often makes sense for the build phase. A senior Python quant developer on a 6–9 month contract can stand up the research platform while the permanent developer hire is in progress.

Permanent quant developer hire: £130k–£200k base, tech-heavy interview process, typically 3–4 months to close from search start.

Most multi-strat platforms have shared KDB infrastructure, but pods with high-frequency data requirements or custom tick capture needs will need their own KDB engineer. This work is often contract — the project is bounded and the skill set is scarce enough that permanent hiring timelines are prohibitive.

A 3–6 month KDB contract at £1,300–1,800/day for a Lead/Principal engineer covers most pod data build requirements, with specialist tick-plant build experience commanding a premium of £1,800–2,200/day. At the end of the engagement: extend the contract, convert to permanent, or hand off to the platform's shared KDB team.

Once the research infrastructure is in place and alpha is being generated at scale, the pod hires down to build depth and handle execution complexity.

Junior Researcher: PhD or very early career. The PM or senior researcher mentors them. They handle data analysis, signal validation, and execution research.

Execution Quant: As pod allocation grows and the strategy trades across more instruments, execution quality becomes a performance driver. An execution quant optimises order routing and manages execution algorithms.

The hire most pods add in months 9–12 but rarely plan for at the outset. As the strategy scales and allocation grows, position monitoring, P&L attribution and the operational interface with the platform's central risk team demand dedicated resource.

This role sits at the intersection of technology and risk — typically a quant developer with risk system experience, or occasionally a risk analyst with strong coding skills. They own the pod's real-time P&L and risk reporting, manage the feed into the platform's risk infrastructure, and act as the PM's eyes on exposure in live markets.

Compensation: £120k–£180k base for a strong candidate with relevant platform experience. Often the hire that makes the senior researcher's and execution quant's jobs materially easier.

A well-functioning pod at month 12 has: PM + senior researcher + quant developer + KDB/data support + execution quant + risk technologist. Total headcount 5–6.

Supporting team comp budget (excluding PM): £1.5M–£3M per annum in base salary and bonus. Fully-loaded pod economics including the PM — guarantee, P&L participation, bonuses, NICs, benefits and platform allocation charges — typically run to £3M–£8M+ at the major multi-managers in a normal performance year.

Year two scaling follows one of three patterns depending on how the strategy is performing:

Second senior researcher. If alpha generation is the constraint — the PM has more strategy ideas than research bandwidth — the next hire is a second senior researcher, often with a complementary signal style.

Junior quant developer. If infrastructure is the constraint — the research team is generating ideas faster than the platform can test and deploy them — the next hire is a junior developer to expand throughput.

Sub-strategy PM. At larger allocations ($300M+), PMs sometimes bring in a junior PM to run a correlated sub-strategy under the pod umbrella, with a separate smaller allocation. This extends the pod's capacity without diluting the lead PM's focus.

Dedicated execution team. As allocation scales toward $500M+ and the strategy trades across a wide instrument universe, execution alpha becomes a material driver. A two-person execution team (execution quant plus an execution developer) is the norm at that scale.