IBM completed its $11 billion acquisition of Confluent on 17 March 2026, and reports of substantial job reductions followed within days. The acquisition is a matter of public record. The scale of the cuts is not, and this page separates the two carefully.
What Is Confirmed
IBM acquired all outstanding shares of Confluent at $31 per share in cash, valuing the deal at about $11 billion, and Confluent’s Class A common stock was suspended and delisted from Nasdaq. The stated rationale was combining Confluent’s data streaming platform with IBM’s portfolio so enterprises can deploy generative and agentic AI on real-time data. Confluent’s board and officers were replaced with the acquirer’s designees.
| Date | Event | Scope and what we know |
|---|---|---|
| 17 March 2026 | Acquisition completed | IBM acquires Confluent for $31 per share in cash, about $11 billion. Confirmed by IBM’s own newsroom and an SEC 8-K filing. |
| 17 March 2026 | Delisting | Confluent Class A common stock suspended and delisted from Nasdaq. Board and officers replaced. |
| From 18 March 2026 | Reported reductions | Job cuts reported in the days following completion, with figures around 800 roles circulating. See the caveat below. |
The acquisition is confirmed by IBM’s newsroom and reported by The Globe and Mail.
A note on the layoff figures. Numbers around 800 roles have circulated on aggregator sites and employee forums, but we have not found them confirmed by IBM, by a regulatory filing, or by a major news organisation. They are repeated here as reported rather than established, and anyone relying on the exact figure should verify it independently.
Who Becomes Available After a Streaming Acquisition
Whatever the precise number, acquisitions of this shape reliably free up a particular kind of engineer, and Confluent’s population is unusually specialised. The company is built around Apache Kafka, and more than 6,500 enterprises including around 40% of the Fortune 500 run on its platform, so the engineering and field populations have operated streaming infrastructure at genuine enterprise scale.
That means Kafka internals rather than Kafka usage, stream processing with Flink and ksqlDB, exactly-once delivery semantics and the failure modes around them, schema registry and data contract design, and connector engineering into the systems enterprises actually run. The go-to-market population is equally specialised, because selling streaming infrastructure requires solutions engineers who can hold a technical conversation about consumer lag with a platform team.
Real-time data engineering is one of the persistent shortages in enterprise hiring. Every organisation attempting event-driven architecture or real-time analytics needs people who have run Kafka in anger, and almost nobody trains them from scratch.
What the Market Pays These Engineers
| Role | National median | National 25th to 75th | New York median |
|---|---|---|---|
| Software Developers | $135,980 | $105,210 to $171,980 | $166,830 |
| Data Scientists | $120,230 | $85,660 to $158,880 | $135,980 |
| Database Architects | $139,500 | $109,370 to $169,290 | Not separately published |
Source: U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics, May 2025. These cover whole occupations across all industries rather than streaming specialists, who sit towards the upper end of these ranges.
Common Questions
Did IBM acquire Confluent?
Yes. IBM completed the acquisition on 17 March 2026 at $31 per share in cash, valuing it at about $11 billion, and Confluent was delisted from Nasdaq. This is confirmed by IBM’s own announcement and by a regulatory filing, so it is not in question.
How many people were laid off at Confluent?
We cannot confirm a figure. Numbers around 800 roles have circulated on aggregator sites and employee forums following the acquisition, but we have not found them confirmed by IBM, by a filing, or by a major news organisation. Treat any specific number as unverified until a primary source publishes one.
What kind of engineers come out of a company like Confluent?
Streaming infrastructure specialists, covering Apache Kafka internals rather than just usage, stream processing with Flink and ksqlDB, delivery semantics and failure handling, schema registry and data contract design, and connector engineering. The solutions engineering population is similarly technical, because the product cannot be sold without it.
Hiring From This Pool
nexus IT group runs searches into exactly this kind of displaced talent. If you are building a team that needs these skills, start with our relevant practice area or get in touch and we will tell you honestly whether the pool holds what you need.
