Computer Network Architects: Utah vs Washington pay

Percentile	Published wages	Utah	Washington
10th	Utah$75,640Washington$93,610	$75,640	$93,610
25th	Utah$99,180Washington$126,470	$99,180	$126,470
Median	Utah

Place	Employment	Jobs per 1,000	Location quotient	Employment RSE
Utah	1,330Jobs per 1,000: 0.77 Location quotient: 0.66	0.77	0.66	10.9%
Washington	4,730Jobs per 1,000: 1.33 Location quotient: 1.15	1.33	1.15	4.8%

75th	Utah$150,170Washington$200,940	$150,170	$200,940

90th	Utah$182,790Washington$224,910	$182,790	$224,910

Start with the answer

Computer Network Architects pay in Utah and Washington

The May 2025 BLS OEWS median for Computer Network Architects is $121,000 per year in Utah. It is $168,070 per year in Washington. Utah is 28.0% below Washington on the published median.

Both rows use SOC 15-1241 and the same annual wage metric. Median means the middle of each area's published wage spread. It is not one worker's pay. The larger median is not proof that one place gives a better job or a better result. It is one wage fact from one source period.

BLS lists 1,330 wage and salary jobs in Utah and 4,730 in Washington. Those are survey job counts, not open posts. Read pay, job scale, local share, and price level as separate facts before you make a choice.

Evidence: bls-oews-may-2025 · Rule: same-soc-same-metric-pair · nominal-median-gap · employment-not-openings

Pay range

Compare the full Computer Network Architects wage ladder

A median can hide a wide range. The 10th, 25th, 50th, 75th, and 90th percentile points show more of each area's spread. A percentile is a rank point. It is not a career stage. The 10th point does not mean new-worker pay. The 90th point does not mean a wage that comes after a set number of years.

The lower half can differ from the upper half. One area can lead at the median and trail at another point. Read each field against the same field in the other area. Do not compare one area's 75th percentile with the other area's median. That would answer a different question.

A posted job range can sit below, across, or above these marks. That does not make the post wrong. A listing can differ by employer, level, hours, field, or work rules. Keep the listing tied to that employer. Keep the BLS range tied to the whole role-place row.

10th percentile: Utah is $75,640 per year; Washington is $93,610 per year. Utah is 19.2% below Washington at this point.
25th percentile: Utah is $99,180 per year; Washington is $126,470 per year. Utah is 21.6% below Washington at this point.
Median: Utah is $121,000 per year; Washington is $168,070 per year. Utah is 28.0% below Washington at this point.
75th percentile: Utah is $150,170 per year; Washington is $200,940 per year. Utah is 25.3% below Washington at this point.
90th percentile: Utah is $182,790 per year; Washington is $224,910 per year. Utah is 18.7% below Washington at this point.

Evidence: bls-oews-may-2025 · Rule: paired-percentile-fields · same-field-comparison · posted-pay-separation

Shape of pay

Mean and median tell two parts of the Computer Network Architects story

Utah has a mean of $127,970 per year and a median of $121,000. Washington has a mean of $164,930 per year and a median of $168,070. Mean adds all wage values and splits the total by the number of jobs behind the estimate.

Utah's mean is 5.8% above its median on the same published median. Washington's mean is 1.9% below its median on the same published median. The gaps show that each wage spread has a shape. They do not explain why the shape differs.

Use median for the middle. Use mean to see how the full set pulls. Use percentiles to see more of the spread. None of the three is a pay promise. A person, team, or listing can sit far from all three for reasons that are outside these BLS rows.

Evidence: bls-oews-may-2025 · Rule: paired-mean-median · mean-median-gap · no-causal-inference

Job scale

How the two Computer Network Architects job bases differ

Utah has 1,330 estimated Computer Network Architects jobs. Washington has 4,730. The larger count shows a larger covered job base in this source. It does not show more open roles, faster hiring, or a better chance for one applicant.

Utah has 0.77 Computer Network Architects jobs per 1,000 local jobs. Washington has 1.33 per 1,000. This rate helps compare places of different size. It is not a job-post rate and does not use the MeritLog catalog.

The employment RSE is 10.9% in Utah and 4.8% in Washington. RSE means relative standard error. It is a survey precision flag. It is not the chance that the job count or one person's pay is right.

Evidence: bls-oews-may-2025 · Rule: paired-employment · paired-jobs-per-thousand · employment-rse-field-scope

Local share

Where Computer Network Architects takes a larger share of jobs

The location quotient is 0.66 in Utah and 1.15 in Washington. A value of 1 means the role has the same share of local jobs as it has across the nation. A value above 1 means the local share is larger. A value below 1 means it is smaller.

Utah's quotient is 42.6% below Washington's. That gap is about the job mix. It is not a wage gap, a job-count gap, or a growth claim.

Read location quotient with employment. A small place can have a high share and few jobs. A large place can have many jobs and a share near the national mark. Then read pay as its own field. The three measures do not form one score.

Evidence: bls-oews-may-2025 · Rule: paired-location-quotient · quotient-gap · metric-separation

BEA price view

How price levels differ between Utah and Washington

BEA's 2024 all-items price index is 98.9 in Utah and 107.0 in Washington. The U.S. level is 100. A higher number means the broad local price level is higher than the national mark. It does not say a place is good or bad.

Housing is 107.8 in Utah and 126.0 in Washington. Goods are 96.4 and 104.4. Utilities are 78.7 and 92.9. Other services are 99.0 and 103.9. The parts can move in different ways.

The wage period is May 2025. The price period is 2024. WageScope keeps those clocks visible. It uses the all-items index for one clear proxy. It does not mix BEA prices into the BLS source row, and it does not claim the two releases describe the exact same month.

Evidence: bea-rpp-2024 · bls-oews-may-2025 · Rule: paired-rpp-fields · rpp-us-baseline · source-period-separation

Price-level proxy

Compare the medians in national-price dollars

WageScope divides Utah's $121,000 median by 98.9 divided by 100. The result is $122,390 per year. It divides Washington's $168,070 median by 107.0 divided by 100. That result is $157,056 per year.

Utah's proxy is 22.1% below Washington's. The nominal gap is 28.0%. The order can stay the same or change after the price-level step. Both results must keep their labels.

The proxy is a narrow math tool. It is not take-home pay. It does not add taxes, benefits, household size, debt, commute, schools, safety, climate, or taste. It does not set a wage target. Use it to see how one broad price index changes the wage view, then check your own costs outside WageScope.

Evidence: bls-oews-may-2025 · bea-rpp-2024 · meritlog-bounded-comparison-v1 · Rule: price-level-adjusted-formula · nominal-adjusted-gap-separation · proxy-limits

Same-proxy pay

What equal price-level pay would look like in the other place

$121,000 per year in Utah has the same national-price-dollar proxy as $130,974 per year in Washington. The math keeps Utah's proxy fixed, then applies Washington's all-items price index.

$168,070 per year in Washington has the same proxy as $155,272 per year in Utah. This reverse view is useful because the answer depends on which wage you start with. It is not a claim about an offer in either place.

Equivalent nominal pay uses one broad price measure. It does not know what a person buys. It does not know rent, family size, debt, taxes, travel, benefits, or savings. Treat the result as a clean source-backed comparison, not a full move plan or a number an employer must match.

Evidence: bls-oews-may-2025 · bea-rpp-2024 · meritlog-bounded-comparison-v1 · Rule: equivalent-nominal-value-forward · equivalent-nominal-value-reverse · proxy-limits

Data care

Check the survey marks before you use the gap

The mean-wage RSE is 4.6% in Utah and 1.5% in Washington. The employment RSE is 10.9% and 4.8%. RSE is a precision flag for the field it sits beside. It is not a score for the whole page.

BLS does not publish the same RSE field for the median and each percentile. WageScope does not move a mean RSE to the median. It does not use an employment RSE as a wage care mark. Each value stays tied to its source field. Missing or top-coded values also keep their source state.

A later BLS or BEA release can change the result. MeritLog checks the official source clocks before promotion. The page cannot call its data current when a newer complete release is waiting for review. Current job cards have their own seen date and do not make the government data newer.

Evidence: bls-oews-may-2025 · Rule: paired-rse-field-scope · no-rse-transfer · independent-source-freshness

Use the result

A short check list for Utah and Washington

Start with the same Computer Network Architects wage field. Then read the full percentile spread. Check job count, jobs per 1,000, and location quotient. Add the 2024 all-items and housing price levels. Read the national-price-dollar proxy with its limits. Keep the BLS and BEA dates in view.

Next, inspect one current employer-title match in each place when an exact public place match exists. A job post can show work level, hours, location rules, and pay that the BLS row cannot. The post is dated employer evidence. It does not change the survey median or prove a broad trend.

Last, use your own facts. Compare the job needs with work you have done and can support. A wage gap cannot show fit. A price-level gap cannot show fit. A job count cannot show fit. MeritLog's résumé path starts only after you choose a listing and confirm the work facts you want to use.

Evidence: bls-oews-may-2025 · bea-rpp-2024 · meritlog-public-job-boundary-v1 · Rule: comparison-checklist · job-source-separation · confirmed-resume-evidence

Limits

What this Computer Network Architects comparison does not decide

The page does not choose Utah or Washington for you. It does not say what one worker earns. It does not promise a job, offer, raise, or move result. It does not say why the medians differ. It does not turn the larger wage, job count, quotient, or proxy into a place score.

The comparison leaves out people who work for themselves and other work outside the OEWS scope. It does not add taxes, take-home pay, benefits, stock, bonus pay, hours, travel, remote work, or a household budget. Current listings are separate and can be empty even when the government rows are complete.

Use this page for a bounded choice. Compare the same May 2025 BLS role and metric across two exact areas. Add the separate 2024 BEA price view. Inspect dated employer-title matches. Then build a résumé from facts you have confirmed. Keep each source tied to the question it can answer.

Evidence: bls-oews-may-2025 · bea-rpp-2024 · meritlog-public-job-boundary-v1 · Rule: no-place-choice · no-personal-pay-claim · source-purpose-separation

Computer Network Architects: Utah vs Washington

Same occupation, same annual wage metric

The winner can change when local prices differ

Housing and all-items indexes explain the adjustment

Equivalent nominal pay, using price levels only

Employment scale and local concentration

Compare another occupation or pair

Computer Network Architects: Utah and Washington guide

Computer Network Architects in Utah and Washington: common questions

Compare Computer Network Architects listings by place

Utah

We could not load these listings.

Washington

Exact location filter unavailable.

Current jobs

Tailor for a real Computer Network Architects job, not a generic wage number.

Computer Network Architects pay in Utah and Washington

Compare the full Computer Network Architects wage ladder

Mean and median tell two parts of the Computer Network Architects story

How the two Computer Network Architects job bases differ

Where Computer Network Architects takes a larger share of jobs

How price levels differ between Utah and Washington

Compare the medians in national-price dollars

What equal price-level pay would look like in the other place

Check the survey marks before you use the gap

A short check list for Utah and Washington

What this Computer Network Architects comparison does not decide

Compare Computer Network Architects listings by place

Utah

We could not load these listings.

Washington

Exact location filter unavailable.

Privacy choices

Computer Network Architects: Utah vs Washington

Same occupation, same annual wage metric

The winner can change when local prices differ

Housing and all-items indexes explain the adjustment

Equivalent nominal pay, using price levels only

Employment scale and local concentration

Compare another occupation or pair

Computer Network Architects: Utah and Washington guide

Computer Network Architects in Utah and Washington: common questions

Compare Computer Network Architects listings by place

Utah

We could not load these listings.

Washington

Exact location filter unavailable.

Current jobs

Tailor for a real Computer Network Architects job, not a generic wage number.

Computer Network Architects pay in Utah and Washington

Compare the full Computer Network Architects wage ladder

Mean and median tell two parts of the Computer Network Architects story

How the two Computer Network Architects job bases differ

Where Computer Network Architects takes a larger share of jobs

How price levels differ between Utah and Washington

Compare the medians in national-price dollars

What equal price-level pay would look like in the other place

Check the survey marks before you use the gap

A short check list for Utah and Washington

What this Computer Network Architects comparison does not decide

Compare Computer Network Architects listings by place

Utah

We could not load these listings.

Washington

Exact location filter unavailable.