live · modelled against state × level × cloud × spec × cert

Is the DevOps offer in front of you
below market, at market, or top of band?

Most negotiation advice is generic. This evaluator drops your base, bonus, equity, and signing onto a modelled band built from the BLS OEWS May 2025 state median for SOC 15-1252, then market-comp level, cloud and specialisation multipliers. You get a verdict, and a counter-target, in one screen.

offer-evaluator.input
$ your_offer
$ your_profile
$ certifications [optional]
verdictAT MARKETbase -10.1% vs mid
band lowmidband high
$181,386$205,804$230,221
Your base
$185,000
vs mid: -10.1%
Modelled mid
$205,804
P75-P90 pctile
Modelled high
$230,221
top of band
total comp comparison
Your total
$247,000
base + bonus + RSU + signing
Modelled mid TC
$241,837
range $195,897–$287,776
Gap
+$5,163
+2.1% vs mid
recommended move

Base lands inside the band. Solid offer. Focus your negotiation on equity, signing bonus, or on-call rather than base.

Counter target (mid)
$205,804
Counter ceiling (high)
$230,221

The band starts from the BLS Occupational Employment and Wage Statistics (OEWS) annual median for SOC 15-1252 Software Developers in the state you pick (snapshot 6 September 2026), then applies experience-level, cloud-platform and specialisation multipliers with cert and on-call layered on top. Those multipliers are market-comp (Levels.fyi, Glassdoor, Built In and Blind self-reports), not BLS, and "DevOps engineer" is not an OEWS occupation. This is a planning tool; verify against current Levels.fyi and offer letters before negotiating.

01 · band

Built from state medians

Every state has a different DevOps median. California sits ~17% above the national mean; Mississippi sits ~29% below. The band starts there, not at a one-size US number.

02 · multipliers

Level, cloud, specialisation

Senior DevOps lands at 1.04x-1.32x of the state median. MLOps and DevSecOps carry 20-27% premiums over General DevOps. Multi-cloud adds 12% over single-cloud.

03 · verdict

Below / at / top / above

Below 90% of band low triggers BELOW MARKET. Top 5% triggers ABOVE MARKET, usually meaning you should verify the level title. Everything in between is broken into low/mid/top of band.

What to do once you have the verdict

The verdict is a signal, not an answer. Here is the move that usually fits each band.

BELOW MARKET

Base below 90% of band low

Counter hard with the modelled mid as your anchor. Cite state median + level multiplier + cloud + specialisation. If they will not move materially, walk. Recruiters lowball candidates who do not push back.

LOW BAND

Base between band low and midpoint

Most candidates with your profile land higher. Push base first because every component above (bonus, equity, retirement match) is pegged to base. Counter at mid or 5-7% above.

AT MARKET

Base within 5% of midpoint

Solid offer. Negotiate the perimeter rather than the centre: signing bonus, equity refresh schedule, on-call stipend, certification budget, remote flexibility. These come from different budget lines and are usually more flexible than base.

TOP BAND

Base between midpoint and band high

Strong offer. Accept it without a counter, or counter once gently (signing bonus, equity refresh). Pushing for above-band on base risks the offer being withdrawn or signalling poor judgement.

ABOVE MARKET

Base exceeds band high by more than 5%

Verify the level title against the company's published ladder. You may be slotting into a higher band than you entered into the evaluator. If the level is right, this is a genuinely strong offer, accept and focus on equity vesting cliffs and refresh schedule.

How the band is calculated

The evaluator starts from the BLS Occupational Employment and Wage Statistics May 2025 annual median for SOC 15-1252 Software Developers in the state you pick, snapshot taken 6 September 2026. That SOC is the closest published occupation to a DevOps engineer, which is not itself an OEWS occupation; SOC 15-1244 Network and Computer Systems Administrators is the operations-side bracket. The median is then multiplied by an experience-level range, a cloud-platform multiplier and a specialisation multiplier, all of which are market-comp judgement rather than BLS. Certifications and on-call stack on as additive amounts. Alaska has no published median in the May 2025 file, so the evaluator abstains there rather than substituting a national or neighbouring figure.

band-formula
base_low = state_median × level_min × cloud_mult × spec_mult
base_high = state_median × level_max × cloud_mult × spec_mult
base_mid = (base_low + base_high) / 2
total_low = base_low × 1.08 + 0.5 × certs + on_call
total_high = base_high × 1.25 + certs + on_call

Multiplier ranges

  • Experience: junior 0.60-0.76 · mid 0.80-1.04 · senior 1.04-1.32 · staff 1.28-1.60 · principal 1.44-2.00 · manager 1.12-1.44
  • Cloud: AWS 1.00 · Azure 1.02 · GCP 1.07 · Multi-cloud 1.12
  • Specialisation: General 1.00 · SRE 1.15 · Platform 1.12 · DevSecOps 1.20 · MLOps 1.27 · Cloud Architect 1.22
  • Cert bonuses (additive, capped at $30K): AWS SA Pro $12.5K · CKA $15K · Terraform $7.5K · AWS DevOps Pro $10K · CKAD $11.5K · GCP DevOps $11.5K
  • On-call: $1,250/mo when rotation is included

What this is not

The band is a planning instrument, not a Levels.fyi replacement. Use it to anchor your counter, then verify against named-company data points (Levels.fyi for FAANG/big-tech, Glassdoor for mid-market, recruiter screens for everything else). The band tells you whether the offer is in the right neighbourhood; the named-company data tells you what specific companies are paying.