DevOps / Platform Engineer — Scientific Computing
Free to start · No card · 5 credits the moment you sign up
Job description
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.
Prepare your application
Use the description above to assess your fit for Constructor Labs. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.