Salary Intelligence

Salary Data by Role and Location

Percentile salary ranges from 45 role+city combinations across 45 roles. All numbers come from job postings with disclosed pay, refreshed monthly.

45

Roles

45

City Combos

Software Engineer

1 city

Backend Developer

1 city

Fullstack Developer

1 city

Mobile Engineer

1 city

Data Engineer

1 city

Frontend Developer

1 city

DevOps Engineer

1 city

Platform Engineer

1 city

Site Reliability Engineer

1 city

Network Engineer

1 city

Cloud Engineer

1 city

Solutions Architect

1 city

AI Engineer

1 city

Machine Learning Engineer

1 city

Data Scientist

1 city

Data Analyst

1 city

Security Engineer

1 city

QA Engineer

1 city

Support Engineer

1 city

Product Analyst

1 city

Content Marketing

1 city

SEO Specialist

1 city

Customer Success

1 city

Product Designer

1 city

UX Designer

1 city

UI Designer

1 city

Project Manager

1 city

Scrum Master

1 city

Technical Writer

1 city

Account Executive

1 city

Sales

1 city

Revenue Operations

1 city

Business Analyst

1 city

Financial Analyst

1 city

Compliance Analyst

1 city

Recruiter

1 city

Supply Chain Manager

1 city

Civil Engineer

1 city

Mechanical Engineer

1 city

Electrical Engineer

1 city

Nurse

1 city

Product Manager

1 city

Marketing Manager

1 city

Operations Manager

1 city

HR Manager

1 city

How We Collect Salary Data

ShouldApply pulls job postings from 4 boards every 2 hours: JSearch, Remotive, Adzuna, and Wellfound. When a posting includes an explicit salary range, we normalize it to an annual figure and tag it with a role classification and city. Hourly, weekly, and monthly rates are all converted. We discard anything below $15K or above $500K as outlier data. The benchmarks you see here require a minimum of 5 postings per role/city pair before we publish.

What the Percentiles Mean

Each salary page shows five percentile markers: 10th, 25th, 50th (median), 75th, and 90th. The "typical range" is the 25th-75th band, which covers the middle half of disclosed salaries. The 10th percentile often reflects entry-level or smaller-company postings. The 90th captures senior positions and top-paying employers.

Why This Beats Glassdoor Estimates

Self-reported salary surveys carry bias. People who feel overpaid or underpaid are more likely to report. Our data comes from employer-disclosed ranges in actual job postings, which reflect what companies are offering right now. Sample sizes are smaller, but the signal is cleaner.

Frequently Asked Questions

How often is salary data updated?

Benchmarks are recomputed monthly from all scored job postings in our database. The underlying job data refreshes every 2 hours across 4 boards.

What's the minimum sample size for a salary page?

We require at least 5 job postings with disclosed salary for any role+city page to appear. Pages with fewer than 10 postings carry a "low confidence" label.

Do these numbers include bonuses or equity?

No. These are base salary ranges as listed in job postings. Total compensation (including bonuses, equity, and benefits) varies by employer.

Can I see salary data for remote roles?

Remote positions don't have a city attached, so they're included in the national aggregate for each role but not on city-specific pages.

How does this relate to the salary estimator tool?

The salary estimator uses static heuristics for roles that don't list pay. These benchmark pages use real disclosed salary data from actual postings. Both are free.

Role IntelligenceSalary EstimatorJob MarketsBrowse Jobs

Salary is one dimension. What about skills, seniority, and logistics?

ShouldApply scores your full profile against every posting. 0-100, with a breakdown.

Try it free