Skip to content
Esc
Internships in Canada
New-grad roles in Canada
Remote roles
Roles that show pay
Postings at high ghost risk
PayWhat student tech roles in Canada pay
Check a linkPaste a posting to see its real age and ghost risk
JobsEvery open tech role
CompaniesWho fills fastest, who leaves postings up
Hiring calendarWhen employers open intern and new-grad roles
Skills gapWhat postings ask for that you don't have
Your resumeScore and fixes
Your matchesOpen roles ranked by your resume
ApplicationsSaved, applied, interviewing, offers
SettingsTheme, text size, motion
How it works

↑ ↓ to move, Enter to open? every shortcut

Keyboard shortcuts

CtrlKor/
Search employers, postings and pages
JorK
Next or previous posting in a list
O
Open the posting's page
Enter
Open it in the preview, on wide screens
S
Save or unsave it
?
This list
Esc
Close
Constructor Labs

DevOps / Platform Engineer — Scientific Computing

  • Seen live on Constructor Labs' site today
  • Mid level
Pay
Not stated
Location
Germany
Open for
12+ days
First seen
Oct 23, 2026
Apply on Constructor Labs' site (opens in a new tab)

Posting record

No flags

Open 12+ days

The posting's record, oldest first
  1. Constructor Labs' site dates the posting
  2. Ghostless first sees this listing
  3. Last checked: still up
How we know

It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.

Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Constructor Labs, so its true age is longer.

Last checked Nov 4, 2026.

How well do you match?

See how much of this posting your resume shows, and what it's missing.

Upload your resume

What the posting discloses

Not stated: Pay, real vacancy, AI screening.

Why these three

Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.

Some employers add pay only on their own site. Check the original posting before you rule it out.

Skills mentioned

About the role

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.

Something wrong with this posting?