Computer science occupations have historically maintained some of the lowest unemployment rates of any professional field in the United States. Understanding what that data means — how it's measured, what drives it up or down, and how it compares to broader labor market trends — gives useful context whether you're a job seeker, a recently laid-off tech worker, or someone trying to understand your options.
The Bureau of Labor Statistics (BLS) tracks unemployment by occupation through the Current Population Survey (CPS), a monthly household survey. Within that data, computer and information technology occupations are grouped into a broad category that includes software developers, systems analysts, network architects, database administrators, and related roles.
The unemployment rate for any occupation is calculated as the number of people in that field who are unemployed and actively seeking work, divided by the total labor force in that field (employed + unemployed). It does not include people who have left the labor force entirely.
This distinction matters: if laid-off tech workers stop actively job searching, they drop out of the unemployment rate calculation — which can make the rate look lower than the underlying employment picture suggests.
Computer science unemployment has typically run well below the national average. In strong labor markets, the rate for computer and IT occupations has often sat between 1% and 3%, compared to national rates of 3.5%–5% during the same periods.
| Period | Approx. National Unemployment | Approx. CS/IT Unemployment |
|---|---|---|
| Pre-pandemic (2018–2019) | 3.5%–3.9% | 1.5%–2.5% |
| COVID-19 peak (April 2020) | ~14.7% | ~5%–7% |
| Post-pandemic recovery (2021–2022) | 4%–5.5% | 1.5%–2.5% |
| 2023 tech layoff cycle | 3.4%–3.7% | 2.5%–4%+ |
These figures are approximations based on BLS occupational employment data and vary depending on exactly which roles are included in the count. The 2023 tech sector layoffs — driven largely by contractions at large technology companies following pandemic-era over-hiring — pushed the rate noticeably higher, though it remained below the national average for most of that period.
Several structural factors keep CS unemployment rates compressed:
Low headline unemployment numbers for computer science can obscure real conditions on the ground:
A low occupational unemployment rate has no direct effect on whether an individual computer science worker qualifies for unemployment insurance if they're laid off. UI eligibility is determined by state-specific rules — not by field-wide employment statistics.
What matters for an individual claim is:
A computer science professional laid off in Washington state will file under different rules, at a different benefit level, and with different work search requirements than someone laid off in Texas or Florida doing the same type of work.
Even within a low-unemployment occupation, individual workers face circumstances that shape their UI eligibility and benefit amounts:
The computer science unemployment rate tells a useful story about labor market conditions for a broad occupational group. It doesn't predict anything about how a specific worker's claim will be evaluated, what they'll receive, or how long benefits will last — because those answers live in state law, individual work history, and the specific facts of each separation.