Senior DevOps Engineer

About the Company

Experi.mate & Lab Connectivity CapabilitiesContextExperience-facing instrument booking platform, part of the D-WoW application suite. Scientists currently use Experi.mate for instrument reservations, with links out to a separate device connectivity solution for remote hood monitoring and a guided weighing workflow. wishes to bring these capabilities in-house, building them natively within Experi.mate. A new device connectivity vendor is currently being assessed and will serve as the integration layer between Experi.mate and lab instruments, connecting via the Mulesoft API gateway.

About the Role

Profile DevOps Engineer

Purpose Maintain and support the current device connectivity platform that depend on today, ensuring it remains stable and reliable while the replacement vendor selection is finalised. Over time, this role will shift toward supporting migration efforts as the new connectivity platform is onboarded and the current one is decommissioned.

Responsibilities

Two capability areas need to be built.

• First, camera live stream integration live video from lab cameras needs to be ingested directly into Experi.mate, while camera control commands route through Mulesoft via the device connectivity vendor.
• Second, data segregation the platform must ensure each user sees data only from their own assigned instruments, that device data is correctly routed to the right dashboard, and that instrument reassignments are handled cleanly.

What this person will work on

• Platform stability day-to-day operational ownership of the current device connectivity platform, keeping it running reliably for lab users across sites.
• CI/CD pipeline ownership maintain and improve build and deployment pipelines on GitLab/GitHub, using Artifactory for package management.
• Kubernetes cluster management cluster operations, scaling, and reliability for the connectivity platform infrastructure.
• Monitoring and observability own the Grafana/Prometheus stack; ensure meaningful alerting and dashboards are in place so issues are caught before scientists are impacted.
• Incident, Problem, and Change management operate within ITSM framework; lead or support incident response, root cause analysis, and change advisory processes.
• High-availability architecture ensure the platform is operated for resilience, particularly given the real-time nature of instrument connectivity workloads.
• Migration support as the replacement vendor is onboarded, support the transition from the current platform, including decommissioning activities.
• AWS hosted applications with some level on on-prem activity

Qualifications

• Seniority Mid level. This person needs to operate independently within an enterprise IT environment and navigate ITSM processes without hand-holding. Expect 4 years of DevOps or platform engineering experience. Prior experience maintaining third-party SaaS or connectivity platforms in an enterprise setting is a strong plus.

Required Skills

Skills and experience

• Skill / ExperienceLevelContext / Notes
• CI/CD (GitLab / GitHub)Must HavePipeline ownership, not just usage
• Artifactory (package management)Must HaveManaging dependencies and build artifacts in an enterprise setup
• Kubernetes (cluster management)Must HaveOperational ownership, not just deployment
• Grafana / PrometheusMust HaveObservability stack for the connectivity platform and its integrations
• ITSM processes (Incident, Problem, Change)Must Have operates a formal change management process; this person needs to work within it
• High-availability architecturesMust HavePlatform reliability is critical for lab instrument workloads
• Lab instrument connectivity / automation platformsMust HaveMust be able to get up to speed quickly on the current connectivity platform and its components

Preferred Skills

• Regulated environment experience (e.g. GxP)Good to HaveNot a GxP application, but rigorous testing discipline and structured change habits are highly valued
• Lab environments (physical)Good to HaveUnderstanding of lab operational context helps prioritise reliability and incident response work

Pay range and compensation package

Not specified.

Equal Opportunity Statement

Not specified.

Notes for SourcingRole is formally non-GxP. However, candidates who have worked in regulated environments tend to bring a testing rigour and change discipline that is genuinely useful here. That habit of mind is what we are looking for, not a specific validation credential.The lab instrument connectivity and physical lab experience criteria are listed as Good to Have, but candidates with this background will ramp significantly faster.

Understanding how scientists work alongside instruments is context that is hard to acquire on the job.