We use technical cookies and Zorky's de-identified visit log. Yandex Metrica (data is stored on servers in Russia) runs only with your consent. We never sell data. More about cookies and statistics.
Zorky is in test mode — everything is free. Jobs and company pages are open to everyone; links to postings and your personal feed open after you sign up. Sign up →

Streaming: market

Data as of November 19, 2026: 36 open Streaming jobs, 31% remote among jobs that state a work format; median advertised salary $9,583/mo (from 6 postings that state a salary). Source: Zorky, updated daily.

Streaming (Kafka) — a stream-processing engineer: builds platforms and data pipelines that work in real time. Unlike classic batch processing (data computed hourly / daily), stream processing works with a continuous flow of events as they arrive — it is the foundation of event-driven architecture, real-time analytics, fraud detection, recommendations, IoT data processing. This is a specialisation within Data Engineering — see also /research/data/data-engineer and /research/data/big-data. Role family: Streaming / Real-time Data Engineer (general — streaming pipelines), Kafka Engineer / Kafka Platform Engineer (operating and evolving the Kafka platform), Stream Processing Engineer (stream processing on Flink / Spark), Data Platform Engineer with a streaming bias. Stack 2026: Apache Kafka (the dominant event-streaming platform — de-facto standard), Apache Pulsar, AWS Kinesis, Redpanda (Kafka-compatible, modern — growing), NATS, RabbitMQ (for contrast — a message broker, not a streaming platform). Stream processing: Apache Flink (leader for complex stateful processing), Kafka Streams, Spark Structured Streaming, ksqlDB. Change Data Capture (CDC): Debezium (capture changes from a DB into a stream). Adjacent: Schema Registry (Avro / Protobuf — message contracts), ClickHouse (analytics on streaming data — popular in CIS), Kafka Connect (source/sink integration), the Confluent ecosystem. Key concepts: partitioning and consumer groups, offsets, exactly-once semantics, backpressure, event sourcing, time windowing, watermarks. Languages: predominantly JVM — Java and Scala (most stream-processing engines on JVM), Python (PyFlink, clients). Infrastructure: Docker / Kubernetes, monitoring (Prometheus + Grafana), CI/CD. Top stack: cloud, kafka, python, flink, grafana. Among jobs with a stated work format, 31% are remote. Streaming — a narrow but one of the highest-paying branches of Data Engineering: real-time processing has become the standard for large products, and specialists are scarce.

Data as of:

Key numbers for the Streaming market: open jobs, median salary, observed talent pool and remote share.

36
open jobs — by job title, reposts merged
$9,583
median $/mo
31%
remote

The Streaming market currently has 36 open roles, 31 of them freshly observed. Median salary $9,583/mo.

Among jobs with a stated work format, 31% are remote. Stream processing is engineering work with code and distributed systems, perfectly remote-friendly.

⚠ salary known for 6 of 36 jobs; remote share from 29 with a stated format; 31 counted as fresh observations; trend and hiring difficulty are not shown

Timeline: postings and sources

How many Streaming 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
New postings per week. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodNew postings per week
2026-06-016
2026-06-086
2026-06-156
2026-06-226
2026-06-294
2026-07-065
2026-07-133
2026-07-2010
2026-07-273
2026-08-031
2026-08-101
2026-08-176
2026-08-244
2026-08-311
2026-09-070
2026-09-144
2026-09-214
2026-09-282
2026-10-0516
2026-10-1219
2026-10-1911
2026-10-264
2026-11-027
2026-11-0910

Active sources per week

Sources over the period: 45. ▲ — a week with a large batch of new sources.

Chart data
Active sources per week. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodActive sources
2026-06-013
2026-06-082
2026-06-151
2026-06-224
2026-06-294
2026-07-065
2026-07-133
2026-07-2010
2026-07-272
2026-08-031
2026-08-101
2026-08-175
2026-08-244
2026-08-311
2026-09-070
2026-09-143
2026-09-214
2026-09-282
2026-10-058
2026-10-127
2026-10-196
2026-10-264
2026-11-026
2026-11-098
New sources connected: Jul 20 +8 · all weeks (16) in the table
WeekNew sourcesNew postings
Jun 22+36
Jun 29+34
Jul 6+45
Jul 13+13
Jul 20+810
Aug 17+46
Aug 24+34
Aug 31+11
Sep 14+14
Sep 21+24
Sep 28+12
Oct 5+116
Oct 12+319
Oct 19+311
Nov 2+27
Nov 9+210

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
Timeline: postings and sources — Streaming. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekNew postings per weekActive sources
2026-06-0163
2026-06-0862
2026-06-1561
2026-06-2264
2026-06-2944
2026-07-0655
2026-07-1333
2026-07-201010
2026-07-2732
2026-08-0311
2026-08-1011
2026-08-1765
2026-08-2444
2026-08-3111
2026-09-0700
2026-09-1443
2026-09-2144
2026-09-2822
2026-10-05168
2026-10-12197
2026-10-19116
2026-10-2644
2026-11-0276
2026-11-09108

Remote work over time

Share of Streaming postings offering fully remote work, per week.

Remote postings, %

Chart data
Remote postings, %. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodRemote
2026-10-0537.5
2026-10-1264.3
2026-10-1927.3
2026-10-26—
2026-11-02—
2026-11-09—

The series starts on Oct 5: there is no data before that.

The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.

Chart data
Remote work over time — Streaming. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekRemote
2026-06-01—
2026-06-08—
2026-06-15—
2026-06-22—
2026-06-29—
2026-07-06—
2026-07-13—
2026-07-20—
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-0537.5
2026-10-1264.3
2026-10-1927.3
2026-10-26—
2026-11-02—
2026-11-09—

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 Streaming.

Hiring index, Oct 16 = 100

Chart data
Hiring index, Oct 16 = 100. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodHiring index
2026-10-16100
2026-10-17100.03
2026-10-1899.76
2026-10-1999.68
2026-10-2099.27
2026-10-2198.6
2026-10-2299.07
2026-10-2397.4
2026-10-2497.41
2026-10-2697.33
2026-10-2796.76
2026-10-2896.21
2026-10-2995.17
2026-10-3095.13
2026-10-3193.65
2026-11-0193.33
2026-11-0292.67
2026-11-0392.65
2026-11-0492.41
2026-11-0592.13
2026-11-0690.44
2026-11-0790.48
2026-11-0890.45
2026-11-1090.29
2026-11-1190.22
2026-11-1390.12
2026-11-1489.7
2026-11-1589.68
2026-11-1689.62
2026-11-1888.91
2026-11-1988.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
Clean market: hiring index — Streaming. Block data table. A missing value is not zero; units and sample are stated in the metric description.
DayHiring index
2026-10-16100
2026-10-17100.03
2026-10-1899.76
2026-10-1999.68
2026-10-2099.27
2026-10-2198.6
2026-10-2299.07
2026-10-2397.4
2026-10-2497.41
2026-10-2697.33
2026-10-2796.76
2026-10-2896.21
2026-10-2995.17
2026-10-3095.13
2026-10-3193.65
2026-11-0193.33
2026-11-0292.67
2026-11-0392.65
2026-11-0492.41
2026-11-0592.13
2026-11-0690.44
2026-11-0790.48
2026-11-0890.45
2026-11-1090.29
2026-11-1190.22
2026-11-1390.12
2026-11-1489.7
2026-11-1589.68
2026-11-1689.62
2026-11-1888.91
2026-11-1988.02

How many open Streaming jobs there are and how many matching specialists Zorky observes.

Demand and observed supply

Chart data
Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricValue
Open demand36
Open demand36
Observed supply— not published

Streaming — a narrow but fast-growing and well-paid branch of Data Engineering. Drivers 2026: real-time processing has become the standard for large products (fraud, recommendations, on-the-fly analytics), event-driven architecture growth, CDC as a way to decouple monolithic DBs. Demand concentrates where data is needed "here and now".

⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown

How salaries in Streaming jobs are distributed, in US dollars per month.

Salary distribution

P25 $8,930 · P50 $9,583 · P75 $14,087
Chart data
Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricValue
<$1k0
$1–2k0
$2–3k0
$3–4k0
$4–5k0
$5–6k1
$6–7k0
$7–8k0
$8–9k1
$9–10k1
$10–12k0
$12–15k2
$15–20k1
$20k+0
Salary in postings: base 36
  • usable for the calculation: 6 (16.7%)
  • stated but not converted to USD/month: 7 (19.4%)
  • not stated: 23 (63.9%)

One in ten postings offers under $5,512, one in ten over $17,754. Half of the postings offer between $8,930 and $14,087. Sample: 6.

⚠ percentiles from 6 salaries out of 36 jobs — a guide on a small sample

Chart data
Salary distribution — Streaming. Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricLower boundUpper boundCount
<$1k01,0000
$1–2k1,0002,0000
$2–3k2,0003,0000
$3–4k3,0004,0000
$4–5k4,0005,0000
$5–6k5,0006,0001
$6–7k6,0007,0000
$7–8k7,0008,0000
$8–9k8,0009,0001
$9–10k9,00010,0001
$10–12k10,00012,0000
$12–15k12,00015,0002
$15–20k15,00020,0001
$20k+20,000—0

Which countries have the most open Streaming jobs.

Demand geography

countryjobsshare
Poland1236.4%
United States824.2%
Canada39.1%
Pakistan39.1%
India26.1%
Germany13%
Sweden13%
Israel13%
United Kingdom13%
Saudi Arabia13%

The leader by Streaming job count is Poland (12 positions). Demand concentrates in fintech (fraud), e-commerce (recommendations, analytics), telco, ad platforms, gaming. International companies hire Russian-speaking Senior Streaming engineers on full-remote.

⚠ job counts only: salary by country is not published

Chart data
Demand geography — Streaming. Block data table. A missing value is not zero; units and sample are stated in the metric description.
CountryJobs
PL12
US8
CA3
PK3
IN2
DE1
SE1
IL1
GB1
SA1

Which technologies are most often required in the same job as Streaming.

Used together with

kafka
2775%
aws
1336.1%
java
1233.3%
cloud
1130.6%
python
1027.8%
spring
822.2%
ansible
719.4%
grafana
719.4%
eks
513.9%
flink
513.9%

Share — how many of the 36 jobs in the Streaming 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 Streaming stack 2026: Apache Kafka (dominator), Apache Pulsar / AWS Kinesis / Redpanda; processing — Apache Flink (leader of stateful processing), Kafka Streams, Spark Structured Streaming, ksqlDB; CDC — Debezium; Kafka ecosystem — Kafka Connect, Schema Registry (Avro / Protobuf); ClickHouse (streaming-data sink); languages — Java / Scala (JVM), Python; Docker / Kubernetes, Prometheus + Grafana.

Common pairs: Kafka + Flink, Kafka + ClickHouse, Kafka + Debezium (CDC), Kafka + Schema Registry, Flink + exactly-once. Learning roadmap: distributed systems and delivery guarantees → Java / Scala → Kafka thoroughly → Kafka ecosystem (Connect, Schema Registry) → stream processing (Kafka Streams → Flink) → CDC (Debezium) → event-driven concepts → Kubernetes and monitoring → end-to-end pet project (source → Kafka → Flink → ClickHouse → Grafana).

Chart data
Used together with — Streaming. Block data table. A missing value is not zero; units and sample are stated in the metric description.
NameCount
kafka27
aws13
java12
cloud11
python10
spring8
ansible7
grafana7
eks5
flink5
ec24
kubernetes4

How many Streaming jobs there are at each level, from junior to principal.

Demand by grade

gradejobs
senior14
principal3
middle3
junior2
lead1

Pure Juniors are almost non-existent — people come from Data Engineering, backend (JVM) or big data. Career flow: Data Engineer / backend → Streaming Middle → Senior → Streaming / Kafka Platform Lead / Data Platform Engineer / data architect.

⚠ demand side only: the grade of the observed pool is unknown for most of it

Chart data
Demand by grade — Streaming. Block data table. A missing value is not zero; units and sample are stated in the metric description.
LevelCount
senior14
principal3
middle3
junior2
lead1

Who hires the most for Streaming and how concentrated demand is among the largest companies.

Employers

Demand is spread across 30 employers. The largest accounts for 8.6%, the top ten for 42.9%; the remaining 57.1% is long tail.

largest 8.6%2nd–3rd 11.4%4th–10th 22.9%the rest 57.1%
sharevalue
top-18.6%
top-320.0%
top-1042.9%
long tail57.1%

⚠ 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 Streaming jobs from.

Where Zorky sees this market

Observed across 17 sources; the largest accounts for 13.9% — this market does not rest on a single channel.

Streaming jobs: hh.ru ("data engineer" / "Kafka" / "streaming engineer" / "stream processing engineer"), Habr Career, getmatch, LinkedIn (international segment), Telegram (data engineering and Kafka communities). The real market is broader than the exact search — Kafka work often falls inside Data Engineer and Data Platform Engineer openings.

Chart data
Where Zorky sees this market — Streaming. Block data table. A missing value is not zero; units and sample are stated in the metric description.
ClassNameEnglish nameCountShare
boardджоб-борды и агрегаторыjob boards & aggregators190.5278
atsATS и карьерные сайтыATS & career sites160.4444
telegramTelegramTelegram10.0278

The newest Streaming jobs from company career sites.

Recent openings

All jobs →

Latest open Streaming / Kafka jobs — the most recent 10 positions with adequate description quality. The full list is in our CRM or via the "see all" link below.

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 Streaming: Streaming / Real-time Data Engineer (general — streaming pipelines), Kafka Engineer / Kafka Platform Engineer (operating and evolving the Kafka platform), Stream Processing Engineer (stream processing on Flink / Spark), Data Platform Engineer with a streaming bias. Comparison with other data specialisations — in the bar below.

Big DataData EngineerDBAData Warehouse

Frequently asked questions

The most common questions about Streaming: pay, grades, tools (Kafka vs Pulsar vs Kinesis vs Redpanda), stream processing (Flink vs Kafka Streams vs Spark), event-driven architecture / CDC / exactly-once, remote, companies, how to start, Senior skills. Answers recompute automatically.

What does a Streaming engineer Junior, Middle, Senior, or Lead earn?

Pure Junior streaming openings are almost non-existent — it's not a first role; people come from Data Engineering, backend development or big data. The jump to Middle — confident work with Kafka (producers / consumers, partitioning), one stream-processing engine. Senior — designing streaming architectures, exactly-once, stateful processing on Flink, operating Kafka under load. Career flow: Data Engineer / backend → Streaming Middle → Senior → Streaming / Kafka Platform Lead / Data Platform Engineer / data architect.

What tools and skills does a Streaming engineer most often need?

Top 5: cloud, kafka, python, flink, grafana. Streaming platforms: Apache Kafka (dominator — de-facto standard), Apache Pulsar, AWS Kinesis, Redpanda (Kafka-compatible, modern). Stream processing: Apache Flink (leader of complex stateful processing), Kafka Streams (lightweight processing inside Kafka), Spark Structured Streaming, ksqlDB (SQL over streams). Change Data Capture: Debezium (capture DB changes into a stream). Kafka ecosystem: Kafka Connect (source / sink integration), Schema Registry (Avro / Protobuf — message contracts), Confluent stack. Storage for streaming data: ClickHouse (real-time analytics — popular in CIS), sometimes Apache Druid, Pinot. Languages: predominantly JVM — Java and Scala (most engines), Python (PyFlink, clients). Concepts: distributed systems, partitioning and consumer groups, offsets, exactly-once / at-least-once semantics, backpressure, time windowing, watermarks, event sourcing, idempotency. Infrastructure: Docker / Kubernetes, monitoring (Prometheus + Grafana), CI/CD, SQL. Understanding of distributed systems and delivery guarantees is valued more highly than knowing a specific API.

Kafka vs Pulsar vs Kinesis vs Redpanda — what to pick?

Apache Kafka — the de-facto standard for event streaming: huge ecosystem (Connect, Streams, Schema Registry, Confluent), widespread, the most jobs and materials. Learn this first. Downsides — historically dependency on ZooKeeper (replaced by built-in KRaft in new versions), operation requires expertise. Apache Pulsar — architecturally interesting in places (storage/processing separation, built-in multi-tenancy, geo-replication), but ecosystem and adoption smaller than Kafka. AWS Kinesis — managed service in the AWS ecosystem: simpler to operate (no cluster admin), but vendor lock-in and less flexibility; sensible if your whole infrastructure is in AWS. Redpanda — Kafka-compatible platform (same API), written in C++, without JVM and ZooKeeper: simpler to operate, lower latency; modern alternative gaining popularity 2024–2026. Strategy 2026: learn Kafka — that's the market, the ecosystem and a transferable skill; Redpanda knowledge comes as a near-free bonus (same API). Pulsar / Kinesis — by company context. Message brokers like RabbitMQ are something else (reliable message delivery between services), don't confuse with a streaming platform for event streams.

What is stream processing — Flink vs Kafka Streams vs Spark Streaming?

Stream processing — processing data as it arrives, not in batches: filtering, aggregations in time windows, enrichment, joins of streams, pattern detection — in real time. Apache Flink — leader for complex stateful processing: true streaming model (processes event by event), powerful state and time handling (event time, watermarks), exactly-once, low latency; the choice for serious real-time tasks (fraud, complex on-the-fly analytics). Entry bar is higher. Kafka Streams — lightweight processing library right "inside" a Kafka application (not a separate cluster): simpler to operate, good for not-too-complex processing in a Kafka-centric architecture; Java / Scala only. Spark Structured Streaming — stream processing in the Spark ecosystem, works via micro-batch (small batches); convenient if the company already has Spark and wants batch and streaming in one stack, latency slightly higher. ksqlDB — stream processing in SQL, low entry bar for simple tasks. Strategy: Flink — the main skill for serious stream processing 2026; Kafka Streams — know as a simpler tool in the Kafka ecosystem; Spark Streaming — if the company is already on Spark. Choice depends on processing complexity and existing stack.

What are event-driven architecture, CDC and exactly-once?

Event-driven architecture — a style of building systems where components communicate via events (facts "what happened") published to a stream (Kafka), rather than via direct synchronous calls. Services independently subscribe to the events they need. Pros — loose coupling, scalability, natural history of all changes. CDC (Change Data Capture) — a technique to capture changes from a database into an event stream: a tool (Debezium) reads the DB transaction log and publishes every change (insert / update / delete) to Kafka. Why — without loading the DB, get a stream of its changes to populate other systems (search indexes, caches, analytical stores, other services) in real time; a key way to "decouple" a monolithic DB and the event-driven world. Exactly-once semantics — one of the hardest topics in stream processing: a guarantee that every event will be processed exactly once, even under failures and restarts — not lost (at-least-once allows duplicates) and not duplicated. Critical, for example, for financial operations. Achieved through a combination of idempotency, Kafka transactions and checkpoints in the processing engine (Flink). Understanding these three concepts is the core of Streaming engineer expertise; interview questions and real architectural decisions are built around them.

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.

Where to start a Streaming engineer career in 2026?

Streaming — not a first role; people usually come from Data Engineering, backend development (especially JVM) or big data. Roadmap: 1) Base — distributed systems: what a distributed system is, consistency, fault tolerance, delivery guarantees (at-least-once / at-most-once / exactly-once). 2) Language — Java or Scala (most stream engines on JVM); Python as a supplement. 3) Apache Kafka thoroughly — topics, partitions, producers and consumers, consumer groups, offsets, replication, delivery guarantees; deploy locally and experiment. 4) Kafka ecosystem — Kafka Connect (integrations), Schema Registry (Avro / Protobuf and why message contracts are needed), operation basics. 5) Stream processing — start with Kafka Streams (simpler), then Apache Flink (the main skill — stateful processing, windows, event time, watermarks, exactly-once). 6) CDC — Debezium: capturing DB changes into a stream. 7) Concepts — event-driven architecture, event sourcing, idempotency, backpressure. 8) Infrastructure — Docker / Kubernetes, monitoring (Prometheus + Grafana), SQL, ClickHouse as a sink for streaming data. 9) End-to-end pet project: event source → Kafka → Flink processing (window aggregations) → write to ClickHouse → Grafana dashboard; add CDC from PostgreSQL via Debezium. Resources: book "Kafka: The Definitive Guide" (O'Reilly), Apache Kafka and Flink documentation, Confluent Developer (free courses and materials), data engineering and streaming courses (Otus, Karpov.Courses, Data Learn). In a Streaming engineer CV real streaming pipelines and an understanding of delivery guarantees are what's valued.

How many open jobs are in this sample?

The published sample contains 36 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 Streaming engineer need?

A Senior Streaming engineer designs and operates streaming platforms and pipelines under high load. Distributed systems: deep understanding — consistency, fault tolerance, partitioning, delivery guarantees (at-least-once / exactly-once and their cost), CAP trade-offs; this is the foundation without which the rest doesn't work. Apache Kafka at operational level: cluster internals, partitioning and its impact on scaling and ordering, consumer groups and rebalancing, replication, KRaft, performance tuning, monitoring and incident analysis, schema evolution (Schema Registry). Stream processing: expert command of Flink (stateful processing, state management, checkpoints, event time vs processing time, watermarks, windowing, exactly-once), understanding of Kafka Streams and Spark Streaming and when to apply which. Architecture: designing event-driven systems, event sourcing, choosing delivery semantics per task, CDC pipelines (Debezium), idempotency, backpressure handling, designing for failures and reprocessing. Performance and reliability: tuning for throughput and latency, capacity planning, hot-partition handling, consumer-lag monitoring. Languages: confident JVM (Java / Scala), Python. Storage: ClickHouse and other streaming-data sinks, understanding how a stream connects to analytics and services. Infrastructure: Kubernetes, Docker, IaC, CI/CD, observability (Prometheus / Grafana). Data Engineering breadth: how streaming combines with batch (lambda / kappa architectures), data lakehouse. Communication: design decisions, reviews, mentoring, explaining trade-offs (e.g. the cost of exactly-once). English — for documentation and the international market. The main value of a Senior — the ability to design a streaming system with the required guarantees, which holds the load and behaves correctly under failures.

Leave a request

Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.

By submitting, you agree to the privacy policy.