Computer and Information Systems Managers in Washington
May 2025 wages · tax year 2026
You keep
$155,828
after federal, FICA and Washington tax
Tax takes
$53,542
25.6% of the whole
Worth, in national money
$143,538
Washington costs more than average
On that salary you would be around the 25th percentile for this work in Washington — roughly, since only five points along the band are published.
One filer, standard deduction, no dependants and nothing paid in before tax — the same household the rest of this page uses, so the comparison holds. City and school-district income taxes are not included.
Median here
$209,370
Kept after tax
$155,828
Worth in national money
$143,538
State rank
4
of 51 states
What this pays, and what it is worth
- Pay for this job is strong here. Washington's middle earner gets $209,370, putting the state 4 of 51 — about 19.54% ahead of the national figure.
- Within Washington this is well-paid work. Of 493 occupations with published figures in the state, this job ranks 5 — in the top quarter of everything people do there.
- Costs eat into it here. Of $209,370, tax leaves $155,828 — and because Washington is dearer than average, that stretches only as far as $143,538 would nationally. Averages run higher here, $222,510, since top earners drag the number up.
- For computer and information systems managers, Washington sits in the upper band nationally: a median of $209,370, ranking 4 of 51 and running about 19.54% above the national midpoint. Nominal advantage of this size is usually, though not always, large enough to survive the state's own tax and price levels.
- Ranked against every occupation Washington publishes a median for, computer and information systems managers sits 5 of 493 — the upper quartile of the state's wage distribution. National standing and within-state standing are separate questions, and a job can occupy very different positions on each.
- After tax, $155,828 remains from the Washington median of $209,370 for this occupation. Applying the state's above-average price parity yields $143,538 in national-average terms — the quantity relevant to a relocation decision, and the one absent from essentially every published wage comparison. Mean pay of $222,510 exceeds the median, so the upper tail is doing the work.
Compare this career across states
Choose your filing status and local taxes, compare pay, and keep a shortlist.Compare wage and personal-pay outcomes by state, with selected resident local taxes and saved career choices.
Pay band: Computer and Information Systems Managers
The state median for this job
| Lowest tenth earn under | $130,010 |
|---|---|
| Half earn under | $209,370 |
| Top tenth earn over | $327,300 |
| This salary | $209,370 |
Positions between the published tenth, quarter, half, three-quarter and ninetieth points are estimated by straight line.
The same pay, somewhere else
The state median for this job
| Take-home in Washington | $155,828 |
|---|---|
| Take-home in Texas | $155,828 |
| Once local prices are leveledBEA price parity | +$16,820 |
The raise and the real gain point in opposite directions here.
State income tax and state price levels only. No city income tax, and no housing market.
What you would need there
The state median for this job
| To match take-home only | $209,370 |
|---|---|
| You could take a cut of | −$22,038 |
| Prices in Texas | 97 vs 109 |
State taxes and state price levels only. No city tax, and no housing market.
Sources and assumptions
- Treat $209,370 as a midpoint for Washington, not a promise. The tenth percentile is $130,010 and the ninetieth is $327,300 — a wide band, and where you land in it depends on far more than the state.
- One filer, no dependants, no pension contributions — that is the household behind Washington's $155,828, worked from $209,370. That is on purpose. It lets states be compared with each other, not with each other's family circumstances. Local city taxes are left out. Locally this work ranks 5 of 493.
- The wage data and the price data come from different years. That is how each is published. The price adjustment behind $143,538 uses one figure for the whole of Washington. A city and a rural county there can differ by more than two states do. Out of 493 occupations the state publishes, this one sits at 5.
- The Washington median of $209,370 describes the midpoint of a distribution spanning $130,010 to $327,300. Because that spread is typically larger than the interstate spread, a state median is a weak predictor for any individual worker in this occupation.
- The Washington take-home of $155,828, on $209,370 for work ranking 5 of 493 locally, models the simplest household deliberately: holding it constant is what makes the interstate comparison meaningful. It also means the absolute figure overstates liability for most real filers, and municipal income taxes are outside the model entirely. The occupation ranks 5 of 493 in the state.
- Wage and price series carry different reference periods, each published on its own schedule. The real-terms figure of $143,538, worked from $209,370, deflates by a statewide parity that conceals substantial intra-state variation, concentrated in housing — so it supports comparison between states rather than the pricing of a move to a particular Washington address, on work sitting at 5 of 493 locally.
Questions people ask
Is this the average pay for the job?
No — it is the middle. Half of these workers earn more and half earn less. The average is $222,510, pulled upward by the top of the range, which is why the middle is the fairer number to plan against.
Why is the pay range for this job so wide?
Because one job title covers very different work. The bottom tenth here earn $130,010 and the top tenth $327,300 — experience, employer and specialism separate them, and a single figure hides all three.
Does a bigger number here mean I am better off?
Not on its own. Prices in Washington run above the national level, so the same dollars buy less here. Adjusted for that, this pay is worth $143,538 — the wage did not change, only what it covers.
Is most of this wage taxed away?
No. $155,828 survives, because Washington levies no wage income tax. The federal share does not change with the state you work in.
Can I compare this job across every state?
Yes for this one. Pay is published in all 51 jurisdictions, so a state-to-state comparison here rests on the same survey everywhere rather than on a patchwork.
How does the published median differ from the mean for this occupation?
The median is the midpoint of the distribution; the mean for this occupation in Washington is $222,510. Wage distributions are right-skewed, so the mean exceeds the median wherever a minority earn substantially more. BLS publishes both because substituting one for the other misstates a typical worker's pay.
What drives the percentile dispersion in this occupation?
Dispersion between the tenth percentile ($130,010) and the ninetieth ($327,300) exceeds the family median dispersion. SOC codes aggregate roles differing in seniority, industry and specialisation, and BLS does not disaggregate below the detailed occupation level, so within-title variance is not separable from the published series.
How does the state price level affect real compensation?
Washington's regional price parity sits above the national average, so nominal wages overstate purchasing power. Deflating take-home by the state price level gives $143,538 in national-average terms. ⚠️ RPPs are an all-items index; housing parities vary far more widely than the headline figure.
Why is the take-home ratio comparatively high in this state?
Washington levies no personal income tax on wages, so take-home of $155,828 reflects the federal layer and FICA alone. Federal income tax and FICA are unchanged; states without a wage income tax generally recover revenue through consumption and property bases instead.
Is this occupation's state coverage complete?
State-level estimates are published for all 51 jurisdictions for this occupation, so cross-state comparison is not confounded by suppression. ⚠️ Estimates remain survey-based and carry sampling error; small differences between adjacent states should not be over-read.