Permanent vs Contract in Quant Engineering — When Each Makes Sense

Permanent hires make sense when the work is ongoing, IP-sensitive, and requires deep institutional knowledge.

Quant researchers. Alpha generation is the core IP of a systematic fund. Researchers who develop signals, build models and iterate on strategy need to understand the fund's historical data, research conventions and risk framework deeply. That knowledge accumulates over years. Most research roles should be permanent.

Systematic portfolio managers. PMs own a strategy and are accountable for P&L. The relationship between a PM and the fund's infrastructure, risk team and CIO is built over time.

Senior quant developers building core greenfield systems. If you are building the firm's primary backtesting framework, execution management system or risk engine — the system that will run live for five to ten years — the engineer building it should understand it deeply and be around to maintain it.

Contract works when the work has a defined shape, bounded duration, or requires a skill set that the permanent market cannot supply quickly enough. The distinction worth holding in your head: greenfield core systems that will run for a decade are permanent work; bounded transformation projects on those same systems are contract work.

Platform migrations. Moving from KDB 3.x to Kx 4.1, rebuilding a tick plant, migrating from on-premise to cloud. These are projects with a start and end. Contract is the right model.

New pod or strategy build-outs. When a PM joins a multi-strat platform and needs to build infrastructure in 8–12 weeks, contract engineers can stand up backtesting infrastructure, data pipelines and execution connectivity faster than a permanent search can deliver.

Covering specialist gaps. If your permanent KDB engineer is on extended leave and you have a major data delivery in six weeks, permanent search timelines (12–16 weeks) don't solve the problem — contract timelines (4–8 weeks) do.

Testing a new capability. Want to experiment with a Rust-based execution layer without committing permanent headcount to an experiment? Contract gives you expert capacity without the long-term commitment.

Since the 2021 IR35 off-payroll working rule changes, Inside IR35 determinations have become more common in financial services.

Inside IR35: The fund or umbrella company deducts employee NICs and income tax from day rates. Day rates are typically 20–25% higher to compensate.

Outside IR35: The contractor operates as a genuine business. Lower employer costs, higher contractor net take-home. Requires a genuine business-to-business relationship.

The determination should be made properly before engagement starts. We provide a written IR35 assessment on every contract placement we make.

Ask these five questions:

1. Will this work still exist in 2 years? Yes — lean permanent. No or uncertain — contract. 2. Does success depend on deep institutional knowledge? Yes — permanent. No — contract. 3. Can you find a strong permanent hire within 8 weeks? Yes — go perm. No — start with contract. 4. Is the work IP-sensitive at a strategy level? Yes — permanent. No — contract or hybrid. 5. Is the skill set so scarce that permanent rates are prohibitive? Yes (e.g. FPGA) — contract as the only viable model.

The cleanest outcome is often a contract that converts to permanent once the project is delivered and both sides want to work together long-term. We handle contract-to-perm conversions cleanly — it is a planned part of many of our placements.