Kafka: market
Apache Kafka is the event-streaming standard: the bus between microservices, a source for real-time analytics and the backbone of event-driven architectures. We track 5 611 open positions listing Kafka, 5 373 of them fresh. Backend needs Kafka for asynchronous service interaction, data engineers — for streaming pipelines (Kafka Streams, Flink, Spark Streaming), infrastructure — for operating clusters. Most of the demand comes from Backend, Data and DevOps roles. It most often appears next to Java, Kubernetes and AWS. 36% of the postings allow fully remote work. Below is a live slice of Kafka demand.
The Kafka market currently has 5,611 open roles, 5,373 of them freshly observed. Median salary $7,250/mo. Observed candidate pool — 1,416.
36% of Kafka postings allow fully remote work; the share counts only postings that state the work format.
⚠ salary known for 367 of 5611 jobs; remote share from 4836 with a stated format; 5373 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many Kafka postings appeared each week since 10 Aug, and from how many sources. The second line 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 and active sources per week
Sources over the period: 255
New sources connected: 17 Aug +28 · 24 Aug +25 · 31 Aug +24 · 7 Sept +15 · 14 Sept +20 · 21 Sept +31 · 28 Sept +9 · 5 Oct +10 · 12 Oct +22
Week = posting first-seen date, all statuses. A posting belongs to the technology by its stack tag; the series starts on 10 Aug 2026 — earlier tags were assigned differently and are not comparable. Sources are distinct collection channels; their names are not published.
Salaries over time
Median Kafka salary per week, USD per month.
Median salary, USD per month
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.
Remote work over time
Share of Kafka postings offering fully remote work, per week.
Remote postings, %
The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.
Countries over time
How the share of Kafka postings in each of the top countries changed, per week.
Postings in the country, %
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.
Demand and observed supply
| Open demand | 5,611 |
| Observed supply | 1,416 |
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
Salary distribution
One in ten earns under $3,695, one in ten over $16,708. Half the market falls between $5,593 and $13,030. Sample: 367.
The range histogram for Kafka postings uses only postings with an explicit compensation range; the median is computed over the same sample.
Demand geography
| country | jobs |
|---|---|
| PL | 1,311 |
| US | 926 |
| RU | 578 |
| IN | 325 |
| GB | 217 |
| DE | 172 |
| CA | 126 |
| SG | 85 |
| KZ | 78 |
| ES | 75 |
The top country for Kafka demand is Poland (1 311 positions).
⚠ job counts only: salary by country is not published
Used together with
Kafka most often appears next to Java, Kubernetes and AWS. The Java and Kubernetes pairing reflects the typical setting: JVM services in containers.
Roles that use it
| role | jobs |
|---|---|
| Backend | 1,656 |
| Data | 862 |
| DevOps | 838 |
| Fullstack | 758 |
| Architect | 362 |
| Platform Engineer | 162 |
| ML/AI | 138 |
| QA | 133 |
| SRE | 85 |
| Analyst | 80 |
⚠ the `Other` and `IT` buckets are excluded as non-roles
Demand by grade
| grade | jobs |
|---|---|
| senior | 2,349 |
| middle | 550 |
| principal | 389 |
| lead | 269 |
| junior | 158 |
Senior-and-above is about 81% of 3 715 graded Kafka postings.
⚠ demand side only: the grade of the observed pool is unknown for most of it
Employers
Demand is spread across 2,058 employers. The largest accounts for 3.7%, the top ten for 12.1%; the remaining 87.9% is long tail.
| share | value |
|---|---|
| top-1 | 3.7% |
| top-3 | 7.2% |
| top-10 | 12.1% |
| long tail | 87.9% |
⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier
Where Zorky sees this market
Observed across 195 sources; the largest accounts for 21.1% — this market does not rest on a single channel.
Kafka postings arrive mostly from ATS & career sites and job boards & aggregators.
Recent openings
- Python Developer - IT Contracting · PL
- Principal Engineer, Data Analytics Engineering [ 8+ years ] (Java/Python | Kafka | Kubernetes) · IN
- Senior Software Engineer (.NET + React)
- DevOps (Senior) инженер · RU
- Technical Lead — Identity & Data Intelligence
- Analityk Systemowy · PL
- Java Developer · PL
- [Banking/Boletos] Software Engineering Manager I · PL
Adjacent markets
⚠ 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: 7.
Data as of 2026-10-23
Frequently asked questions
Common questions about the Kafka market — short answers from the same data slice.
Is Kafka a backend skill or a data-engineering skill?
Both, with different focus: backend cares about producers and consumers, delivery semantics, idempotency and message schemas; data engineers — stream processing and connectors; DevOps — partitioning, replication and cluster monitoring.
What do Kafka interviews ask about?
Partitions and message ordering, consumer groups and rebalancing, at-least-once versus exactly-once, retention and compaction, Schema Registry, error handling and retries.
How does Kafka differ from RabbitMQ in requirements?
Kafka is an event log with storage and replay, built for high throughput and analytics; RabbitMQ is a classic queue broker with flexible routing. Many postings name both, but Kafka leads in high-load systems.
How big is Kafka demand?
The slice tracks 5 611 open positions listing Kafka. Dedicated 'Kafka engineers' are few — the skill is part of backend, data and platform profiles and noticeably lifts a candidate in the shortlist.