How to Research Salary for Your Role and City

12 min read

Salary research only works when you match level band, total comp stack, and work location before you compare numbers. Most candidates skip that step, grab one headline figure from a generic title search, and wonder why the recruiter's band looks nothing like what they found online. The fix is triangulation: base, bonus, and equity from three source types, all filtered to the same title level and city rules.

You've got three tabs open and none of them agree. That's normal when you're comparing a senior title at a startup to a mid-band corporate posting. Before you type a number into Workday, check your resume for free against the posting. You're confirming your file reads at the level you're about to price, not one band below because the title line still says a generic label.

Job searching under financial pressure is brutal, and a wrong range can get you filtered before anyone reads your bullets. This page walks through why salary research breaks, how to spot which mistake you're making, and what to paste into your worksheet tonight. When the posting asks for expectations in a cover letter, use the cover letter generator so the level in the letter matches the band you're quoting.

You won't find a magic number here. You'll find a method that stops you from naming a range built on mismatched inputs. That's the difference between sounding informed and sounding out of touch on the recruiter screen.

When salary research gives you three different stories

The symptom is easy to spot. You run the same title and city through two paths and get bands so far apart they cannot both be right. You are not bad at research. You are comparing inputs that were never meant to match.

Recruiters filter on band fit before they debate your bullets. When your stated range sits outside the approved band, the file often stops in the ATS or on the recruiter's first pass. The resume never gets a fair read because the number told a different level story than the experience block.

Three causes show up again and again. Title inflation without level band. Base-only comparison when the role pays on a total comp stack. City averages that ignore remote, hybrid, or HQ-location pay zones. Most failed research is one of those three, sometimes all at once.

Cause 1: Same title, different level band

"Analyst" at a ten-person startup and "Analyst" at a Fortune 500 firm are not the same search query. One might map to entry scope. The other might sit two bands higher with manager sign-off and budget ownership. Aggregators blend those into one blob unless you filter by years of experience and company size.

Internal titles make it worse. You were "Customer Success Manager III" and the market label is "Senior Customer Success Manager." If you research the wrong label, every downstream number is noise. The posting's level language is the anchor, not the title on your offer letter from four years ago.

I've screened salary fields in Greenhouse where the candidate quoted a senior band while the resume still read mid-level on scope. The number and the file disagreed, and the recruiter moved on before the hiring manager ever opened the PDF.

Cause 2: Comparing base salary to total compensation

A role with a moderate base and a real bonus target is not comparable to a higher base with no variable pay. Equity at a late-stage private company behaves differently than refresh grants at a public firm. Candidates who research base only walk into screens quoting a range that sounds high or low depending on which side of the stack the employer weights.

Sales and success roles often split base and commission. Product and engineering seats at growth-stage firms may trade base for equity. Government and nonprofit bands are often published as base with predictable steps. Your worksheet needs a row for each layer, even when one row says "not applicable for this search."

For how base fits into the full offer picture, see total compensation vs base salary . Research the stack the employer actually uses, not the headline that showed up in a generic search.

Cause 3: City label without work arrangement

Metro averages assume you live and work in that metro under a standard office arrangement. Remote roles tied to a HQ city often pay on zone tables you cannot see from a city name alone. Hybrid three-days-in-office roles may track the office metro more closely than fully remote seats with no location requirement.

Relocation adds another variable. A Denver posting with relocation support is not the same comp math as a Denver posting that expects you local on day one. Cost of living matters for your budget, but employers price against their band tables and competitor sets first.

Edge case: you are remote in a low-cost area targeting a coastal HQ employer. Research the employer's stated pay zone or HQ metro, not only your home city. Edge case: multi-state travel sales roles. The city on the posting may be territory center, not where payroll taxes land.

How to research salary for your role and city without mixing signals

Start by writing four labels at the top of a blank doc: official posting title, level band, city or pay zone, and work arrangement. Every source you touch gets those four tags. If a source cannot be tagged, it does not enter the range yet.

How to tell which cause is breaking your research

If bands swing wildly when you change the title slightly, you have a level-band problem. Fix the title first. If bands converge on base but diverge on "total pay," you are mixing comp stacks. If bands only make sense when you ignore where you live, you have a location or remote-zone mismatch.

Run a five-minute check. Pick one posting you would actually apply to. Copy its level line verbatim. Search that exact string plus your city. If results still look like three different jobs, split the search by company size before you average anything.

Fix 1: Lock the level band before any number

Map your current scope to the posting's ladder. Count years in the seat, people managed, budget owned, and tools named in the posting. If the posting says "Senior" in the first line, research Senior variants only. Drop generic title searches until the band is stable.

Before: A operations coordinator researches "Operations Manager" because that is the next step they want. Postings they target still say "Coordinator II" with manager-track language.
After: They research "Operations Coordinator II" in their metro for companies with similar headcount, then note the senior manager band as a separate column for negotiation after scope proof lands in the interview.

Fix 2: Build the comp stack row by row

Create five rows: base, annual bonus or commission target, equity grant or refresh, signing bonus, and benefits you would actually use. Not every row applies to every search. A public-sector band might be base plus step increases only. A startup offer might be base plus options with no bonus line.

Before: A mid-level marketer compares a posted base from one employer to a friend's "total comp" anecdote that included commission and stock.
After: They list base ranges from postings, ask one trusted contact for base and bonus split only, and leave equity as a separate note until the employer names grant size in writing.

Fix 3: Tag city, zone, and arrangement on every source

Government occupational tables by metro give a floor for many professional roles when you match the standard occupational code to your band. Live postings with listed bands show what employers currently advertise in your market. One human signal from someone in a similar seat catches zone tables and nuance tables miss.

Those three source types rarely match to the dollar. They should point the same direction. When government tables, live postings, and a human signal all land in the same band for the same tagged title and city, you have a defensible range.

When applications ask for desired pay early, read how to answer desired salary on US applications so the range you researched fits the field without oversharing on the resume itself.

Operations analyst, Midwest metro (level-band fix)

Before: A candidate researches "Business Analyst" nationally and quotes a senior band on a coordinator posting.
After: They retag as "Operations Analyst II," pull metro government tables for that occupational family, collect four local postings with listed bands, and ask one former colleague for base-only range. The three sources cluster in the same band. They quote a range on the application form, not in the resume header.

Implementation lead, remote with HQ on the coast (location fix)

Before: A remote candidate in a smaller metro researches salary for their home city only and names a range the recruiter's zone table cannot approve.
After: They research the employer's HQ metro zone, note "fully remote" on each source, and split base from equity on the worksheet. The quoted range tracks the zone. They ask about geo adjustment on the recruiter screen instead of arguing from mismatched city labels.

Copy-paste salary research worksheet

ROLE RESEARCH WORKSHEET
Posting title (verbatim): _______________________
Level band (posting language): __________________
City / pay zone: _______________________________
Work arrangement: onsite / hybrid / remote_______
Company size bucket: startup / mid / enterprise__

SOURCE 1 - Government metro table (occupational code + band): ___________
SOURCE 2 - Live postings (link + listed band + date saved): ____________
SOURCE 3 - Human signal (role + metro + base/bonus split only): ________

COMP STACK (range per row, not one headline number)
Base: __________   Bonus/commission: __________
Equity: __________   Signing: __________________
Benefits that matter to you: ____________________

QUOTE RANGE (only when three sources agree on direction)
Floor (walk-away total): _______________________
Target (expected total): _______________________
            

Fill one worksheet per target band. Do not merge startup and enterprise rows into one average. Save the doc with the company name when you tailor an application so you do not reuse a zone table from the wrong employer.

When triangulation still will not converge

Sometimes honest research still spreads wide. That usually means the role is poorly defined in the market, not that you failed. These patterns explain the gap.

New title, no market history. "AI Operations Lead" might map to three different occupational families. Pick the closest standard title for research and note the translation in your screen prep. You are building a case, not finding a perfect match.

Contract vs W-2. Hourly contract rates do not convert cleanly to salaried bands without benefit load and gap risk. Research contract day rates separately from W-2 postings. See W-2 vs 1099 when applying in the US if the posting blends employment types.

Academic or fellowship stipends. Postdoc and fellowship pay follows grant tables, not corporate bands. Do not compare those to industry offers on one worksheet. Transition searches need two worksheets, one per track.

Outlier anecdotes. One friend's offer at a hot company is not a source type. It is color. Keep it off the worksheet unless you can tag their level, metro, comp stack, and year. Stories without tags inflate ranges fast.

Edge case: internal promotion with no posting. Research the external market for your new title anyway, then ask HR which band the promotion mapped to before you counter. Edge case: union or step schedules. Published steps are your source one. Private sector postings are the wrong comparison set.

When your range might screen you out early, read how salary signals affect screening so you know where the number is read relative to your resume.

Match your file to the band before you name a number

Salary research and resume level must tell the same story. A senior range with mid-level bullets is a common auto-reject. Align the file first, then quote the band you can defend in a screen.

Score your job match against the posting you used to label your level band. You are checking that title, scope words, and seniority signals in the file match the role you priced. Fix the experience block before you enter compensation on the form.

Run the ATS checker on the export with the posting pasted in. Manager keywords should sit under the title line that matches your salary research label. If the parser reads a lower title than the band you quoted, recruiters see the same mismatch the worksheet cannot fix.

Save the tailored PDF with the company name and the band you quoted. When the recruiter calls, open that file, not a generic master. The range, title, and bullets should trace back to one posting.

Build the range tonight

How to research salary for your role and city comes down to matching level band, comp stack, and location before you compare anything. Triangulate from government metro tables, live postings, and one tagged human signal. Quote a range only when all three point the same direction.

Open one target posting. Copy its level line. Fill the worksheet. Tag every row. Split base from bonus and equity. Paste your resume into plain text and confirm the title scope matches the band you are about to name.

You do not need perfect data. You need consistent labels. Recruiters can work with a tight range backed by coherent scope. They cannot work with a senior number on a mid-level file because the research skipped the title line.

• One worksheet per level band and pay zone.
• Three source types before you quote.
• Comp stack rows, not one headline figure.

Check your resume for free against the posting before you submit the range. When the file and the number tell the same level story, you stop getting filtered on pay before anyone reads your work.