9 min read
Most candidates treat market data like a trump card they play too early. Recruiters hear a national average before they've mapped you to a level, and the conversation turns defensive. The fix isn't more tabs open. It's matching your research to the employer's band language at the moment they can actually move money.
Check your resume for free while you're still in process. You're not negotiating with a parser, but you won't reach a salary talk if bullet one never matched the req's must-haves in Workday or Greenhouse.
Job searching is stressful enough without guessing when to name a number. You don't need a finance degree. You need a dated sequence: research, silence, review, counter, close.
Below is that sequence, what to skip between phases, and copy you can adapt tonight.
Quick Wins
- Open one comp log row per active final-round employer tonight.
- Save posting title, level hint, metro, and remote policy beside each source note.
- Write your walk-away floor as total comp, not base alone.
Why timing beats a bigger spreadsheet
Employers price roles against internal bands, not your favorite chart. Market data helps when it mirrors their job code: same title family, level, geography, and employment type. Dump a broad range in round one and you signal you haven't read the posting.
Public wage tables lag real postings. Job ads with listed ranges, when your state allows them, show what that company is willing to print today. Professional association reports and union scales matter in licensed fields. Mix source types so you're not arguing from one number.
Before: You quote a single web estimate in the recruiter screen and call it research.
After: You keep a private log with three source types tied to this title and metro, ready for the written offer.
For how bands get set before you ever talk numbers, read how market rates shape job offers . That post explains employer side constraints; this one is your calendar.
Edge case: internal transfer or promotion. External posting ranges may not apply. Ask which job code and geography the band uses, then research that combination instead of your old team title.
How to negotiate salary using market data on a clock
Work forward in order. Skipping a phase usually costs you bargaining room or credibility.
Weeks 1 to 3 of interviews: build the comp log
Each time you reach a hiring manager round, add a row: company, exact posting title, level language from the ad, metro or remote policy, and employment type. Pull ranges from BLS Occupational Employment and Wage Statistics for the occupation and area when it fits. Add recent postings that list pay where legal, employer career pages that publish bands, and any licensed-field wage schedule you can verify.
Note the date on every entry. Stale rows are worse than empty ones because they sound confident and wrong.
Early screens: deflect without freezing
When HR asks for expectations, tie the answer to learning scope: "I'm focused on fit and level. Once we align on responsibilities, I'm open to a competitive package for this role in this location." If they push, offer a broad range only when forced, and label it preliminary.
Before: You share your ceiling and anchor yourself below a band you haven't seen.
After: You keep the conversation on level and repeat that you'll respond thoughtfully to a written offer.
Day 0: verbal offer lands
Thank them. Ask for the full written package: base, bonus target or guarantee, equity grant and vesting, benefits start, PTO, remote or travel expectations, and title level. Say you will review and respond within two business days. Do not counter on the phone unless they've asked for an immediate yes or no on an exploding timeline.
Days 1 to 2: map offer to your log
Open the comp row for this employer. Compare apples to apples: same level string, same metro, same full-time versus contract. Model total comp, not base alone. If bonus is discretionary, treat it as uncertain unless the offer letter guarantees a minimum.
Pick one target number or narrow range you can defend from overlapping sources. If the offer sits below your floor, decide whether to counter, ask for level reclassification, or walk.
Day 2 or 3: send the written counter
Email beats phone for clarity. Lead with enthusiasm, state your target, name source types, and invite questions. Keep it short.
Copy-paste counter skeleton (edit brackets only):
{`Subject: [Your name] – [Role title] offer
Thank you for the offer for [Role title] at [Company]. I'm excited about [one specific team or project detail].
After reviewing the package and comparing similar [level] [job family] roles in [metro or remote policy], I'm requesting [target base or total comp figure] with [bonus/equity expectation in plain words].
My review included [source type 1], [source type 2], and [source type 3, e.g., listed ranges on comparable postings]. I'm happy to discuss level scope if the band differs from the posting title.
Could we schedule a brief call this week to align?`}
Days 3 to 7: negotiate components
If base is firm, ask about signing bonus, equity refresh, extra PTO, title bump, or start date. Get any new promise in the revised letter. Verbal yes on bonus doesn't help if it's not in writing.
I've seen candidates lose the thread by debating national averages while the recruiter held a band keyed to a lower level code. Fix level first, then price.
Signature: pause before you click
Read the final PDF for title, start date, at-will language, and bonus clauses. Compare against your floor. If you're choosing between offers, use a scorecard instead of vibes. See how to compare two offers with a scorecard before you accept the faster yes.
Deeper research tactics live in how to research salary for your job title and city . Use that page to fill the log; use this page to know when to spend it.
Between-step traps that waste your data
Countering before the written offer. Verbal numbers skip vesting cliffs and bonus language. Wait for the letter so your market comparison includes total comp.
Mixing levels in the log. Senior in the posting isn't senior in the band file. Match the employer's level hint, not your self-title.
Before: You attach ten screenshots and no clear ask.
After: You send three sentences, one target, and offer a call.
Ignoring geography and remote policy. A remote role tied to a high-cost HQ often prices differently than fully location-neutral pay. Tag each source with the geography it assumes.
Accepting because the process felt long. Fatigue isn't data. If the package sits under your floor, ask once more or walk. Read should you accept a job offer quickly before you click accept out of relief.
Keep proof aligned while you wait
Negotiation starts after you're the finalist. While interviews run, score your job match on each late-stage posting so bullet one still mirrors must-have tools. A strong comp case dies if the file barely matched the req.
When the offer letter references start date or relocation, generate a cover letter draft only if you need a short written note for HR about start timing or visa paperwork. Don't repeat salary math in the letter; keep numbers in the offer thread.
Do this now: Add one comp log row for your hottest process, tag three source types with today's date, and block two hours after the written offer lands before you reply.
Sign when the package matches your floor
Market data isn't a mood booster. It's a calendar discipline: log early, speak late, counter in writing, and negotiate the whole package. When the letter matches the role you priced, sign. When it doesn't, you still have words left.
- One comp row per finalist employer with dated sources.
- Written offer before hard counters.
- Total comp math, not base alone.
- Revised letter in hand before you celebrate.
Run a free ATS check on the resume that got you this far. You'll know whether proof lines still match the posting before you stake your next ask on them.
Read more
Frequently asked questions
Start a private comp log as soon as you're in late-stage interviews, not after the verbal number lands. Match title, level, metro, and remote policy to each row. You can't negotiate with data you haven't collected yet, and employers move faster once they pick a finalist.
Usually no. Name two or three source types you used, such as public wage tables and recent postings with listed ranges, and state your target in plain language. Attach screenshots only if they ask. The goal is a calm business case, not a folder that reads like a debate club submission.
That's normal when sources mix national tables with local postings. Pick a defensible target inside the overlap for your level and geography, then explain which factors push you up or down: scope, niche skills, travel, or shift requirements. Wide ranges are why you negotiate total comp, not a single base guess.
You can reopen before you sign the written offer if you discovered a band mismatch or missing components. Send one professional note with your updated target and the same role details. After signature, treat base changes as a future review conversation unless they materially changed the job.
It still helps you decide whether to accept, walk, or shift the ask to signing bonus, equity refresh, title level, or start date. Fixed band language often means base is tight, not that every dollar of value is gone. Data tells you if the whole package is below your floor.
