Skip to content

Salary guide

Software Engineer salary

Software engineer compensation here is a US band, not the BLS median for software developers and not an offer from an employer. BLS also groups testers into the same handbook chapter, then splits the wages. Check the posting's level and whether the number is base salary or total pay.

Illustrative total comp

$95k–$230k

Midpoint
$150k

$95k$230k

What moves the range

  • Seniority
  • Company tier and stage
  • Tech-hub location
  • Equity

The band above is not the BLS median for software developers, and it is not the separate median BLS publishes for quality assurance analysts and testers. Career guide.

Software Engineer, Software role. AmazApply editorial team, Software role. , Software role. , Software role. AI drafted this Software role page.

Software Engineer pay comparison diagram. Work: improving a service while keeping production behavior stable. Proof: a design note, test plan and rollout checklist. Check: latency, error rate and operational maintenance effort.
Software Engineer pay comparison diagram. Work: improving a service while keeping production behavior stable. Proof: a design note, test plan and rollout checklist. Check: latency, error rate and operational maintenance effort.

Developer wages and tester wages are not this band

BLS publishes developer wages separately from testers inside one handbook chapter. AmazApply's software engineer band is not either figure. When you compare offers, split base, bonus, and equity, and ask whether a remote range changes with your home location.

On-call and level belong in the comparison

Judge a software posting by what is live: on-call, legacy code, and who approves architecture. A greenfield promise with no maintenance is a question, not a match. Ask what the last production incident required of this seat. That answer tells you more than a stack diagram.

Do not treat a tutorial language as leverage

Skills such as testing and code review count when a bullet shows the review changing a design. A language you completed a tutorial in is exposure, and the skills list should say so or leave it off. Version control is assumed. The interesting part is how you rolled a change back.

Résumé bullets should stay readable without your old employer's nicknames. Name the constraint first, then the change. A claim of 5 million requests or a perfect availability number is off-limits unless it is your number from a system you can describe. Test coverage you did not own should not be written as if you built the suite.

Remote ranges can depend on where you live

Pick a production change for a software engineer application: the service, the design note, and the rollout check. Latency, error rate, or the hours you spent keeping it up are fair measures when you have them. A faster path that weakened data handling belongs in the story. Say what you personally merged versus what the team reviewed.

Sources