Перейти до вмісту
Kontakt.io

Staff Software Engineer

Kraków
4 місяці тому

Коротко

Staff Software Engineer role in Kraków. Focus on data ingress/egress pipelines, device integration (Cisco, Aruba), Kafka, gRPC, and system architecture. Requires technical leadership, driving standards, and cross-team ownership. Full-time, on-site.

Стислий виклад підготував ШІ на основі тексту оголошення.

Our team is the connective tissue of this platform. We own the full data ingress pipeline — from third-party devices (Cisco, Aruba, and beyond) to our internal Kafka backbone — and we own egress: streaming enriched location and telemetry data out to downstream systems, external APIs, and partner platforms. We are rebuilding this domain the right way: event-driven, observable, documented, and built to scale.

We need a technical anchor — someone senior enough to raise the bar, pragmatic enough to ship, and confident enough to drive alignment across engineering and product.

What you will work on:

Data ingress & device integration

Own the pipeline that brings external device data into the Kontakt.io platform. Build and maintain robust integrations with Cisco Spaces, Aruba, and similar third-party infrastructure. High-volume BLE telemetry, Kafka Streams, gRPC — multi-tenant SaaS where both correctness and latency matter.

Data egress & external integrations

Build and evolve the egress layer that streams enriched location and event data to partner systems and customer-facing APIs — real-time position feeds, alarm forwarding, standards-compliant adapters. You own how the outside world consumes Kontakt.io data.

Architecture & technical leadership

You will drive the architectural evolution: what to rewrite, what to stabilize, and how to sequence it without breaking production. You establish the engineering standards — documentation, testing with Testcontainers, observability with Prometheus/Grafana — and you hold the team to them.

Cross-team ownership

Work directly with product stakeholders to translate business requirements into engineering decisions. When scope is unclear, you clarify it. When dependencies block the team, you resolve them.

Опубліковано 2026-05-12
Джерело