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.</p> <h2>Responsibilities</h2> <p><strong>Pillar 1 Deployment and Delivery</strong></p> <ul> <li>Own build, CI/CD and release for the platform across cloud and on-premise targets.</li> <li>Build and maintain installers and update paths that work in restricted and offline environments.</li> <li>Manage database migration and rollback paths for customer installations.</li> </ul> <p><em>Success Metrics and KPIs: release frequency, failed deployments, time to patch a customer site.</em></p> <p><strong>Pillar 2 Infrastructure</strong></p> <ul> <li>Run the Kubernetes and GitOps side of the platform.</li> <li>Own secrets management, access control and infrastructure-as-code.</li> <li>Implement monitoring and log aggregation across internal and customer environments.</li> <li>Integrate with Constructor's platform, identity and deployment tooling.</li> </ul> <p><em>Success Metrics and KPIs: uptime, mean time to detect, infrastructure reproducible from code.</em></p> <p><strong>Pillar 3 Security and Governance</strong></p> <ul> <li>Introduce static ana