Senior Platform Engineer
Listed on 2026-05-31
-
IT/Tech
Systems Engineer, Network Engineer, Cloud Computing
Location
Valencia
Employment TypeFull time
Location TypeOn-site
DepartmentEngineering
Role highlights:- Senior Platform Engineer
- Location:
Valencia, Spain - Department:
Signal Processing - Reports to:
Engineering Manager, Signal Processing - Employment type:
Permanent - Workplace model:
Hybrid (3 days per week in office) - Employment is subject to applicable security screening (incl. SUPO, where required)
As the first dedicated Platform Engineer for ICEYE's newly forming Signal Processing and Acquisition Planning teams, you will build the infrastructure foundation that two critical engineering teams depend on to deliver next-generation satellite intelligence capabilities. From Kubernetes environments and deployment pipelines to networking, secrets management, and on-premises deployment patterns, you will own the full platform stack — designing it from day one to work equally well in the cloud and in customer‑controlled, off‑cloud environments.
This is a greenfield role with real stakes: the infrastructure decisions you make now will shape how these teams operate for years, directly underpinning a capability that contributes to the defence of Europe.
Container environments and compute infrastructure. Kubernetes clusters, resource management, networking, storage, access control, and compute capacity that teams can build on. You own the environments, you keep them healthy, and you design them with an on‑premises‑first approach from day one, even if we also run them in the cloud.
Deployment and environment tooling. Reproducible, reliable deployment pipelines. Infrastructure‑as‑code that teams can understand and extend. Environments that can be spun up, torn down, and updated without drama.
On‑premises environments. Everything we build will eventually run in customer environments that are not cloud‑based. This constraint shapes infrastructure choices from the start: portable deployments, well‑defined infrastructure contracts, and clean separation between what the platform provides and what the applications consume. You will design the infrastructure so that the stack works the same on‑premises as in the cloud.
Networking and access management. Service‑to‑service communication, ingress, network policies, secrets management, and the access control patterns and services that keep things secure without slowing teams down.
Whatever comes next. GPU compute provisioning for signal processing workloads, security hardening, integration with IceOS platform services, or capabilities that emerge as the teams grow. You will help define what the infrastructure becomes.
Must haves:
Strong infrastructure and platform engineering fundamentals. You have built and operated the infrastructure that other teams depend on. You understand what it means to be a platform team: your users are engineers, your SLAs are their productivity, and your failures cascade. You have opinions about how to do this well, grounded in experience.
Container orchestration in production. You have designed, deployed, and operated Kubernetes or equivalent environments in production. You understand networking, storage, resource management, and the operational realities of keeping these environments healthy. This is the core of what you will own.
Infrastructure‑as‑code and deployment automation. You have built reproducible infrastructure with tools like Terraform, Pulumi, or equivalent. You know how to make deployments safe, fast, and predictable. You have seen what happens when infrastructure drifts, and you know how to prevent it.
On‑premises and hybrid deployment experience. You have shipped software to environments you do not control. You understand the difference between running in your own cloud and running on customers’ premises, and you have designed infrastructure that works in both.
AWS experience. Production experience with AWS services: EKS, VPC, IAM, S3, and the networking and identity patterns that underpin cloud infrastructure.
Networking and security fundamentals. You understand service‑to‑service communication, network policies, ingress, TLS, secrets management, and access control. You can…
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).