8 min read
You did the interviews. You hear they have room. Then the offer lands below what you needed, and you're sure someone said the band was wider. You're not imagining the gap. You're missing how salary data is used internally after you already gave them a number they didn't have to beat.
Most guides talk to HR about benchmarking and equity audits. You need the candidate view: where your stated range sits in Workday or Greenhouse, how recruiter notes follow it, and why a screen answer can become the ceiling even when the hiring manager's got more budget in mind.
Check your resume for free before you fix comp talk. If you're still filtered out at parse, you never reach the conversation where bands matter.
Below is a diagnostic path: the symptom, where internal data attaches to your file, copy-paste lines to reset anchors, and mistakes that lock a low floor early.
How salary data is used internally during your hiring process
Decision rule: treat every salary touchpoint as data entry, not casual chat. Internal salary data is the approved band for the req, peer pay already on payroll, and every expectation field plus recruiter note attached to your profile.
Comp teams set a min and max for the title and location before the req goes live. Recruiters are told to stay inside that band unless a manager documents a level change. That band is real, but it is not the only number in the system. Your application expectation, your screen answer, and sometimes your current pay field sit beside it in the ATS profile.
When offer time arrives, the path of least resistance is to land near the intersection of band and what you already said you'd accept. Managers who wanted to pay higher still need a reason on the worksheet. Your early anchor is the easiest reason to stop pushing.
Before: You enter a single low figure in a required Workday field because you fear being filtered out.
After: You enter the bottom of a researched band and reopen range on the screen with level language.
Before: You tell the recruiter your current paycheck first when they ask what you're targeting.
After: You answer with market range for this title, then ask what they budgeted for the level on the req.
This is not about tricking anyone. It is about knowing which fields persist so you don't negotiate against your own typed data three weeks later.
Trace where your number sticks on the file
Run this like a checklist the next time you're in process. Each step is a place internal salary data gets copied forward.
Step 1, portal expectations: Greenhouse and Workday often store desired salary in the candidate profile. Recruiters see it on the first open. If you typed one number with no context, assume it traveled.
Step 2, recruiter screen notes: Free-text fields capture what you said out loud. I've watched comp partners quote my screen notes back verbatim when they build the offer worksheet, even when the manager later described a bigger scope.
Step 3, level on the req: Bands attach to grade. If your resume still reads one level down, the band attached to your profile may be lower than the work discussed in interviews. Fix level on paper before you argue about base.
Step 4, hiring manager input: Managers recommend a point inside the band. If your stated range sits below their first pick, the default adjustment is toward you, not toward the top of band they never had to disclose.
Step 5, offer approval: HR routes the package against band and internal equity. Exceptions need narrative. Your own earlier number is the narrative they already have.
Step 6, written offer: Compare base, bonus, equity, and benefits against your private band note, not against what you whispered on call one. If scope grew, say so on the offer call and tie the ask to level, not guilt.
What to do when the profile already shows a low anchor
Do not pretend the field is empty. Name the change: "Since we mapped the role to [title], my range for this scope is [band]. What did you budget?" That gives recruiters a clean note to replace the old one instead of stacking contradictions.
For timing on when to say that out loud, see when to discuss salary in hiring so you match stage instead of reopening pay in every email thread.
Copy-paste lines that reset the anchor
Portal comment field (when the form forces a number):
Target base for [title] in [metro]: roughly $X to $Y depending on bonus and level. Happy to align once scope is confirmed on a screen.
Recruiter screen (band plus question back):
{`For this level in [city], I'm looking at about $X to $Y base. What range did comp approve on the req?`}
After scope expands in manager rounds:
Given the team size and ownership we discussed, my range for this scope is $X to $Y. Can we confirm the level on the req matches that work before offer?
Current pay redirect:
{`I'm focused on market range for this role and level rather than my last paycheck. For [title] here, I'm targeting about $X to $Y base. What band did you budget?`}
Keep a one-page private note: floor, target, bonus expectation, and must-have benefits. Update it after manager rounds when scope shifts so you're not rebuilding math on the offer call with tired eyes.
Anchor mistakes that shrink internal offers
- Single-number anchors: one figure on a fifteen-minute screen becomes the offer starting point in recruiter notes.
- Typing desperation lows in portals: automated filters are real, but a fake floor still lives on the profile after you're screened in.
- Leading with last employer pay: trains the system on your old band, not the market for this req.
- Ignoring level on the req: fighting for base while the title stays junior locks you into that band's ceiling.
- Never revisiting range after scope grows: leaves the original screen note as the only salary story on the file.
I've seen polite candidates lose headroom not because comp had no budget, but because their own expectation field gave approvers an easy yes at the lower number.
Align level on paper before comp talk
Internal bands attach to the level on your resume as much as to the job title in the posting. If you read junior, you often get junior band math even after strong interviews.
Score your job match against the posting at the band you want, then fix the first bullet under your current role so scope matches the req language.
If you need a clean one-page base before tailoring, build your resume in a single-column layout that still parses in Greenhouse.
When a portal asks for a short note with your application, generate a cover letter that sells scope fit, not your pay target.
Pair that file work with total compensation vs base salary so you compare offers on the full package, not just the anchor line recruiters repeat.
What to do tonight
Sequence: research a band for the title, enter a range instead of a floor in portals, confirm level after manager rounds, then negotiate total comp on the offer call using your private note, not your first nervous number.
How salary data is used internally is blunt: bands set the fence, and your stated range tells them where to stop inside it. You win by giving them a credible band tied to scope and asking what they budgeted before you treat silence as extra budget.
If they still will not share any band after you gave a fair range, treat that as data about transparency, not as proof you asked wrong.
Read more
Frequently asked questions
It often becomes the first anchor in the file. Recruiters and comp partners treat portal expectations as signal even when the posting was silent. A low number can sit in the profile through screens unless you reopen the conversation with a researched band tied to level and location.
Sometimes, but it takes a manager fight and a documented level change. Most offers start inside the approved band for the title. If your stated range sits below that band, the default path is to meet you near your number, not at the top of budget they never had to show you.
They use it as another anchor when policy allows, and to check internal equity against peers already on payroll. It is process and risk control, not a quiz you failed. You can redirect to market range for the role instead of leading with last year's paycheck.
In the req's approved band, the applicant profile expectation fields, recruiter screen notes, and the offer worksheet comp uses at approval. Those systems do not always talk to each other cleanly, but the lowest credible number you gave usually travels the farthest.