How every number on this site is produced

Vacancies are collected from employer-operated job boards only — the same pages a candidate would apply through. We do not use job aggregators, scraped third-party listings, or recruiter-posted duplicates.

Each source is recorded with its employer, board type and board URL, and carries a permission flag; a source marked not permitted is never read. Every collection run records its status and the number of vacancies returned, so a silently failing source shows up as a gap rather than as a drop in demand.

Editorial firm profiles cover a wider set of employers than we read boards for. Where we have no live feed for a firm, its profile says so plainly rather than showing an estimated count.

Employers routinely list the same role several times — once per office, once per level, or repeatedly as the requisition is refreshed. Counting those as separate demand would overstate every figure on the site.

Each vacancy gets a deduplication key built from the employer, its normalised title and its resolved city. Normalising a title strips seniority prefixes, requisition numbers, bracketed office names and punctuation. Two postings with the same key are one vacancy; the newest sighting updates the existing record rather than creating another.

A vacancy that disappears from its board is not deleted. It is marked closed with the date, which is what makes it possible to measure how long roles stay open.

Each vacancy description is matched against a fixed, published list of terms per skill. A mention means the employer asked for the skill in writing. We do not infer skills from job titles, from the firm's reputation, or from any model's judgement.

Terms and thresholds are set in advance and applied identically to every posting, so the same vacancy always produces the same result and any figure can be reproduced from the source link.

The consequence is a known undercount: an employer who wants C++ but never writes the word is invisible to this method. We prefer the undercount to a guess.

Two distinct kinds of pay figure appear on this site, and they are never mixed. Measured ranges come only from vacancies where the employer advertised a figure — currently 182 of 1,333 live vacancies. Those are parsed conservatively: annual figures only, with implausible values discarded, and reported as medians of the advertised minimum and maximum.

Figures are expressed as annual total compensation (base salary plus expected performance bonus) in the reference market's local currency, converted from a US dollar base. They describe typical market ranges rather than any individual offer, and exclude sign-on payments, deferred equity and carried interest. Portfolio-manager figures reflect formulaic profit-share arrangements and are therefore far more dispersed than any other role.

These are indicative ranges pending first-party verification. They will be replaced by verified submissions as the Quant Salary Index dataset builds.

Every figure carries the number of vacancies behind it and the number of employers those came from. A confidence band is derived from both: high, medium, early signal, or insufficient. An early-signal figure is published but should not be read as a trend.

Period-over-period change is only published where the comparison period held at least five postings. Below that, the change reads 'insufficient' rather than showing a swing that is arithmetic noise.

We do not claim a trend from a handful of vacancies, and we do not round small samples up into confident language.

This dataset measures advertised demand, not total hiring. A great deal of senior quant hiring — portfolio managers especially — never reaches a public board, so senior counts understate reality more than junior counts do.

Coverage is uneven by firm. Employers on boards we read are measured precisely; others appear only in editorial profiles. Comparing two firms' vacancy counts is only meaningful where both are read live.

Posting dates are the employer's own and are sometimes refreshed when a requisition is re-advertised, which can make an old role look new. Location fields are free text and resolve to a city only where the text is unambiguous; the rest are counted in totals but not in any city figure.

Advertised pay skews towards jurisdictions that require it, so measured pay ranges are not a representative sample of global compensation.