DevOps / Platform Engineer — Scientific Computing

<p><strong>Location:&nbsp;</strong>Remote within Europe, with regular presence in Bremen</p> <p><strong>Direct Reports:&nbsp;</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 analysis and dependency and licence scanning into the pipeline.</li> <li>Own backup, recovery and continuity for the platform.</li> <li>Support audit and compliance requirements from funded research and customer contracts.</li> </ul> <p><em>Accountability: no single undocumented dependency on one person, including yourself.</em></p> <h2>Requirements</h2> <p><strong>Experience</strong></p> <ul> <li>Strong AWS or equivalent, Kubernetes, and configuration management such as Ansible, at production scale.</li> <li>Real experience of on-premise and offline deployment, not only cloud.</li> <li>CI/CD pipeline ownership end to end</li> </ul> <p><strong>Skills &amp; Competencies</strong></p> <ul> <li>Autonomous and proactive. You have carried infrastructure alone.</li> <li>Willing to hand knowledge over rather than hold it.</li> <li>Interested in the product and the science, not only the pipeline.</li> <li>Clear communicator in English.</li> </ul> <p><strong>Education &amp; Languages</strong></p> <ul> <li>Degree in computer science or engineering, or equivalent practical track record.</li> <li>Fluent English.</li> </ul> <h2>What This Role Is (and Is Not)</h2> <p><strong>This role IS</strong></p> <ul> <li>Full ownership of infrastructure for a technically unusual product.</li> <li>A role where you finally get a team around you.</li> <li>Exposure to a broad modern stack.</li> </ul> <p><strong>This role is NOT</strong></p> <ul> <li>A pure cloud or pure on-premise role.</li> <li>A ticket-driven operations role.</li> <li>A role without contact with the product.</li> </ul>