Load several years of market data and see how pay has moved for each job family, level and job code. Find the biggest movers up and down, and decide how much to trust the small samples.
Every year a new market survey arrives, and the first question is always the same: what moved? Answering it means lining up this year's file against last year's, job code by job code, and most teams do that by hand in a spreadsheet.
This tool does the lining up for you. Load one file per survey year and it shows how the median has moved for the whole market, for each job family and level, and for every job code. It tracks total fixed remuneration (TFR): base salary plus cashable benefits plus superannuation.
You can look at the latest year, the change since the first year, or the average per year. A chart shows every family on the same scale, a heat map shows which levels moved in which year, and two lists show the biggest movers up and down. Click anything to drill down to the job codes behind it.
It also deals with the problem that catches people out: small samples. A job with three incumbents can jump 30% in a year because one person changed, not because the market moved. You set the minimum number of incumbents and organisations, then choose to show, flag or leave out anything below it.
It was "vibe coded": you describe what you want to an AI assistant in plain English and let it write the code. Once built, it is ordinary code. It runs the same calculation every time and uses no AI when you run it.
This is the real tool, running in your browser on five years of invented market data for 239 job codes. Switch "Small samples" between Show all and Exclude and watch the biggest movers change. Click a line, a row or a cell to drill down.
Every job code and figure is invented. If you load your own files, they are read by your own browser and nothing is uploaded.
Five steps from a stack of survey files to knowing what moved. Press Play, or step through at your own pace.
| job_code | job_title | job_family | level | tfr_median | incumbents | organisations |
|---|---|---|---|---|---|---|
| TEC-SWE-4 | Software Engineer | Technology | Level 4 | $162,400 | 270 | 40 |
| DAT-DSC-5 | Data Scientist | Data & Analytics | Level 5 | $234,900 | 63 | 16 |
| MKT-BRD-4 | Brand Manager | Marketing | Level 4 | $118,300 | 43 | 15 |
| RSK-MDL-6 | Model Risk Specialist | Risk | Level 6 | $264,900 | 3 | 3 |
Start with a file per year. One row per job code, with the median and the two sample sizes: how many people and how many organisations sit behind the figure. Select all five files at once and the tool stacks them.
Work out each job's movement. This year's median divided by last year's, for the same job code. The tool does this for every code that appears in both years, and for any pair of years you choose.
Roll up to job families. A family's figure is the average of its job codes' movements, using only codes found in both years. That way a job being added to or dropped from the survey is not mistaken for a pay movement. Marketing, in gold, fell.
Watch the small samples. The two biggest "movers" rest on three and four people. With so few, one person joining or leaving swings the median. The tool flags any job code under your minimum, here 10 incumbents or 5 organisations.
Find the real movers. Leave out the small samples and the list changes: 23 job codes drop out and the picture is now Data & Analytics rising and Marketing falling. Click any job to see its full history, year by year.
All figures in this walkthrough are invented and match the tool's built-in sample at its starting settings.
You can build your own version with any capable AI assistant your employer allows, for example Microsoft Copilot, Claude or ChatGPT. You describe what you want, it writes the code, and you check the answers.
Build it with invented data, never your real survey files. Expect two or three rounds of "that's not quite right, change X".
Say what the tool is, what goes in, and who will use it.
Do not let the AI guess the maths. Tell it exactly what to calculate.
Survey data is licensed, so the tool should keep it on your computer and remind people of that.
Load a tiny file where you can work out every answer by hand.
| Whole market | Job codes compared | Movement |
|---|---|---|
| Latest year (2025 to 2026), small samples shown | 4 | +9.3% |
| Latest year, small samples excluded | 3 | +2.3% |
| Latest year, weighted by incumbents | 4 | +5.6% |
| Since first year (2024 to 2026) | 4 | +14.0% |
| Average per year | 4 | +6.6% |
Three rows are there to test the edges. A3 has only 4 incumbents, so it is the small sample, and leaving it out drops the answer from 9.3% to 2.3%. B1 has exactly 10 incumbents and 5 organisations in 2026, which is on the minimum and so not small. B1 is also missing in 2025, so it counts in "since first year" but not in "latest year".
If the tool gives a different answer, it is wrong. Tell the AI what you expected and ask it to fix the calculation.
Market survey data: medians, percentiles and sample sizes by job code. It holds no employee records and no personal information. It is usually licensed, and the licence sets who can see it and where it can go.
The finished tool runs in your browser and nothing is uploaded. Keep it and its downloads with the people your licence covers. When you build your own, give the AI assistant invented data only, never an extract from the survey.
Small samples matter for a second reason: a figure resting on a handful of people at a few organisations can come close to revealing what a single employer pays, which is why survey providers set their own minimums. This tool is market data only. If you later add your own pay data to compare against the market, it becomes employee data and the rules change: see the position in range analyser for how that is handled. General information, not legal advice.
It is a single file. Save it anywhere and double-click to open it. The sample files can be downloaded from inside the tool.
What next: to see how your own people sit against their reference points, try the position in range analyser, or go back to all use cases.