Price a role you've never hired
Get a defensible range for a brand-new job by tomorrow, not next week.
The prompt
We're opening a Staff Machine Learning Engineer role in Austin and remote US. Find the closest market matches, recommend a level in our architecture, and give me base, bonus and equity ranges at our target percentile.
Then try
- How does this compare to our current IC5 engineering band?
- What changes if we only hire in Austin?
What you get back
Sample output with illustrative data
Closest market match is Machine Learning Engineer at the Staff level. Recommended mapping is your IC5. Ranges below target your 60th percentile for Austin.
The problem
The business wants to open a role that isn't in your job architecture yet. The title is fuzzy, the hiring manager wants a number, and you need one you can defend.
The old way
- Search surveys for something close to the title
- Argue about which level it maps to
- Hand-build a range and hope it holds up in offers
Why it works in Pave
Matches fuzzy titles
It reads the job description, not just the title, and shows you the match it picked.
Maps to your levels
The range lands in your architecture, so it fits next to the bands you already have.
Location built in
Geo differentials come with the benchmark, not from a separate table.
Data it uses
Your data
- Job architecture
Your levels and job families - Comp philosophy
Target percentiles by function - Adjacent bands
Ranges for similar roles you already have
Pave intelligence
- Market Data benchmarks
Matched jobs by level - Geographic differentials
Location adjustments - Equity benchmarks
Annual grant value by company stage
What you need
See it on your data
We'll run this prompt in your Pave instance before we ever meet.
Book a demo