I build the platforms that let regulated teams ship fast and stay compliant.

I run the DevOps Center of Competence at B. Braun SE, an international medical device and pharmaceutical manufacturer. The platform runs on Kubernetes as a universal API, with Crossplane as the control plane for infrastructure. Compliance lives in that contract, not in a review after deployment. That's platform engineering, not paperwork.

Bad Emstal, GermanyLinkedInGitHub

The numbers

Numbers I am accountable for.

>100
developers served by the platform
4 → 13
engineers grown in the DevOps CoC (Dec 2024 – Sep 2026)
99.9%
internal platform SLO, run with error budgets
6
international hubs supported across Europe

What I do

From DevOps to platform engineering, with SRE built in.

Platform engineering

Self-service infrastructure: Kubernetes with Crossplane

Product teams build their own infrastructure using Kubernetes and Crossplane compositions instead of filing a ticket. Over 100 developers use these standard patterns on the developer platform.

A product team submits a claim to a Crossplane composition, which provisions cloud resources.productteamclaimCrossplanecompositiongolden pathapplycomputedatabasenetwork
// team → composition → cloud, self-service
DevSecOps & compliance

The company's first standardised DevSecOps process

Built in three months. It gives cloud-native teams one standard way to align with IEC 62304 and ISO 13485 and govern releases for regulated products. The compliance gate runs in the pipeline, not after it.

A pipeline with commit, build, and scan stages passing through a compliance gate before release.commitbuildscanvalidatereleasefail → back to commit
// commit → build → scan → [compliance gate] → release
Building the org

From 4 to 13 engineers, and still growing

A four-person system team supports a regulated medical-device Agile Release Train. Planned hubs in Malaysia and Colombia will extend that support across time zones as the CoC grows.

A growth chart showing the CoC growing from 4 engineers in December 2024 to 13 in September 2026.051015Dec '24Sep '26413
// CoC headcount, Dec 2024 → Sep 2026

Experience

Twenty years of building and running infrastructure.

For the peers reading

How I think about platforms.

Sebastian Ickler, Head of CoC DevOps & Platform Engineering
Sebastian Ickler, Head of CoC DevOps & Platform Engineering
B. Braun SE
01

I turn DevOps teams into platform engineering teams. Nobody's written that playbook yet. I like fixing what everyone's gotten used to being broken.

02

Platforms win on adoption, not on features. If a team needs a ticket, the platform failed.

03

Compliance is a design constraint, not a gate at the end. IEC 62304 and ISO 13485 alignment belongs in the composition.

04

Reliability is a budget you spend, not a number you promise. SLOs, error budgets, honest postmortems.

Tools

The stack I build and run on.

Azure iconAzure
Kubernetes iconKubernetes
Crossplane iconCrossplane
GitHub iconGitHub
Grafana iconGrafana
Prometheus iconPrometheus
OpenTelemetry iconOpenTelemetry
Terraform iconTerraform
Ansible iconAnsible
SonarQube iconSonarQube
Snyk iconSnyk
Linux iconLinux
Docker iconDocker

Building a platform engineering practice in a regulated industry?

I work best where compliance, reliability and developer experience all have to hold at once. If that is your problem, email me.