Platform Observability Engineer

ICEYE is the world leader in sovereign intelligence from space. We deliver persistent monitoring capabilities to detect and respond to changes in any location on Earth. ICEYE owns the world's largest and most advanced SAR (synthetic aperture radar) satellite constellation.

• Own and continuously improve a unified, production-grade observability stack covering metrics, logs, and traces, giving every team a consistent, self-service way to understand and operate the health of their services.
• Build and maintain trusted alerting by tuning alerts against clear SLOs/SLIs, reducing noise, improving ownership and ensuring real issues surface early.
• Define, document, and drive adoption of instrumentation standards covering metric naming, label cardinality, structured logging, and distributed tracing with OpenTelemetry.
• Enable product teams to diagnose and resolve incidents faster through well-designed dashboards, runbooks, hands-on support, and practical observability guidance.
• Run the observability platform like a product, owning its roadmap, interfaces, reliability, scalability, and cost across areas such as retention, sampling, and cardinality.
• Provide clear technical direction for observability across the engineering organisation, making pragmatic architectural trade-offs and helping teams adopt platform capabilities effectively.

• 6+ years in Platform Engineering, Observability, or infrastructure roles, with end-to-end ownership of a production observability stack (for example the LGTM stack - Loki, Grafana, Tempo, Mimir/Prometheus - or an equivalent metrics/logs/traces platform) at scale.
• Instrumentation & telemetry: OpenTelemetry adoption, metric and label design, structured logging, and distributed tracing across complex, multi-team systems.
• SLO/SLI & error budgets: dashboards and alerting that surface real problems early while minimizing noise and false positives.
• Platform as a product: treating other engineering teams as customers, with clear interfaces and a roadmap shaped by their needs.
• Alerting & reliability attitude: comfortable with on-call, driving blameless learning from incidents, and continuously tuning signal quality instead of letting alert fatigue set in.
• A background that includes time spent writing and shipping production software, bringing engineering instincts to building tooling and automation rather than only operating what already exists.
• Proficiency in at least one backend language (for example Python or Go) for automation, tooling, and building internal observability capabilities.
• Demonstrated experience owning the long-term consequences of your own architectural and tooling decisions - having lived with what you built through its maintenance, upgrades, and failure modes, not just its initial rollout.
• Excellent written and verbal communication skills in English, able to explain complex system behavior clearly to both engineers and non-technical stakeholders.

• Permanent employment.
• Hybrid workplace model.
• Employment is subject to applicable security screening (incl. SUPO).