DevOps / Platform Engineer — Scientific Computing

Constructor Knowledge Labs; Bremen; Hybrid; EUR 90.000 - 130.000; Vollzeit

Zusammenfassung

Constructor Knowledge Labs seeks a senior Infrastructure Engineer to own build, deployment and infrastructure for scientific software across cloud and on-premise environments. You will manage installers, upgrade paths, and migrations, while ensuring compliance and security in restricted networks.

Responsibilities include running Kubernetes, GitOps operations, secrets and IAM, IaC, monitoring, and cross-cloud integrations.

Qualifikationen

• Experience with AWS or equivalent at production scale.
• Kubernetes experience in production environments.
• Configuration management with Ansible at scale.
• Experience with on-premise and offline deployments.
• End-to-end CI/CD ownership.
• Fluent English communication.

Aufgaben

• Own build, deployment, and infrastructure for the platform across cloud and on-premise targets.
• Manage installers and update paths for restricted/offline environments.
• Handle database migrations and rollback paths for customer installations.
• Run Kubernetes and GitOps operations for the platform.
• Manage secrets, access control, and infrastructure-as-code.
• Implement monitoring and log aggregation across internal and customer environments.
• Support audit and compliance requirements for funded research and customer contracts.

Kenntnisse

AWS or equivalent

Kubernetes

Ansible

On-premise deployment

CI/CD

English communication

Ausbildung

Degree in computer science or engineering

Tools

GitOps tooling

Jobbeschreibung

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. The role combines conventional cloud platform engineering with the harder problem of shipping updatable software into environments we do not control.

Responsibilities

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 requirements from funded research and customer contracts.

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

Requirements

Experience

• 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

Skills & Competencies

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

Education & Languages

• Degree in computer science or engineering, or equivalent practical track record.
• Fluent English.

What This Role Is (and Is Not)

This role IS

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

This role is NOT

• A pure cloud or pure on-premise role.
• A ticket-driven operations role.
• A role without contact with the product.