DevOps / Platform Engineer — Scientific Computing

<p><strong>Location: </strong>Remote within Europe, with regular presence in Bremen</p> <p><strong>Direct Reports: </strong>None</p> <p><strong>Working Model: </strong>Remote / hybrid.

Regular time on-site in Bremen.

</p> <h2>Mission</h2> <p>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.

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

Responsabilidades

Pillar 1 Deployment and Delivery

• 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.

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

Pillar 2 Infrastructure

• 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.

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

Pillar 3 Security and Governance

• Introduce static analysis and dependency and licence scanning into the pipeline.
• Own backup, recovery and continuity for the platform.
• Support audit and compliance

  Requisitos

  from funded research and customer contracts.

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

Requirements

...