TL;DR — A data engineer builds and runs the pipelines and storage that everyone else's analysis depends on: moving data from source systems into a warehouse, modelling it, and keeping it correct and on time. Analysts query what you build; you build what they query. Our index held 459 live remote data engineer roles on 20 September 2026 — 19.8% stated a salary range and 28.3% named the United States among their hiring regions.
Data engineering is the least visible of the data roles and the one whose job title is most often used loosely. Plenty of postings titled "data engineer" are analyst jobs with extra SQL, and plenty of "analytics engineer" postings are data engineering with a friendlier name. This guide draws the lines, shows what the market looked like in September 2026, and lists the stack that postings actually name.
What a data engineer does
A data engineer designs, builds and maintains the systems that move and store data: ingestion from source systems and APIs, transformation into models other people can query, orchestration so it all runs on a schedule, and the monitoring that catches it when it doesn't. The output is not an insight. The output is a table that is correct, documented and there at 6am.
Put the four adjacent roles side by side and the boundaries get clearer.
| Role | What they own | Typical output |
| Data engineer | Pipelines, storage, orchestration, data quality | Reliable, modelled tables and the systems that produce them |
| Analytics engineer | The transformation layer between raw and reporting | Tested, documented models — usually in dbt |
| Data analyst | Questions asked of existing data | Queries, ad hoc analysis, recommendations |
| BI analyst / BI developer | The reporting layer | Dashboards, semantic models, scheduled reports |
The practical test when you read a posting: if the role is judged on whether a number was right and arrived on time, it is engineering. If it is judged on whether the number changed a decision, it is analysis. Our guide to remote data and analytics jobs covers the analyst side of that line, and remote data analyst jobs lists the live openings there.
Data engineering also borders infrastructure work. Cloud cost, infrastructure-as-code, CI/CD and on-call rotations show up in plenty of data platform roles — which is why the boundary with remote DevOps and SRE jobs is a soft one, especially on small teams.
The market on 20 September 2026
Our index counts live remote postings published on employers' own careers pages and applicant tracking systems, not aggregator reposts.
| Measure (20 September 2026) | Remote data engineer roles | All remote roles |
| Live openings | 459 | 37,811 |
| State a salary range | 19.8% | 15.6% |
| Name the US among their hiring regions | 28.3% | 8,128 postings do |
| Employers posting them include | Coinbase, DoiT International | — |
Data engineering is a specialist market: 459 live openings against 37,811 remote roles overall means it is a narrow, deep pool rather than a broad one. Two of the numbers are in your favour. Pay disclosure runs above the market average, at 19.8% against 15.6% — not generous, but better odds than most functions of knowing the range before you invest in an application. And at 28.3%, US concentration is only modestly above the market, so roughly seven in ten postings are not US-restricted.
One structural fact worth naming: across the whole index, roles labelled senior (11,039) outnumber junior ones (2,018) by more than five to one. Remote hiring skews experienced everywhere, and data engineering — where a mistake silently corrupts a company's reporting — skews further. Breaking in usually means moving sideways from analytics or backend work rather than applying cold to a first remote job.
The stack postings actually ask for
A 2026 analysis of 6,877 data engineering job postings, which we checked in September 2026, found the requirements clustered into a small, stable core with a second tier of warehouse and orchestration tools.
| Skill | Share of postings |
| Building data pipelines | 74% |
| SQL | 71% |
| Python | 71% |
| Snowflake | 31% |
| Databricks | 29% |
| Apache Airflow | 29% |
| dbt | 24% |
Read that as two lists. The first three are table stakes — a posting that does not ask for SQL and Python is either not a data engineering role or has renamed them. The second four are the consolidated modern stack: one cloud warehouse or lakehouse, one orchestrator, one transformation framework. Because they now appear in a quarter to a third of postings each, they have stopped being differentiators and started being expectations.
What the list leaves out is as useful as what it contains. Streaming tools such as Kafka appear far less often than the core, so a Kafka gap will not close most doors. Cloud platform experience is usually named as whichever one the employer runs, and is more transferable between clouds than postings imply. And "data modelling" — dimensional design, slowly changing dimensions, knowing why a table is shaped the way it is — is the skill most often tested in interviews and least often listed in the requirements.
How to read a data engineer posting
Three archetypes hide under the same title, and they want different people.
- The warehouse team. A big company with a platform already built. You work inside an established stack — SQL, dbt, a warehouse, an orchestrator — and the job is modelling, quality and scale. Best for analysts moving into engineering.
- The platform team. Infrastructure-first: streaming, Spark, Kubernetes, cost management, sometimes on-call. Closer to backend or SRE work than to analytics, and the postings read that way.
- The one-person data team. A startup where you are ingestion, warehouse, transformation, dashboards and the analyst. Enormous scope and enormous learning; ask hard questions about the state of what you are inheriting.
The tell is in the responsibilities section, not the title. Count how many lines are about building systems versus answering questions — and check who you report to, because a data engineer reporting to a head of analytics does a very different job from one reporting to a VP of engineering.
Pay, ranges and what to ask
Just under a fifth of remote data engineer postings state a range, so four times out of five you are negotiating without an anchor. When a range is published, read it properly — what a salary range in a job posting means covers how location bands, levels and the difference between base and total compensation get folded into a single line.
Three questions that separate good data engineering roles from difficult ones, whatever the number:
- Who is on call, and for what? Pipelines break at night. Find out whether that is your pager, a rotation, or nobody's problem until morning.
- What does the team do about data quality? Tests, contracts, monitoring and alerting — or a Slack message from an analyst who noticed a number looked wrong.
- How much of the job is migration? Plenty of 2026 data engineering roles are a multi-year move from a legacy warehouse. That can be excellent experience or two years of nothing but backfills, and the interview is where you find out which.
Where to look
Data engineering roles are posted in the same places as other engineering work, and the boards covered in our guide to job boards for remote software engineers all carry them. The narrower the specialism, the more it pays to watch company careers pages directly: a company hires one data engineer a year and may never put that role on a board.
Our remote data engineer jobs page lists the live openings from employers' own careers pages, with the hiring regions each employer states.
RemoteHunt is an all-in-one AI job-search platform for remote workers — it builds your resume, finds and scores jobs against it, writes tailored applications, and answers your career questions along the way. Every job gets a 0–100 score against your resume with a written explanation of the score, and the free plan needs no credit card.
Most remote postings that show pay are open to US candidates. Our list of best remote job boards in the US compares the boards that show salary, with our own count of how many live remote postings can hire in the United States.
FAQ
What is the difference between a data engineer and a data analyst?
A data engineer builds and maintains the pipelines, storage and models that data flows through; a data analyst queries that data to answer business questions and build dashboards. Engineers are judged on whether the data is correct, complete and on time. Analysts are judged on whether their analysis changed a decision. The engineer builds the table; the analyst asks it a question.
Is an analytics engineer the same as a data engineer?
Not quite. Analytics engineering is the transformation layer between raw data and reporting — usually dbt models, tests and documentation — and it sits between the two other roles. A data engineer's scope is wider: ingestion, orchestration, storage and infrastructure as well as transformation. Many small teams combine both in one job whatever the title says.
What skills do remote data engineer jobs ask for in 2026?
SQL, Python and pipeline-building are close to universal — a 2026 analysis of 6,877 data engineering postings, which we checked in September 2026, found each in roughly 71–74% of them. The next tier is the consolidated modern stack: Snowflake (31%), Databricks (29%), Apache Airflow (29%) and dbt (24%). Data modelling is heavily tested in interviews even when it is not in the requirements.
How many remote data engineer jobs are there?
Our index held 459 live remote data engineer postings from employers' own careers pages on 20 September 2026, out of 37,811 remote roles in total. It is a specialist market rather than a high-volume one, so a focused search across company careers pages tends to beat scrolling a general board.
Are remote data engineer jobs US-only?
Mostly not. On 20 September 2026, 28.3% of the live remote data engineer postings in our index named the United States among the places they can hire, which is only a little above the market as a whole. That leaves the majority open to other regions — though, as everywhere in remote hiring, about half of all postings say nothing about location at all, so it is worth asking before you apply.
See which remote data engineering roles fit your resume. Try it free.