/ TEAMS · Apache Kafka Platform Engineering
Operate event streaming as essential infrastructure. Source Kafka specialists for broker architecture, replication, Connect pipelines, access control and operational reliability across production clusters.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
KRaft · Controller quorum
Topics · Partitions · ISR
Producers · Consumers · Connect
Schema Registry · ACLs
Lag · Rebalances · Upgrades
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Senior Apache Kafka Platform Engineer — Streaming Operations
Inquire availability13+ years of experience · Croatia
Apache Kafka Platform Engineer — Streaming Operations with 13 years in production systems, focused on Apache Kafka Platform Engineer — Streaming Operations and Production systems.
Languages: Croatian, English C1
Senior Apache Kafka Platform Engineer — Streaming Operations
Inquire availability8+ years of experience · Poland
Apache Kafka Platform Engineer — Streaming Operations with 8 years in production systems, focused on Production systems and Technical delivery.
Languages: Polish, English B2+
Mid-level Apache Kafka Platform Engineer — Streaming Operations
Available3+ years of experience · Romania
Apache Kafka Platform Engineer — Streaming Operations with 3 years in production systems, focused on Technical delivery and Apache Kafka Platform Engineer — Streaming Operations.
Languages: Romanian, English B2+
Mid+ Apache Kafka Platform Engineer — Streaming Operations
Inquire availability5+ years of experience · Poland
Apache Kafka Platform Engineer — Streaming Operations with 5 years in production systems, focused on Apache Kafka Platform Engineer — Streaming Operations and Production systems.
Languages: Polish, English B2+
/ Engineering teams
Onectus recruits engineers for production backend and infrastructure systems with integration, data and operational requirements. For Kafka-specific roles we distinguish broker/platform ownership from Java or Node.js application producers and consumers, qualifying cluster incidents and streaming operations for each candidate.
/ Technical specializations
A platform-focused Kafka hire should reason about replication, metadata controllers, partition allocation, connector health and recovery—not merely publish an event to a topic.
KRaft quorum, cluster metadata, controller behavior, broker provisioning and failure domains.
Topic configuration, ISR, leader elections, retention, replication factor and producer durability.
Connect clusters, source/sink connectors, offsets, DLQ strategy, retries and external system contracts.
Schema Registry, Avro/Protobuf compatibility, event evolution and consumer migration.
TLS/SASL, ACLs, service identities, quotas and isolated platform responsibilities.
Consumer lag, rebalances, disk/partition skew, throughput, rolling upgrades and incident runbooks.
/ Project scenarios
Trace broker I/O, replication delays, hot partitions and consumer backpressure.
Plan ZooKeeper-to-KRaft or version transitions with tested compatibility and rollback.
Improve Connect task recovery, schema evolution, offset handling and destination consistency.
Establish quotas, ACLs, monitoring, topic policies and incident ownership for tenants.
/ Practical evaluation
Validate experience with cluster failures, producer guarantees, consumer groups and connector recovery. Application-only Kafka experience is not enough for this page's core intent.
Can they diagnose ISR shrinkage, controller changes, skew and unavailable partitions?
Can they explain acks, idempotent producers, transactions and replay tradeoffs?
What failed connectors, offset problems, schema changes or replay processes did they handle?
How did they address lag, security, scaling, upgrades and service-level objectives?
/ Sourcing process
Kafka distribution/version, KRaft/ZooKeeper, partitions, Connect, schemas and SLOs.
Identify engineers with proven broker and streaming infrastructure responsibilities.
Discuss replication, consumer lag, offset recovery, security and upgrades.
Confirm access controls, on-call scope, change windows and availability.
Profiles, availability and engagement terms are confirmed for each request.
/ Questions
A platform engineer owns broker health, replication, Connect infrastructure and upgrades. Application engineers primarily implement producers, consumers and event-driven business logic.
Yes. Share Kafka versions, cluster topology, migration stage, downtime constraints and change-control expectations.
Yes when your platform owns integration services and schema governance; provide connector types, expected throughput and compatibility rules.
Yes. Specify boundaries around client libraries, event contracts, observability, data recovery and shared incident response.
/ Onectus · TEAMS
Tell us the technology, production responsibilities, experience level and working model. We'll activate the appropriate engineering sourcing channels.
