DevOps / Platform Engineer - Scientific Computing

Location:

Remote within Europe, with regular presence in Bremen

Direct Reports:

None

Working Model:

Remote / hybrid. Regular time on-site in Bremen.

Mission

Own build, deployment and infrastructure for scientific software that runs in awkward places - customer premises, restricted laboratory networks, air-gapped sites, and our own cloud

combines conventional cloud platform engineering with the harder problem of shipping updatable software into environments we do not control

Pillar 1 Deployment and Delivery

Success Metrics and KPIs: release frequency, failed deployments, time to patch a customer site.

Pillar 2 Infrastructure

Success Metrics and KPIs: uptime, mean time to detect, infrastructure reproducible from code.

Pillar 3 Security and Governance

Accountability: no single undocumented dependency on one person, including yourself

• Own build, CI/CD and release for the platform across cloud and on-premise targets.
• Build and maintain installers and update paths that work in restricted and offline environments.
• Manage database migration and rollback paths for customer installations.
• Run the Kubernetes and GitOps side of the platform.
• Own secrets management, access control and infrastructure-as-code.
• Implement monitoring and log aggregation across internal and customer environments.
• Integrate with Constructor's platform, identity and deployment tooling.
• Introduce static analysis and dependency and licence scanning into the pipeline.
• Own backup, recovery and continuity for the platform.
• Support audit and compliance requirements from funded research and customer contracts.

Experience

Skills & Competencies

Education & Languages

What This Role Is (and Is Not)

This role IS

This role is NOT

• Strong AWS or equivalent, Kubernetes, and configuration management such as Ansible, at production scale.
• Real experience of on-premise and offline deployment, not only cloud.
• CI/CD pipeline ownership end to end
• Autonomous and proactive. You have carried infrastructure alone.
• Willing to hand knowledge over rather than hold it.
• Interested in the product and the science, not only the pipeline.
• Clear communicator in English.
• Degree in computer science or engineering, or equivalent practical track record.
• Fluent English.
• Full ownership of infrastructure for a technically unusual product.
• A role where you finally get a team around you.
• Exposure to a broad modern stack.
• A pure cloud or pure on-premise role.
• A ticket-driven operations role.
• A role without contact with the product.