Big Data: market
Data as of November 19, 2026: 508 open Big Data jobs, 31% remote among jobs that state a work format; median advertised salary $6,825/mo (from 61 postings that state a salary). Source: Zorky, updated daily.
Big Data Engineer — processing very large data volumes (terabytes, petabytes) via distributed engines. A Data Engineering sub-segment with focus on Spark/Hadoop/Flink/distributed computing. A premium niche thanks to distributed-systems complexity. Role family: Spark Engineer (PySpark or Spark Scala — Big Data's main application), Hadoop Engineer (legacy enterprise — HDFS + Hive + MapReduce, migrations to Spark), Flink Engineer (true streaming, low-latency event processing), Big Data Platform Engineer (Hadoop cluster admin, Spark on k8s + Iceberg/Delta), Data Lakehouse Architect (modern architecture — Iceberg/Delta + Spark + dbt). Stack: Apache Spark (must — PySpark or Scala, execution model, shuffles, broadcasts), Hadoop (HDFS + Hive + YARN — legacy in large enterprise), Apache Flink (streaming, premium niche), Kafka (must), Delta Lake/Apache Iceberg (lakehouse table formats — modern standard), Apache Hudi (lakehouse alternative), HBase/Cassandra (NoSQL distributed for real-time), Scala or Python (Scala for performance-critical Spark, Python for most), Airflow (orchestration), Cloudera/Hortonworks (distributions, migrations to the open-source stack), Kubernetes (Spark on k8s — modern deployment). Top stack: python, spark, cloud, java, hadoop. Among jobs with a stated work format, 31% are remote.
Data as of:
Key numbers for the Big Data market: open jobs, median salary, observed talent pool and remote share.
The Big Data market currently has 508 open roles, 442 of them freshly observed. Median salary $6,825/mo.
Among jobs with a stated work format, 31% are remote. Cluster admin work — cloud-based. International cloud-data SaaS (Databricks/Snowflake/Confluent) — full-remote.
⚠ salary known for 61 of 508 jobs; remote share from 354 with a stated format; 442 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many Big Data postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.
New postings per week
Chart data
| Period | New postings per week |
|---|---|
| 2026-06-01 | 48 |
| 2026-06-08 | 26 |
| 2026-06-15 | 25 |
| 2026-06-22 | 86 |
| 2026-06-29 | 83 |
| 2026-07-06 | 69 |
| 2026-07-13 | 128 |
| 2026-07-20 | 135 |
| 2026-07-27 | 67 |
| 2026-08-03 | 56 |
| 2026-08-10 | 28 |
| 2026-08-17 | 29 |
| 2026-08-24 | 25 |
| 2026-08-31 | 56 |
| 2026-09-07 | 37 |
| 2026-09-14 | 39 |
| 2026-09-21 | 81 |
| 2026-09-28 | 91 |
| 2026-10-05 | 98 |
| 2026-10-12 | 342 |
| 2026-10-19 | 133 |
| 2026-10-26 | 117 |
| 2026-11-02 | 106 |
| 2026-11-09 | 134 |
Active sources per week
Sources over the period: 131. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 13 |
| 2026-06-08 | 12 |
| 2026-06-15 | 11 |
| 2026-06-22 | 24 |
| 2026-06-29 | 27 |
| 2026-07-06 | 35 |
| 2026-07-13 | 28 |
| 2026-07-20 | 33 |
| 2026-07-27 | 24 |
| 2026-08-03 | 30 |
| 2026-08-10 | 18 |
| 2026-08-17 | 19 |
| 2026-08-24 | 14 |
| 2026-08-31 | 22 |
| 2026-09-07 | 19 |
| 2026-09-14 | 17 |
| 2026-09-21 | 27 |
| 2026-09-28 | 34 |
| 2026-10-05 | 27 |
| 2026-10-12 | 36 |
| 2026-10-19 | 35 |
| 2026-10-26 | 32 |
| 2026-11-02 | 34 |
| 2026-11-09 | 48 |
New sources connected: Jun 22 +14 · Jun 29 +13 · Jul 6 +18 · Jul 13 +8 · all weeks (23) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +6 | 26 |
| Jun 15 | +3 | 25 |
| Jun 22 | +14 | 86 |
| Jun 29 | +13 | 83 |
| Jul 6 | +18 | 69 |
| Jul 13 | +8 | 128 |
| Jul 20 | +5 | 135 |
| Jul 27 | +6 | 67 |
| Aug 3 | +6 | 56 |
| Aug 10 | +1 | 28 |
| Aug 17 | +2 | 29 |
| Aug 24 | +1 | 25 |
| Aug 31 | +4 | 56 |
| Sep 7 | +1 | 37 |
| Sep 14 | +1 | 39 |
| Sep 21 | +3 | 81 |
| Sep 28 | +3 | 91 |
| Oct 5 | +1 | 98 |
| Oct 12 | +6 | 342 |
| Oct 19 | +5 | 133 |
| Oct 26 | +2 | 117 |
| Nov 2 | +2 | 106 |
| Nov 9 | +7 | 134 |
The current week is not over yet and is not shown: an incomplete week would look like a drop.
Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.
Chart data
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 48 | 13 |
| 2026-06-08 | 26 | 12 |
| 2026-06-15 | 25 | 11 |
| 2026-06-22 | 86 | 24 |
| 2026-06-29 | 83 | 27 |
| 2026-07-06 | 69 | 35 |
| 2026-07-13 | 128 | 28 |
| 2026-07-20 | 135 | 33 |
| 2026-07-27 | 67 | 24 |
| 2026-08-03 | 56 | 30 |
| 2026-08-10 | 28 | 18 |
| 2026-08-17 | 29 | 19 |
| 2026-08-24 | 25 | 14 |
| 2026-08-31 | 56 | 22 |
| 2026-09-07 | 37 | 19 |
| 2026-09-14 | 39 | 17 |
| 2026-09-21 | 81 | 27 |
| 2026-09-28 | 91 | 34 |
| 2026-10-05 | 98 | 27 |
| 2026-10-12 | 342 | 36 |
| 2026-10-19 | 133 | 35 |
| 2026-10-26 | 117 | 32 |
| 2026-11-02 | 106 | 34 |
| 2026-11-09 | 134 | 48 |
Salaries over time
Median Big Data salary per week, USD per month.
Median salary, USD per month
Chart data
| Period | Median | Postings with a salary per week (n) |
|---|---|---|
| 2026-07-20 | 5,750 | 12 |
| 2026-07-27 | — | 4 |
| 2026-08-03 | — | 0 |
| 2026-08-10 | — | 0 |
| 2026-08-17 | — | 0 |
| 2026-08-24 | — | 0 |
| 2026-08-31 | — | 0 |
| 2026-09-07 | — | 0 |
| 2026-09-14 | — | 1 |
| 2026-09-21 | — | 4 |
| 2026-09-28 | — | 3 |
| 2026-10-05 | 5,079 | 10 |
| 2026-10-12 | 6,793 | 20 |
| 2026-10-19 | 6,250 | 36 |
| 2026-10-26 | 6,726 | 21 |
| 2026-11-02 | 7,699 | 22 |
| 2026-11-09 | 4,658 | 22 |
The series starts on Jul 20: there is no data before that.
Only postings with a USD salary and a known period (month or year), $500–$50,000 per month. Weeks with fewer than 10 such postings are left blank — that means no data, not zero.
Chart data
| Week | Median |
|---|---|
| 2026-06-01 | — |
| 2026-06-08 | — |
| 2026-06-15 | — |
| 2026-06-22 | — |
| 2026-06-29 | — |
| 2026-07-06 | — |
| 2026-07-13 | — |
| 2026-07-20 | 5,750 |
| 2026-07-27 | — |
| 2026-08-03 | — |
| 2026-08-10 | — |
| 2026-08-17 | — |
| 2026-08-24 | — |
| 2026-08-31 | — |
| 2026-09-07 | — |
| 2026-09-14 | — |
| 2026-09-21 | — |
| 2026-09-28 | — |
| 2026-10-05 | 5,079 |
| 2026-10-12 | 6,793 |
| 2026-10-19 | 6,250 |
| 2026-10-26 | 6,726 |
| 2026-11-02 | 7,699 |
| 2026-11-09 | 4,658 |
Remote work over time
Share of Big Data postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-06-01 | 79.1 |
| 2026-06-08 | 31.6 |
| 2026-06-15 | 11.8 |
| 2026-06-22 | 31.5 |
| 2026-06-29 | 23.9 |
| 2026-07-06 | 32.4 |
| 2026-07-13 | 44 |
| 2026-07-20 | 75.6 |
| 2026-07-27 | 68 |
| 2026-08-03 | 20 |
| 2026-08-10 | 25 |
| 2026-08-17 | 28 |
| 2026-08-24 | 20 |
| 2026-08-31 | 20 |
| 2026-09-07 | 17.1 |
| 2026-09-14 | 23.7 |
| 2026-09-21 | 37.5 |
| 2026-09-28 | 36.9 |
| 2026-10-05 | 43.6 |
| 2026-10-12 | 36.8 |
| 2026-10-19 | 31.9 |
| 2026-10-26 | 25.9 |
| 2026-11-02 | 25.3 |
| 2026-11-09 | 24.6 |
The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.
Chart data
| Week | Remote |
|---|---|
| 2026-06-01 | 79.1 |
| 2026-06-08 | 31.6 |
| 2026-06-15 | 11.8 |
| 2026-06-22 | 31.5 |
| 2026-06-29 | 23.9 |
| 2026-07-06 | 32.4 |
| 2026-07-13 | 44 |
| 2026-07-20 | 75.6 |
| 2026-07-27 | 68 |
| 2026-08-03 | 20 |
| 2026-08-10 | 25 |
| 2026-08-17 | 28 |
| 2026-08-24 | 20 |
| 2026-08-31 | 20 |
| 2026-09-07 | 17.1 |
| 2026-09-14 | 23.7 |
| 2026-09-21 | 37.5 |
| 2026-09-28 | 36.9 |
| 2026-10-05 | 43.6 |
| 2026-10-12 | 36.8 |
| 2026-10-19 | 31.9 |
| 2026-10-26 | 25.9 |
| 2026-11-02 | 25.3 |
| 2026-11-09 | 24.6 |
Technologies over time
How the share of Big Data postings mentioning each of the top technologies changed.
Postings mentioning the technology, %
Chart data
| Period | Python | cloud | SQL |
|---|---|---|---|
| 2026-08-10 | 34.8 | 4.3 | 13 |
| 2026-08-17 | 44.4 | 7.4 | 22.2 |
| 2026-08-24 | — | — | — |
| 2026-08-31 | 49 | 15.7 | 35.3 |
| 2026-09-07 | 48.3 | 13.8 | 41.4 |
| 2026-09-14 | 28.6 | 25.7 | 20 |
| 2026-09-21 | 36.4 | 30.3 | 37.9 |
| 2026-09-28 | 43.2 | 42 | 37 |
| 2026-10-05 | 57.8 | 47.8 | 51.1 |
| 2026-10-12 | 33 | 32.6 | 27.7 |
| 2026-10-19 | 61.4 | 41.2 | 47.4 |
| 2026-10-26 | 59.4 | 44.8 | 50 |
| 2026-11-02 | 50 | 28.4 | 34.1 |
| 2026-11-09 | 54.5 | 24.2 | 37.4 |
Share among postings with a tagged stack; the series starts on Aug 10: earlier stack tags were assigned differently. Weeks with fewer than 20 tagged postings are left blank.
Chart data
| Week | Python | Java | cloud | hadoop | SQL |
|---|---|---|---|---|---|
| 2026-08-10 | 34.8 | 17.4 | 4.3 | 39.1 | 13 |
| 2026-08-17 | 44.4 | 11.1 | 7.4 | 3.7 | 22.2 |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | 49 | 13.7 | 15.7 | 15.7 | 35.3 |
| 2026-09-07 | 48.3 | 20.7 | 13.8 | 17.2 | 41.4 |
| 2026-09-14 | 28.6 | 25.7 | 25.7 | 17.1 | 20 |
| 2026-09-21 | 36.4 | 24.2 | 30.3 | 27.3 | 37.9 |
| 2026-09-28 | 43.2 | 22.2 | 42 | 21 | 37 |
| 2026-10-05 | 57.8 | 35.6 | 47.8 | 23.3 | 51.1 |
| 2026-10-12 | 33 | 39 | 32.6 | 54.3 | 27.7 |
| 2026-10-19 | 61.4 | 34.2 | 41.2 | 36 | 47.4 |
| 2026-10-26 | 59.4 | 31.2 | 44.8 | 15.6 | 50 |
| 2026-11-02 | 50 | 33 | 28.4 | 13.6 | 34.1 |
| 2026-11-09 | 54.5 | 36.4 | 24.2 | 26.3 | 37.4 |
Countries over time
How the share of Big Data postings in each of the top countries changed, per week.
Postings in the country, %
Chart data
| Period | Poland | USA | India |
|---|---|---|---|
| 2026-06-01 | 62.2 | 20 | 0 |
| 2026-06-08 | 16 | 20 | 24 |
| 2026-06-15 | 14.3 | 33.3 | 19 |
| 2026-06-22 | 57.5 | 8.8 | 15 |
| 2026-06-29 | 12.5 | 20 | 15 |
| 2026-07-06 | 14.3 | 32.7 | 12.2 |
| 2026-07-13 | 22.3 | 28.7 | 20.2 |
| 2026-07-20 | 53.2 | 7.3 | 10.5 |
| 2026-07-27 | 51.6 | 12.9 | 6.5 |
| 2026-08-03 | 13.7 | 19.6 | 21.6 |
| 2026-08-10 | 17.4 | 17.4 | 30.4 |
| 2026-08-17 | 3.8 | 26.9 | 19.2 |
| 2026-08-24 | 0 | 20 | 15 |
| 2026-08-31 | 1.9 | 13.2 | 18.9 |
| 2026-09-07 | 11.1 | 11.1 | 16.7 |
| 2026-09-14 | 6.2 | 21.9 | 18.8 |
| 2026-09-21 | 22.1 | 32.4 | 14.7 |
| 2026-09-28 | 11.9 | 26.2 | 11.9 |
| 2026-10-05 | 46.4 | 9.5 | 3.6 |
| 2026-10-12 | 14.5 | 33.6 | 9.3 |
| 2026-10-19 | 32 | 20.3 | 6.2 |
| 2026-10-26 | 26.3 | 15.8 | 15.8 |
| 2026-11-02 | 14.7 | 21.1 | 10.5 |
| 2026-11-09 | 19.8 | 10.7 | 5 |
Share among postings with a known country; the chart shows the five countries with the most postings over six months. Weeks with fewer than 20 postings with a known country are left blank. A rising share can mean a newly connected source in that country rather than market growth.
Chart data
| Week | Poland | USA | India | Singapore | South Africa |
|---|---|---|---|---|---|
| 2026-06-01 | 62.2 | 20 | 0 | 0 | 0 |
| 2026-06-08 | 16 | 20 | 24 | 0 | 12 |
| 2026-06-15 | 14.3 | 33.3 | 19 | 0 | 9.5 |
| 2026-06-22 | 57.5 | 8.8 | 15 | 0 | 0 |
| 2026-06-29 | 12.5 | 20 | 15 | 38.8 | 1.2 |
| 2026-07-06 | 14.3 | 32.7 | 12.2 | 10.2 | 0 |
| 2026-07-13 | 22.3 | 28.7 | 20.2 | 2.1 | 0 |
| 2026-07-20 | 53.2 | 7.3 | 10.5 | 12.1 | 0.8 |
| 2026-07-27 | 51.6 | 12.9 | 6.5 | 16.1 | 1.6 |
| 2026-08-03 | 13.7 | 19.6 | 21.6 | 3.9 | 5.9 |
| 2026-08-10 | 17.4 | 17.4 | 30.4 | 0 | 0 |
| 2026-08-17 | 3.8 | 26.9 | 19.2 | 3.8 | 0 |
| 2026-08-24 | 0 | 20 | 15 | 10 | 0 |
| 2026-08-31 | 1.9 | 13.2 | 18.9 | 1.9 | 15.1 |
| 2026-09-07 | 11.1 | 11.1 | 16.7 | 0 | 13.9 |
| 2026-09-14 | 6.2 | 21.9 | 18.8 | 3.1 | 12.5 |
| 2026-09-21 | 22.1 | 32.4 | 14.7 | 5.9 | 0 |
| 2026-09-28 | 11.9 | 26.2 | 11.9 | 16.7 | 4.8 |
| 2026-10-05 | 46.4 | 9.5 | 3.6 | 4.8 | 8.3 |
| 2026-10-12 | 14.5 | 33.6 | 9.3 | 1.9 | 12.6 |
| 2026-10-19 | 32 | 20.3 | 6.2 | 7 | 7 |
| 2026-10-26 | 26.3 | 15.8 | 15.8 | 6.1 | 4.4 |
| 2026-11-02 | 14.7 | 21.1 | 10.5 | 12.6 | 7.4 |
| 2026-11-09 | 19.8 | 10.7 | 5 | 5.8 | 18.2 |
Clean market: hiring index
The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just Big Data.
Hiring index, Oct 16 = 100
Chart data
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.
Chart data
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open Big Data jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 508 |
| Open demand | 508 |
| Observed supply | — not published |
Big Data forms a premium distributed-systems segment. Drivers: legacy Hadoop → Spark on k8s + Iceberg migrations, demand for streaming (Flink + Kafka), growth of Databricks partners. Trend 2026: lakehouse architecture (Iceberg/Delta) dominates, Hadoop EOL in large enterprise.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in Big Data jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 0 |
| $1–2k | 4 |
| $2–3k | 2 |
| $3–4k | 2 |
| $4–5k | 5 |
| $5–6k | 7 |
| $6–7k | 12 |
| $7–8k | 8 |
| $8–9k | 5 |
| $9–10k | 4 |
| $10–12k | 3 |
| $12–15k | 3 |
| $15–20k | 5 |
| $20k+ | 1 |
- usable for the calculation: 61 (12%)
- stated but not converted to USD/month: 63 (12.4%)
- not stated: 384 (75.6%)
One in ten postings offers under $3,289, one in ten over $14,641. Half of the postings offer between $5,375 and $9,250. Sample: 61.
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 0 |
| $1–2k | 1,000 | 2,000 | 4 |
| $2–3k | 2,000 | 3,000 | 2 |
| $3–4k | 3,000 | 4,000 | 2 |
| $4–5k | 4,000 | 5,000 | 5 |
| $5–6k | 5,000 | 6,000 | 7 |
| $6–7k | 6,000 | 7,000 | 12 |
| $7–8k | 7,000 | 8,000 | 8 |
| $8–9k | 8,000 | 9,000 | 5 |
| $9–10k | 9,000 | 10,000 | 4 |
| $10–12k | 10,000 | 12,000 | 3 |
| $12–15k | 12,000 | 15,000 | 3 |
| $15–20k | 15,000 | 20,000 | 5 |
| $20k+ | 20,000 | — | 1 |
Which countries have the most open Big Data jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| Poland | 113 | 27.2% |
| United States | 86 | 20.7% |
| India | 43 | 10.3% |
| Singapore | 28 | 6.7% |
| Canada | 17 | 4.1% |
| United Kingdom | 15 | 3.6% |
| Russia | 13 | 3.1% |
| France | 11 | 2.6% |
| Spain | 10 | 2.4% |
| Germany | 9 | 2.2% |
| Other countries | 71 | 17.1% |
The leader by Big Data job count is Poland (113 positions). Moscow dominates. Poland — Big Data-friendly EU market. Large international remote via Databricks/Snowflake.
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| PL | 113 |
| US | 86 |
| IN | 43 |
| SG | 28 |
| CA | 17 |
| GB | 15 |
| RU | 13 |
| FR | 11 |
| ES | 10 |
| DE | 9 |
Which technologies are most often required in the same job as Big Data.
Used together with
Share — how many of the 508 jobs in the Big Data market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).
Top Big Data stack 2026: Apache Spark (must — PySpark or Scala), Hadoop (HDFS + Hive — legacy enterprise), Apache Flink (premium streaming), Kafka (must), Delta Lake / Apache Iceberg (lakehouse — modern standard), Apache Hudi, HBase / Cassandra (NoSQL distributed), Scala or Python, Airflow, Cloudera / Hortonworks, Kubernetes (Spark on k8s). Senior — Apache Atlas / DataHub.
Common pairs: Spark + Kafka, Spark + Iceberg, Hadoop + Hive, Spark + Scala, Flink + Kafka. Learning roadmap: Data Engineer Middle experience → Spark deeply → Spark execution model → one lakehouse (Iceberg) → Hadoop basics (for legacy) → Spark on k8s.
Chart data
| Name | Count |
|---|---|
| python | 217 |
| spark | 215 |
| java | 163 |
| cloud | 157 |
| hadoop | 151 |
| sql | 142 |
| aws | 118 |
| pyspark | 105 |
| databricks | 92 |
| azure | 77 |
| scala | 74 |
| kafka | 70 |
How many Big Data jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 141 |
| lead | 48 |
| middle | 47 |
| principal | 20 |
| junior | 6 |
Juniors are almost non-existent — the market expects Data Engineer Middle experience. Career flow: Data Engineer Middle → Big Data Middle in 4-8 months → Senior → Platform Engineer / Lakehouse Architect / Head of Big Data.
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| senior | 141 |
| lead | 48 |
| middle | 47 |
| principal | 20 |
| junior | 6 |
Who hires the most for Big Data and how concentrated demand is among the largest companies.
Employers
Demand is spread across 293 employers. The largest accounts for 7.9%, the top ten for 20.5%; the remaining 79.5% is long tail.
| share | value |
|---|---|
| top-1 | 7.9% |
| top-3 | 11.8% |
| top-10 | 20.5% |
| long tail | 79.5% |
⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier
Which company sites and job boards Zorky collects Big Data jobs from.
Where Zorky sees this market
Observed across 64 sources; the largest accounts for 18.9% — this market does not rest on a single channel.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 257 | 0.5059 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 240 | 0.4724 |
| telegram | Telegram | Telegram | 11 | 0.0217 |
The newest Big Data jobs from company career sites.
Recent openings
- Senior Java Microservices & Spark Developer · SG
- Senior Java Spark Developer - Assistant Vice President · IN
- Senior Data Engineer (Snowflake, AWS, Big Data) · AU
- Senior/Lead Data Engineer (Java/Flink/Kafka) · UA
- Эксперт по администрированию Hadoop в Мегафон · RU
- Senior Python Developer (PySpark, Databricks, React)
- Senior Python Developer (PySpark, Azure)
- Senior Data Engineer (Spark & Python Specialist) · ZA · $4,158
Latest open Big Data jobs — the most recent 10 positions with adequate description quality. The full list is in our CRM or via the "see all" link below.
Adjacent markets
Big Data Engineer — niche premium segment of the Data direction. Comparison with other data specialisations — in the SiblingSubnichesChart above.
⚠ adjacent markets for comparison are not defined yet
How this is measured
- Vacancy
- an open job that cleared the quality gate and lists at least two technologies
- Observed candidate
- a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
- Matchable candidate
- not counted yet
- Window
- jobs open at the moment the snapshot was built
About the data
- Some breakdowns are hidden: their data coverage is not yet sufficient.
- Statistics are shown only where the sample clears a quality gate.
- A missing block does not mean a value of zero.
Breakdowns currently hidden: 8.
Direction: Data Engineering
Related specializations
Inside Big Data Engineer: Spark Engineer (PySpark or Spark Scala — main application), Hadoop Engineer (legacy enterprise — HDFS + Hive + MapReduce), Flink Engineer (true streaming, premium niche), Big Data Platform Engineer (Hadoop cluster admin, Spark on k8s + Iceberg/Delta), Data Lakehouse Architect (modern architecture). Comparison with other data specialisations — in the bar below.
Frequently asked questions
The most common questions about Big Data: pay, Spark vs Hadoop vs Flink, Lakehouse (Delta/Iceberg/Hudi), difference from Data Engineer / ML Engineer, remote, how to start (4-8 months after Data Engineer Middle), Senior skills. Answers recompute automatically.
What does a Big Data Junior, Middle, Senior, or Lead earn?
Junior Big Data openings are ALMOST NON-EXISTENT — the market expects Data Engineer Middle experience + hands-on Spark. The Junior → Middle jump — Spark execution model + one of Hadoop/Flink/Kafka deeply. Senior owns Big Data platform architecture + mentor. Lead Big Data — managing distributed systems with 5+ engineers, accountable for cluster sizing + cost optimisation. Career flow: Data Engineer Middle/Senior → Big Data Middle in 4-8 months → Senior → either Platform Engineer (infra-focus) or Lakehouse Architect (modern data stack).
What stack does Big Data most often need?
Top 5: python, spark, cloud, java, hadoop. Apache Spark — must (PySpark for most, Spark Scala for performance-critical). Deep understanding of the execution model (DAG, stages, tasks), shuffles, broadcasts, partitioning. Hadoop — HDFS + Hive + YARN — legacy enterprise (Sber/banks/telco), migrations to the open-source stack. Apache Flink — true streaming, premium niche. Kafka — must (partitions, consumer groups, exactly-once). Delta Lake/Apache Iceberg — lakehouse table formats (modern standard, replacing the classic Hadoop stack). Apache Hudi — alternative to Iceberg. HBase/Cassandra — NoSQL distributed for real-time. Scala or Python — Scala for production Spark, Python for most. Airflow for batch-job orchestration. Cloudera/Hortonworks distributions (legacy enterprise). Kubernetes — Spark on k8s + Spark Operator. Apache Atlas/DataHub — data lineage + catalog (Senior must). Knowledge of JVM tuning (GC G1/ZGC, heap profiling) — Spark Scala Senior must.
Spark vs Hadoop vs Flink — what to pick for Big Data?
Apache Spark — industrial standard + dominator. PySpark — the largest market, Spark Scala — premium niche. Downsides: micro-batch streaming (seconds latency), not true realtime. Hadoop (HDFS + MapReduce + Hive) — legacy enterprise. Used at large banks/telco where migration to open-source isn't finished. Must know if you work at Sber/banks. Trend: migrations from Hadoop to Spark on k8s + Iceberg/Delta Lake. Apache Flink — true streaming engine with millisecond latency, exactly-once semantics out of the box. Growing segment: FinTech/AdTech/IoT/real-time ML inference. Strategy: Spark first (market size), then Flink for diversification and premium pay. Learn Hadoop only if you're going into banking.
Lakehouse (Delta Lake / Iceberg / Hudi) — what to learn in 2026?
Lakehouse architecture — modern data architecture that combines Data Lake (cheap storage in S3/HDFS) with Data Warehouse (ACID + schema enforcement + indexing). Replaces the classic Hadoop stack. Three main table formats: Delta Lake (Databricks-original, most mature, dominator in Databricks shops), Apache Iceberg, Apache Hudi (third place, fastest updates via incremental ingestion). Strategy: Iceberg first (open-standard winner 2024–2026), Delta Lake if you work with Databricks, Hudi only for a specific use-case (CDC + updates-heavy).
What share of jobs are remote?
Among jobs with a stated work format, 31% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How is Big Data Engineer different from Data Engineer / ML Engineer?
Big Data Engineer (this page) — focus on distributed systems for processing terabytes+. Spark/Hadoop/Flink + cluster management. Premium for distributed-systems complexity. Data Engineer (general) — can work with smaller volumes (GB-TB) without Spark. Focus on pipelines + DWH modelling. ML Engineer — deploy models to production (FastAPI + ONNX/TorchServe), feature store, MLOps. Focus on inference. ML Engineer Senior ≈ Big Data Senior. Career switch Data Engineer → Big Data in 4-8 months (Spark + one lakehouse + Kafka). Big Data → ML Engineer in 8-12 months (PyTorch + MLOps stack). Many Senior Big Data engineers move into ML Engineering (data infrastructure → model deployment).
Where to start in Big Data in 2026?
Data Engineer Middle experience assumed (Python + SQL + Airflow + one DWH). Roadmap: 1) Apache Spark deeply — official documentation + Databricks Learning Academy (free). Master DataFrame API + Spark SQL + Window Functions + Structured Streaming. 2) Spark execution model — physical/logical plans, DAG, stages, tasks, shuffles, broadcasts, partitioning strategies. 3) PySpark — for most projects. Alternative: Spark Scala for performance-critical. 4) Kafka — partitions, consumer groups, exactly-once semantics. 5) One lakehouse format: Iceberg (recommended — open-standard winner) or Delta Lake (if Databricks). 6) Hadoop basics — HDFS + Hive (for maintenance of legacy banking projects). 7) Spark on Kubernetes (Spark Operator). 8) End-to-end pet project: Spark + Kafka + Iceberg + Airflow pipeline on a 10-50 GB dataset, deployed in the cloud. Courses: Karpov.Courses "Spark Developer", OTUS "Big Data Engineer", Yandex.Practicum (part of the Data Engineer track), Databricks Learning Academy (EN — best free resource), Coursera "Big Data" specialisation. Books: "Spark: The Definitive Guide" Chambers/Zaharia, "Designing Data-Intensive Applications" Kleppmann (must-read). Data Engineer Middle → Big Data Middle — 4-8 months.
How many open jobs are in this sample?
The published sample contains 508 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.
What skills does a Senior Big Data Engineer need?
A Senior Big Data Engineer owns the full distributed-systems cycle. Spark mastery: execution model (logical plan → physical plan → tasks), shuffle optimisation (avoid shuffles where possible, broadcast joins for small tables, repartition vs coalesce, skew handling), Catalyst optimizer internals, Tungsten memory model, Spark SQL deep, Structured Streaming with exactly-once. Performance: JVM tuning for Spark Scala (G1/ZGC, heap sizing — executor.memory + driver.memory + memoryOverhead), pandas UDFs vs Pandas API on Spark, Photon engine (Databricks-only). Kafka: producer-consumer semantics deep, partitioning strategies, exactly-once via transactions, schema registry (Avro/Protobuf), Kafka Streams basics. Lakehouse: Iceberg/Delta — schema evolution, time-travel, partition evolution, optimize/vacuum, hidden partitioning. Cluster admin: Spark on k8s (Spark Operator), cost optimisation (spot instances, auto-scaling), Cloudera/Hortonworks for legacy. SQL: advanced SQL for Spark SQL + Hive SQL + one DWH (Snowflake/BigQuery). Data Governance: Apache Atlas or DataHub — lineage, catalog, access control. DevOps: Docker, Kubernetes, Terraform for IaC, CI/CD for Spark applications (Spark Submit + GitHub Actions). Soft: code review, mentoring, communication with Data Scientists / Analytics teams on requirements. English — must for Senior+ (Big Data documentation is predominantly EN, few Russian-speaking sources).
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.