How to compare your pay with job titles without turning a benchmark into a fantasy.

Reference bars are useful, but only if you know what they are and what they are not. A job title is a rough container, not a full description of the market value of a human being in a specific place doing a specific version of that work.

Why the bars exist

The bars on EarningsBar are there to give your number a visual anchor. A raw hourly rate floating in empty space is hard to interpret. Put it next to familiar roles and it becomes easier to locate. That is the benefit.

The danger appears when people start treating those bars as precise destiny. They are not.

Median is not the same as “what people like me get”

Median pay is useful because it is less distorted by outliers than an average. But a median still describes a broad distribution. It does not know your city, your employer, your industry niche, your seniority, your negotiating leverage, or the peculiarities of your actual workload.

If your rate sits below a reference bar, that does not automatically mean you are underpaid. It means the benchmark deserves a closer look. Sometimes the explanation is obvious: geography, benefits, skill level, or a title mismatch. Sometimes the benchmark reveals a genuine problem. The bar is the start of the question, not the final answer.

Title drift is real

Job titles are messy. “Data analyst” can mean one thing in a large enterprise, another in a small agency, and something else entirely in a startup. “Software developer” can stretch from junior implementation work to highly specialised engineering. That is why broad title-based comparison must stay broad.

Use benchmarks in layers

Start with a broad title anchor, like the bars on the site.
Adjust for geography and cost of living if your market is very different from the benchmark market.
Adjust for seniority and responsibility.
Adjust for benefits, stability, and work intensity.
Only then decide whether the comparison tells you anything actionable.

What the bars are best at

They are best at catching obviously skewed interpretations. If someone says a monthly number is “pretty good” and the derived hourly rate lands far below a cluster of ordinary benchmark roles, that is a sign to look harder. If your derived hourly rate lands above a set of benchmarks you assumed were out of reach, that is also informative.

What the bars are worst at

They are bad at resolving close calls, pricing niche expertise, and comparing compensation packages with very different non-cash components. A benchmark bar cannot capture a rare certification, equity package, unusual regional premium, or a role whose title badly undersells what the work actually is.

The right attitude

Treat the bars as orientation tools. They help you frame the discussion. They do not replace the discussion. The useful habit is to combine the benchmark with the schedule-aware conversion on the homepage. First get your pay into a comparable hourly rate. Then use the bars to ask better questions.

That pairing is where EarningsBar is strongest: arithmetic first, context second.

Last updated: 2026-04-20