Play 56 · Software, web and AI
Your posting is under market, which is why it's still open
A seven-step play for a technical recruiter or compensation consultant. It starts from Indeed, stacks Levels.fyi and LinkedIn on top, and ends in a message to the hiring manager that is useful before anyone replies.
Installs this workflow, five project tables and a draft campaign. Source access and any external outputs are checked before research.
- Category
- Software, web and AI
- Sources
- 3
- Steps
- 7
The workflow
- Trigger
IndeedPosting age and the salary band - Evidence
- ArtifactWhat you hand overA comp sheet for the role in that metro, with candidates who fit at the right number.
- ContactGliderFinds the hiring manager, with a verified work email and a phone
- MessageSend itFrom your own mailboxes, evidence attached
Why it earns attention
A role that stays open for months is usually priced under market. Showing the hiring manager what the market pays, and that candidates exist at that number, explains the stale posting and points to the fix.
The play in seven steps
- 01
Find stale postings
Indeed- What you pull
- Postings open more than 60 days with a posted salary band: title, location, band and date posted.
- Why it matters
- A long-open role costs the team every week. The posted band is what you compare against.
ExampleSenior data engineer · Denver · $130k to $140k · open 70 days
- 02
Find what the market pays
Levels.fyi- What you pull
- Pay data and salary filings for the same title, level and metro: median and range.
- Why it matters
- The gap between the band and the market is usually the reason the role is open.
ExampleSame title in Denver · median about $172k · 25th percentile $155k
- 03
Find candidates
LinkedIn- What you pull
- Profiles in the metro with matching experience who show signs of being open to a move.
- Why it matters
- It proves the role can be filled at the right number, which is the second half of the case.
Example3 candidates with matching stack · 5 to 8 years · in Denver
- 04
Build the comp sheet
Your artifact- What you build
- The posted band against the market range, what a competitive offer looks like, and the candidates who fit.
- Why it works
- The hiring manager can take it to finance to get the band raised.
ExampleBand $140k vs median $172k · 3 candidates at $165k to $175k
- 05
Check before you send
Pay data varies by level and company. Compare like with like, and do not share candidate names before they agree.
- 06
Find the hiring manager in Glider
Glider- Search for
- Hiring managerHead of dataTalent acquisition leadVP engineering
- Why them
- The hiring manager feels the empty seat. Talent acquisition owns the band and will push it to finance.
- What you get
- A work email and a direct phone, with the email verified before it goes into a sequence.
- 07
Send the evidence, then run the first test
To: the hiring managerEvery line comes from a step above Your senior data engineer posting has been up 70 days at $130k to $140k.1 Pay data for the same title in Denver puts the median around $172k.2 I found three candidates with your stack who would consider it at the right number.3 Here's the comp sheet you can take to finance.4 Want to see the profiles?
- Facts from the data (the number is the step)
- What you built for them
- One small ask
- Why it works
- It explains a problem they have been staring at for months and hands them the tool to fix it.
- First test
- Twenty postings over 60 days old with a clear pay gap.
- Success looks like
- Two searches signed out of fifteen stale postings.
The sample message is hypothetical and its numbers are illustrative. Verify every claim, date and rule before sending.
Sources used
The three sources this play names. Each links to the other plays that use it.
Related plays
All 63 GTM playsRun this play with Glider.
Deploy the full workflow into a project. Conway checks your scope and source access, builds the evidence, and prepares outreach for review.