Software Developers salaries in Provo-Orem-Lehi, UT
What software developers earn in the Provo-Orem-Lehi, UT area, from US Department of Labor payroll data covering the 7,870 employed there.
What the role earns here
Half of software developers in Provo-Orem-Lehi, UT earn between $99,500 and $164,560, with a median of $131,210. Bureau of Labor Statistics — employer-reported payroll, 7,870 employed · OEWS-May2025.
What sponsored roles here attest
Employers sponsoring H-1B workers for this role in Provo-Orem-Lehi, UT formally committed to a median of $123,105 ($104,083–$154,750), across 70 certified filings · FY2026-Q2. That is a narrow, self-selected slice of employers — see the note at the foot of this page — and it runs 6% below the earnings median above.
How Provo-Orem-Lehi, UT compares
The median here is 4% below the national figure for software developers ($135,980), which puts Provo-Orem-Lehi, UT 36th of the 94 areas with a published wage estimate for this occupation.
Areas that pay similarly
The nearest medians on either side of Provo-Orem-Lehi, UT — the useful comparison for someone weighing a move, rather than the same handful of top-paying metros on every page.
| Area | 25th | Median | 75th | Employed |
|---|---|---|---|---|
| Palm Bay-Melbourne-Titusville, FL | $101,910 | $131,760 | $163,040 | 5,030 |
| Phoenix-Mesa-Chandler, AZ | $104,230 | $131,750 | $163,370 | 29,380 |
| Boise City, ID | $99,990 | $131,590 | $161,350 | 3,240 |
| Minneapolis-St. Paul-Bloomington, MN-WI | $103,040 | $130,920 | $161,610 | 27,410 |
| Detroit-Warren-Dearborn, MI | $101,850 | $130,760 | $153,270 | 24,870 |
| Providence-Warwick, RI-MA | $101,950 | $130,690 | $159,540 | 5,020 |
| Madison, WI | $101,970 | $130,630 | $161,050 | 6,720 |
| Peoria, IL | $107,280 | $130,590 | $158,060 | 1,650 |
← All software developers salaries by area
→ Everything hiring in Provo-Orem, UT — openings, the skills they ask for, and who is hiring.
Where these numbers come from
The pay figures on this page come from the US Department of Labor's Bureau of Labor Statistics wage series — payroll figures employers report from their own records, covering everyone working in the occupation rather than only those who happen to answer a poll. Nobody self-reported them, and no salary here was submitted by the person earning it.
What that does and does not tell you. These are earnings of people already in the job, not the pay advertised on current openings — and advertised pay tends to run above them. It is a sample of employers, not a count of all of them, so every figure is an estimate. The number beside each band is how many people work in the occupation in that area: it says how substantial the local workforce is, not how many employers were surveyed. And BLS publishes no margin of error for the percentiles — only for the employment count — so treat the median as a solid central figure rather than a precise one.
Where the second band comes from. Some pages also show what employers formally attest they will pay a sponsored worker, from H-1B Labor Condition Application disclosures. Those are real, filed, public wages and the employer is legally bound by them — but the population is only employers who sponsor work visas, which is neither everyone hiring for the role nor a random sample of them. Sponsorship concentrates in large, well-paying technology employers and in IT staffing firms that file toward the lower end, and we have not measured which effect wins. So it sits beside the earnings band, never averaged into it: there is no meaningful figure halfway between what a role pays and what a visa filing committed to.
What we deliberately do not show. Any area with fewer than 100 people in the occupation, or where the estimate is too thinly sampled to stand behind (current data: OEWS-May2025). And any trend or year-on-year change: we hold a single release, and drawing a line through one point would be inventing a finding. When a second lands the trend appears here, and not before.
This covers the pay figures on this page. For the postings, the AI extraction and the market estimates — and the full list of things we deliberately do not claim — see our methodology.