Data Engineer Jobs in 2026: Where to Look, Salary Ranges, How to Prepare

Data engineer jobs in 2026 are concentrated in the United States, France, the United Kingdom and Germany, and the hiring mix is heavily senior. The figures below come from the SharpSkill job board on 29 October 2026 and from dated public salary trackers. They show where data engineering roles are posted, what the postings ask for, what they pay in each market and what the interview loop tests.

Where data engineer jobs are posted in 2026

Four countries carry most of the volume. On the SharpSkill job board on 29 October 2026, the United States accounts for 1,040 active data engineering postings, France for 494, the United Kingdom for 333 and Germany for 271. London, Paris and Berlin are the three cities with the most postings, ahead of Seattle, Munich and San Francisco.

Each market has its own hiring channels, and the same role often appears in several of them with different levels of detail.

Career sites hold the most reliable version of an offer. A posting relayed by an aggregator or an agency is often a shortened copy. The original page names the warehouse, the orchestrator and the cloud provider, which is what decides whether an application is worth sending.

France has a large consultancy and freelance channel. On the board, 39% of French data engineering postings are freelance missions, against 10% across all countries. IT consultancies (ESN) place data engineers on long missions at large accounts, and a significant share of permanent offers in France are consultancy positions rather than direct hires at the end client.

US postings are more transparent on pay. 48% of US data engineering postings on the board publish a salary, driven by pay transparency laws in states such as California, Colorado, New York and Washington. In the UK the share drops to 14%, and in Germany to 8%.

What data engineer job postings ask for

Data engineering postings use many titles for overlapping work. On the SharpSkill job board on 29 October 2026, the most frequent tags after the generic "data engineer" are data platform engineer, ETL developer, analytics engineer and data architect. A search limited to "data engineer" misses a large part of the relevant roles, especially platform and analytics engineering positions.

Python and SQL are the baseline. They are the two most frequent explicit languages in the postings. In France, where skill extraction is most detailed, Python appears in 111 of the 494 postings and SQL in 79. SQL questions in interviews go well beyond SELECT: window functions, incremental loads, deduplication and query plans come up regularly.

One cloud and one warehouse are expected in depth. French postings name Google Cloud Platform (43), Apache Spark (34), Databricks (34), BigQuery (34) and Terraform (29) most often. The pattern is consistent across markets: a posting rarely asks for AWS, Azure and GCP together, it asks for real production experience on the one already in place, plus infrastructure as code to manage it.

Orchestration and transformation tools come next. Airflow and dbt are the common pair for batch pipelines, with Kafka or a managed pub/sub service for streaming. Data quality and observability (tests, freshness checks, lineage) are now listed as responsibilities, not as extras.

Seniority skews high. Across all countries, 1,980 postings are senior, 666 mid-level, 368 lead and 171 staff, against 120 junior postings and 68 internships. In France, 248 postings are senior and 5 are junior. Data engineering is often a second role, reached after a few years as a backend developer, a data analyst or a database administrator.

Data engineer salary ranges in 2026

Salary figures on the board are converted to euros to compare markets. The global median mixes countries with very different pay levels, so the country figures are more useful for a negotiation.

The German and UK samples are small, so their quartiles move quickly from one week to the next. The French median includes a share of senior and lead consultancy positions, which pulls it above what a mid-level permanent role at a regional employer typically offers.

US figures match a public benchmark. According to Levels.fyi, the median total compensation for data engineers in the United States is $157,500, based on 1,175 self-reported salaries, as of 28 October 2026. That figure includes stock and bonus, while job postings mostly publish base salary, which explains why it sits above the base ranges posted on the board.

UK figures have a dated tracker. ITJobsWatch reports a median permanent salary of £70,000 for data engineer roles over the six months to 29 October 2026, unchanged from the same period in 2025, with a 10th percentile at £45,000 and a 90th at £100,000 across 2,224 permanent ads. The board median is higher because postings that publish a salary in the UK are skewed toward senior and London roles.

Day rates for contract work. Among the 117 postings on the board that publish a day rate, almost all in France, the median is €465 per day, with a middle half between €430 and €540. For UK contracts, ITJobsWatch contract data gives a median of £500 per day over the six months to 29 October 2026, across 1,861 contract ads.

Remote, hybrid and onsite data engineer jobs

On the SharpSkill job board on 29 October 2026, 49% of data engineering postings are fully remote, 21% hybrid and 4% onsite, with the rest unspecified. The global remote share hides very different national patterns.

France is mostly hybrid. Only 7% of French data engineering postings are fully remote, and 60% are hybrid. Paris concentrates 175 of the 494 French postings, ahead of Lille, Lyon and Toulouse. A typical French role asks for two or three days per week on site, more during onboarding.

Remote rarely means anywhere. Most remote data engineering roles require residence in a given country, or at least overlap with a time zone, for payroll, tax and data protection reasons. A US remote posting usually means remote within the United States. European remote roles often list the countries where the employer has a legal entity.

Data access drives onsite rules. Data engineers handle production databases, customer data and credentials to the warehouse. Banks, insurers and health organisations restrict access to managed devices and internal networks, which keeps those roles hybrid even when the rest of the market goes remote.

How to prepare for a data engineer interview in 2026

A data engineering loop usually has four parts: a SQL exercise, a Python or coding round, a pipeline or system design discussion, and a behavioural round about incidents and ownership. Senior and staff roles add a data modelling or architecture round.

SQL rounds test correctness on messy data. The classic exercise gives an events table with duplicates and late arrivals, then asks for daily active users, a sessionisation or the latest state per entity. These problems rely on ROW_NUMBER, LAG and partitioned aggregates, covered in the advanced SQL for data engineers module. The trap is idempotency: a query that works once but double-counts when the pipeline reruns on the same day is a red flag for an interviewer.

Pipeline design questions are about failure modes. "Design a pipeline that ingests orders from an API every hour into the warehouse" is not a question about tool names. Interviewers expect backfills, retries, schema changes, late data and alerting to be addressed. The Airflow fundamentals module covers scheduling, catchup, task retries and sensors, which come up in almost every orchestration discussion.

Data modelling separates a senior profile. Questions on star schemas, slowly changing dimensions, partitioning and clustering decide the level. A strong answer explains the trade-off: why a type 2 dimension is needed for a revenue report by historical region, and what it costs in storage and query complexity. The data modelling module focuses on these points.

Cloud certifications help with screening, not with the loop. The Google Cloud Professional Data Engineer certification appears in some GCP-heavy French and UK postings. Its exam covers designing processing systems, ingestion, storage, preparing data for analysis and maintaining workloads, which mirrors the topics of a design round. Recruiters use it as a filter, interviewers still ask for production examples.

Behavioural questions focus on incidents. "A dashboard showed wrong revenue numbers this morning, walk through what you do" is a standard opener. A good answer checks freshness and the last pipeline run first, communicates impact to consumers, fixes and backfills, then adds a test so the same failure is caught next time.

The full set of data engineering interview questions on SharpSkill, the top 25 data engineering interview questions in 2026 and the cheatsheet cover the remaining fundamentals.

Landing a data engineer job: the checklist

• Check the data engineer job market page and the France page to see current volumes, salary quartiles and the cities with the most postings.
• Search under several titles: data engineer, data platform engineer, analytics engineer and ETL developer cover overlapping roles.
• Position a salary expectation against the country median, not the global one: €93,740 in France, €141,916 in the US and £70,000 in the UK according to ITJobsWatch.
• Ask in the first call which warehouse, orchestrator and cloud provider are in production, and which pipeline the role will own.
• For remote roles, confirm the country and time zone requirements before the technical rounds.
• Review window functions, idempotent loads and slowly changing dimensions: they make up most SQL and modelling questions.
• Prepare two incident stories with the root cause, the fix, the backfill and the test added afterwards.