Senior Software Engineer-MLOps & Observability

CloudFerro creates technologies used daily by European leaders in science and the space sector, including ESA, EUMETSAT, ECMWF, Mercator Ocean International, DLR, and EGI. The company works closely with the Earth Observation sector to support analyses and better understanding of our planet. They are building a sovereign European cloud platform from scratch, offering a complete PaaS stack based on Kubernetes and open source technologies.

• Experience with Kubernetes: independently building or operating complex systems running on Kubernetes.
• Designing distributed systems: practical skills in creating scalable and reliable services.
• Proficiency in Go and good knowledge of Python: developing operators, controllers, APIs, and CLI tools.
• Integrations and APIs: ability to build API wrappers and integrations with REST/gRPC frameworks.
• AI-assisted development: comfortable using tools like Claude Code or Copilot as a natural part of daily work.

Nice to have:

• Experience with ML platforms: Kubeflow, JupyterHub, GPU scheduling on Kubernetes.
• Knowledge of Airflow or other workflow orchestration tools.
• Observability stack: Prometheus/Thanos, Grafana, Loki, OpenTelemetry.
• Multi-tenant monitoring: exposure of metrics and logs per client.
• Terraform providers: creating custom resources.
• Experience at a cloud provider: working in cloud service environments.
• Open source contributions: especially in the CNCF ecosystem.

• Full ownership of MLOps and Observability: responsible for Kubeflow, Airflow, Jupyter Notebooks, and Observability as a Service in a you build it, you own it model, covering architecture, code, API, documentation, and operational stability.
• Development of the monitoring platform: building observability services for clients based on foundations prepared by Platform DevOps / SRE Engineers.
• End-to-end delivery: from operator/integration, through API endpoint and CLI command, to Terraform resource and documentation.
• Integration with common services: connecting services with IAM, billing, and quota systems developed by the Common Services team.
• Co-creating technical standards: collaborating with other Product Engineers on platform development direction and best practices.