Applied AI & ML Systems
Custom model pipelines, RAG architectures, and inference infrastructure engineered for production reliability, not demo theatre.
[ Life & Brain GmbH / est. software engineering ]
We build resilient platforms, data systems, and applied AI for teams operating where biology, research, and industry converge. No theatrics — just software that runs, scales, and keeps running.
Life & Brain GmbH was founded on the conviction that the most consequential software of the next decade will be built at the borders — between disciplines, industries, and regulatory regimes.
We assemble small, senior teams around a shared operational grammar: measured decisions, transparent tradeoffs, and code you can still read at 2AM. Our work spans genomics platforms, clinical infrastructure, applied AI systems, and the quiet plumbing that keeps modern organizations functional.
Based in Germany, delivering globally, deliberately mid-sized so senior people stay close to the work.

We believe software should be an instrument of clarity, not a source of it. Our mission is to deliver systems that the organizations depending on them can understand, operate, and evolve — long after our engagement ends.
The people you meet in the pitch are the people who write the code.
Every non-trivial decision is documented, dated, and reviewable.
You should never learn about production from a customer.
Deterministic environments, versioned data, replayable pipelines.
We speak GDPR, HIPAA, and ISO fluently — as engineers, not lawyers.
We choose the smallest interesting solution that could work.
Custom model pipelines, RAG architectures, and inference infrastructure engineered for production reliability, not demo theatre.
Warehouses, lakehouses, and streaming pipelines that turn scattered signal into governed, queryable evidence.
Reproducible genomics, imaging, and multi-omics workflows built on modern orchestration and containerized compute.
Full-stack web platforms, internal tools, and clinical dashboards designed for demanding daily operators.
Infrastructure as code, zero-downtime delivery, and observability that turns operations into a boring, predictable rhythm.
GDPR, HIPAA, and ISO-aligned engineering with auditable trails baked into the architecture from day one.
Deep discovery with stakeholders, data audits, and system archaeology.
Architecture proposal, RFCs, and a shared vocabulary for the build.
Vertical slice in weeks; real code, real data, real feedback loops.
Testing, observability, security review, and load characterization.
Progressive rollout with instrumentation from the first release.
Handover with runbooks or continued partnership under an SLA.
We choose tools we can defend, operate, and hand over. No language wars — just fit for purpose.

Lab automation, ELN integrations, discovery platforms.
Clinical workflow tools, patient-facing apps, connected devices.
Grant-funded platforms, data commons, reproducibility tooling.
Device firmware companion apps, regulatory-ready pipelines.
Actuarial platforms, underwriting AI, risk observability.
Edge collection, telemetry, and predictive maintenance.
Interactive variant analysis over 40M records with sub-second cohort queries.
Multi-site trial console orchestrating consent, capture, and quality review.
Low-latency inference routing across 6 regions with autoscaled GPU fleets.
Unified lakehouse ingesting 22 upstream systems into one queryable model.
Rebuilt a genomics preprocessing pipeline on Nextflow + Kubernetes, cutting end-to-end runtime from 18h to 6.5h per cohort.
Replaced an aging monolith with an event-driven core; ingest throughput tripled while operational cost stayed flat.
Introduced SLO-driven observability across an FDA-regulated product line — twelve months incident-free since launch.
They act like an internal team with an external perspective. The rigor they brought to our data infrastructure changed how the whole company operates.
Precise, calm, and unusually good at translating research constraints into shippable software. A rare combination.
We stopped talking about technical debt and started talking about roadmap again. That's the outcome I was hired to produce.
We stay deliberately small so the people writing the RFC are the people writing the deploy. Every engagement is staffed from the same bench.

Why teams that invest in deterministic compute stop firefighting and start compounding.
A pragmatic pattern for products that must remember what happened, not just what is.
Where retrieval architectures succeed, and where they quietly collapse under real load.