Data Engineer Job Outlook

The data engineer job outlook has a problem before you read a single number: the Bureau of Labor Statistics doesn't track Data Engineers. It tracks the neighbors. In its 2024-34 projections, BLS has data scientists growing 33.5%, information security analysts 28.5%, and software developers 15.8%, against 3.1% for all occupations.^[1] In the newer 2025-35 cycle, the Occupational Outlook Handbook projects database administrators and architects, counted as one combined group, growing 4%.^[3]

Here's the finding in plain terms. The occupations closest to data engineering range from roughly average growth (database work) to some of the fastest growth BLS projects anywhere (data science). None of them is your job title. The numbers also come from 2 different projection cycles with different base years, so they shouldn't share a sentence without a label.

I've gotten more recruiter emails than I can count that opened with some version of "data engineering is growing X% a year!" I've never once seen a source attached. This piece sorts out which numbers exist, which occupation each one belongs to, and what they can and can't tell you about your next search.

What the BLS 2024-34 Projections Show for Data Engineer-Adjacent Roles

The cleanest single source for the 2024-34 cycle is a BLS Economics Daily article from July 16, 2026, on AI, information technology, and employment.^[1] It puts the relevant occupations side by side:

2 housekeeping notes before anyone screenshots that table. First, the Handbook rounds: its data scientist page says 34%, which is the same 33.5% rounded up.^[2] When you need a decimal place, cite the Economics Daily figure. Second, the Handbook's software developer page reports a combined group of software developers, quality assurance analysts, and testers at 15%, so its headline differs slightly from the 15.8% for developers alone.^[7] Same agency, different groupings. Know which one you're quoting.

The last row is the one that trips people up. It comes from a different projection cycle than everything above it, which I'll get to in a minute.

Why BLS Has No Data Engineer Category

BLS projections are built on the Standard Occupational Classification (SOC) system. Data Engineer has no code in it. The closest fit is Database Architects (15-1243), whose official 2018 SOC illustrative titles are Data Architect, Data Integration Specialist, Data Warehousing Specialist, and Database Developer.^[4] If you've built a warehouse or stitched 14 source systems into one model, the federal government thinks you're a "Data Integration Specialist." Congratulations on the title nobody puts on LinkedIn.

The same SOC definition explicitly excludes Database Administrators (15-1242), so those are 2 separate occupations that the Handbook happens to publish together.^[4]

I've had the title "Data Engineer," "BI Developer," "Analytics Engineer," and at one point something with "Solutions" in it that I still can't explain. The work barely changed between them. The title means whatever the hiring company wants it to mean, and BLS doesn't try to keep up with that, which is reasonable. Classification systems move on a timescale of a decade; job titles move on a timescale of whatever the last conference keynote said.

The practical consequence: any growth number someone attaches to "data engineering" is an inference from neighboring codes like Database Architects (15-1243), Software Developers (15-1252), or Data Scientists (15-2051). It might be a reasonable inference. It's still an inference, and whoever's quoting it should say which neighbor they borrowed it from.

BLS Data Scientist Job Outlook: Big Growth, Mostly Replacement Openings

The data scientist numbers are the ones that get waved around most, so they deserve a closer read. BLS projects the occupation to add 82,500 jobs over 2024-34, a 33.5% increase.^[1] The Handbook also projects about 23,400 openings per year over the same decade.^[2]

Those 2 figures measure different things. Openings include new jobs from growth plus replacement demand: people retiring, leaving, or switching occupations. Spread 82,500 net new jobs over 10 years and you get about 8,250 a year (my arithmetic, not a BLS figure). That means most of the 23,400 annual openings are backfills. You'll see some sites report 82,500 as annual openings; that reading is wrong, and it inflates the picture by about 10x.

Pay: the Handbook reports a May 2024 median annual wage of $112,590 for data scientists, with the 10th percentile under $63,650 and the 90th percentile over $194,410.^[2] That spread is enormous. A median that covers everyone from a first-year analyst-turned-scientist to a principal at a big tech company tells you very little about what your specific offer should be.

If you're a Data Engineer wondering whether to rebrand as a data scientist to ride that 33.5%, read the data engineer vs. data scientist comparison first. The interview loops are different, the day job is different, and the growth number belongs to the people doing that day job.

Database Roles in the 2025-35 Outlook: Slower, and Murkier

The Handbook's current page projects database administrators and architects combined to grow 4% over 2025-35, which BLS labels "about as fast as the average," with roughly 144,500 jobs in 2025 and about 7,300 openings a year.^[3] The 2025 headcount splits to about 75,000 administrators and 69,500 architects.^[3]

The 9% vs. 0% split

You'll see a split floating around: 9% growth for database architects and 0% for database administrators over 2025-35. I couldn't trace that pair to a BLS table, and the Handbook page I could see gives only the combined 4%.^[3] For what it's worth, weighting 9% and 0% by those 2025 headcounts gives roughly 4.3%, so the split is arithmetically consistent with the combined figure. Consistent and published are different standards. Until someone points to the detailed 2025-35 table, treat the split as unconfirmed.

My read, labeled as opinion: architects outgrowing administrators would match everything I've seen on the ground. Managed cloud databases ate a lot of the patching, backup scheduling, and failover babysitting that used to fill a DBA's week. Somebody still has to decide what the data model is. That work didn't get automated; it got more important.

Database architect salary

The Handbook lists May 2025 median pay of $139,500 for database architects and $104,620 for database administrators.^[3] One caveat: the $104,620 administrator figure also appears as an earlier-year number in some versions of the page, so check the live page before you quote it in a negotiation. Also watch for aggregator sites that report pay for "Architects, Except Landscape and Naval." That's building architects. Different occupation, different SOC code, zero overlap with your warehouse.

If the architect figure holds, the gap between design work and operations work is about $35,000 at the median. That gap is the most useful number in this section for a Data Engineer, and I'll come back to why. For role-level comp rather than occupation-wide medians, the data engineering salary breakdown is a better starting point.

Reading BLS Projection Cycles Without Mixing Them

BLS has published projections annually since 2019, after years on a 2-year cycle.^[5] Each release is a fresh 10-year model built from a new base year, run through a sequence of steps from labor force through aggregate economy, industry output, industry employment, and finally occupational employment.^[5] A new cycle reflects new data and new assumptions, so 2 cycles aren't 2 points on one line.

The 2025-35 projections were released August 27, 2026, with total employment projected to grow 3.5%.^[6] The 2024-34 cycle projected 3.1% total growth.^[1] So "much faster than average" in one edition is measured against a different average than in the next.

Think of it like any 2 snapshots in your warehouse with different load dates and a schema change in between. You wouldn't union them and call it a time series. Here's how I'd actually store these numbers if I wanted to compare them honestly:

The comparison that respects the cycles joins each occupation to the all-occupations baseline from its own cycle, never across:

Run it and data scientists come out around 10.8x their cycle's average, while combined database roles land around 1.1x theirs. That's my arithmetic on BLS inputs, and it still compares numbers from different editions, so read it as rough positioning rather than a ranking. Grain and lineage matter here for the same reason they matter in your fact tables; if you want practice reasoning about that, the data modeling interview questions drill exactly this kind of thinking.

Key takeaway: Every BLS growth figure needs 3 labels before you repeat it: the occupation (and SOC code), the projection cycle, and whether it's a single occupation or a combined group. A number missing any of those is a vibe.

What BLS Says About AI and Data Engineering Demand

BLS's own framing of AI is more measured than most of what you'll read on LinkedIn. In the 2024-34 Economics Daily piece, BLS says growing AI adoption, including generative AI tools, "will fuel strong job growth" among computer and mathematical occupations.^[1] In its methodology, BLS treats AI like other technologies: its models assume the pace of technological change continues near its historical rate, and the 2023-33 cycle folded in AI effects for occupations with high likely exposure to automation.^[5]

The Handbook's database page is more specific. It says database architects will be critical to database design, transition, backup, and security as organizations adopt AI.^[3]

Now the limit. A projection model built on gradual change can't tell you whether change will stay gradual. If AI tooling moves faster than history suggests, these numbers will lag. If it moves slower than the hype, they'll look smart. Anyone telling you they know which one it'll be is guessing with more confidence than BLS is.

My view, from the cheap seats: I've been through 3 waves of "data engineering is getting automated away." Still here. Still debugging the same categories of problems. Every new layer of AI tooling I've seen adopted at work needed clean, modeled, governed data underneath it, and somebody had to build and fix that. The BLS language about design, transition, backup, and security reads like a job description for the boring, essential half of data engineering.

What This Means for Your Data Engineering Career Outlook in 2026

The evidence supports a few concrete moves.

Cite the occupation and cycle, or don't cite. If you mention market demand in an interview, say "BLS projects data scientists at 33.5% over 2024-34" rather than "data engineering is growing 34%." The first is checkable. The second is a misattribution an informed interviewer will catch, and then they'll wonder what else you're rounding up.

Describe your work in the vocabulary the classification systems use. The official examples under Database Architects are data integration, data warehousing, and data architecture.^[4] Those map directly to what most DEs do. Put that language on your resume next to actual outcomes; the data engineer resume guide covers how to turn "built pipelines" into evidence a hiring manager cares about.

Position toward design, away from pure operations. If the Handbook's architect median of $139,500 versus $104,620 for administrators holds up, design work is where the money sits.^[3] In practice that means data modeling, pipeline architecture, and owning data quality end to end. Those concepts transfer across every tool you'll touch; the tools themselves will change twice before the next projection cycle lands.

Ask recruiters for their source. When someone tells you the market is booming or collapsing, ask which series they mean. Usually you'll get a blank stare, which tells you how much weight to put on the claim.

Ignore growth rates when negotiating; use role-level comp. An occupation-wide median spanning $63,650 to $194,410 at the 10th and 90th percentiles can't price your offer.^[2] Level, company, and location do that.

None of these projections will get you through a loop, though. What gets you hired is the same thing it's always been: you can model the data, write the SQL under pressure, and explain why your pipeline broke and how you fixed it. I've watched people with 10 years of experience get downleveled because they couldn't articulate a design decision live. If that's the gap, a mock interview is better practice than reading another salary report.

What to watch next: the detailed 2025-35 occupational tables, which should settle whether the architect and administrator split is real, and the 2026-36 cycle next year. When that drops, line it up against its own baseline, label the cycle, and resist the urge to draw a trend line through 3 different models. BLS will keep not having a Data Engineer category. You'll keep doing the job anyway.

References

1. U.S. Bureau of Labor Statistics, The Economics Daily, "Artificial intelligence, information technology, and employment, 2024-34," July 16, 2026. bls.gov
2. U.S. Bureau of Labor Statistics, "Occupational Outlook Handbook: Data Scientists." bls.gov
3. U.S. Bureau of Labor Statistics, "Occupational Outlook Handbook: Database Administrators and Architects." bls.gov
4. U.S. Bureau of Labor Statistics, "2018 SOC Definitions." bls.gov
5. Christine Machovec, Michael J. Rieley, and Emily Rolen, Monthly Labor Review, "Incorporating AI impacts in BLS employment projections: occupational case studies," February 2025; and U.S. Bureau of Labor Statistics, Handbook of Methods, "Employment Projections: History." bls.gov, bls.gov
6. U.S. Bureau of Labor Statistics, Employment Projections news release, 2025-35 (USDL-26-1422), August 27, 2026. bls.gov
7. U.S. Bureau of Labor Statistics, "Occupational Outlook Handbook: Software Developers, Quality Assurance Analysts, and Testers." bls.gov