Data Engineering at Confluent

Confluent went through meaningful workforce reductions in 2023 as it shifted focus from growth-at-all-costs to sustainable margins, a transition common across enterprise infrastructure companies of its vintage. The low 30-day layoff risk suggests that immediate acute risk is low, and the trending up happiness trend is a real signal. Hiring tells its own story: no open data engineering roles at the time this was written, which points to a company in a consolidation mode rather than an expansion one. For someone joining now, the next 12 months are more likely to involve deepening into existing systems than standing up net-new platforms. That can be a good environment for engineers who want to build expertise rather than breadth, but it means internal mobility and team growth may be slower than at a company actively scaling headcount.

Confluent's core product is managed Apache Kafka, which means the company's internal data problems are inseparable from the problem it sells solutions to: high-throughput, low-latency event streaming at scale. Data engineers here work on the infrastructure that powers a platform processing trillions of events per day across thousands of enterprise customers. The work spans pipeline reliability for Confluent Cloud, schema evolution via Schema Registry, stream processing with Flink-based tooling, and the telemetry pipelines that feed product analytics and billing. Because the product is the data infrastructure, engineers here operate closer to the systems layer than at most SaaS companies, where the warehouse is downstream of the product rather than central to it. If you enjoy thinking about throughput, partitioning, consumer lag, and exactly-once semantics as first-class concerns rather than occasional firefighting, the day-to-day here is well-matched to that preference.

The salary distribution here is heavily weighted toward junior levels: 11 of the 15 reports are at L3, compared to 4 at L5 with 15 years of experience behind them. That shape, combined with no open data engineering roles, means Confluent is not actively recruiting senior data engineers right now, and the path from entry to senior looks like a long one inside the company. If you're 2 to 5 years in and want a company actively building out a DE function, this probably is not the right moment. Where Confluent does make sense is for an engineer early in their career who wants deep Kafka exposure on a platform that handles real enterprise-scale streaming workloads, and who can tolerate some internal uncertainty while the company stabilizes. If that describes you, prep for systems-oriented streaming questions and check the ladder before negotiating level.