A method has limited value if it cannot be run, inspected, maintained, and reused.
Scientific software needs to preserve the evidence while making the work operational. My work turns statistical methods, omics workflows, clinical data, and reporting requirements into reproducible tools, structured outputs, and user-facing systems.
What this work resolves
Research code to system
Scientific code needs structure, documentation, testing discipline, versioning, and outputs that other people can understand and reuse.
Data to report
Complex omics and clinical workflows need structured reports, machine-readable outputs, and clear links between input, processing, and interpretation.
Method to product
Statistical methods become more useful when they are wrapped in usable interfaces, reproducible workflows, and practical decision support.
Prototype to infrastructure
Biomedical software has to operate across data quality, security, governance, user needs, and long-term maintainability.
Evidence at a glance
20+
public scientific software, data, reporting, and evidence products across genomics and biomedical systems
An average of
3,000+
combined CRAN downloads per quanter (i.e. 2026 Q1) across public R software
30+
stakeholders engaged across biotech, healthcare, academia, public-sector genomics, and clinical research
100+ TB
biomedical data supported through secure, reproducible, and traceable analytical infrastructure
Methods, standards, and systems
Scientific programming
R, Python, Bash, C, Rust, package development, command-line tools, Git, reproducible reports, machine-readable outputs, and software releases.
Workflow automation
Linux, Unix, high-performance computing, Docker, Singularity or Apptainer, Nextflow, Snakemake, versioned pipelines, and reproducible analytical frameworks.
Biomedical data systems
SQL, PostgreSQL, EHR-linked workflows, structured metadata, controlled file transfer, encrypted storage, traceability, and data governance.
Web and platform delivery
HTML, CSS, JavaScript, Next.js, React, TypeScript, Supabase, Vercel, APIs, authenticated systems, and user-facing biomedical platforms.
Reporting and interpretation
Structured standalone HTML reports, variant interpretation outputs, visual analytics, QC summaries, clinical research dashboards, and evidence-linked documentation.
AI and data workflows
Machine learning in omics, PyTorch, AI-assisted scientific software, local model deployment, API-based model deployment, and retrieval-augmented scientific workflows.
Relevant experience
3 years (2023 to present) · Universitäts-Kinderspital Zürich
Reproducible clinical genomics and multi-omics workflows
Built R and Python workflows for genome-wide, rare variant, gene-level, and multi-omic analyses in secure Linux and high-performance computing environments.
WGS, RNA-seq, proteomics, metabolomics, EHR-linked data, approximately 1,000 children, more than 100 TB of biomedical data, structured outputs for clinical research review.
Selected product development · Switzerland Omics
Scientific software, reporting, and data products
Developed product-facing biomedical data workflows that translate statistical genomics methods into reproducible reporting, probabilistic interpretation, and secure data systems.
R packages, CRAN releases, structured HTML reports, YAML criteria, PostgreSQL, Supabase, Next.js, React, TypeScript, APIs, authenticated scientific software.
5 years (2018 to 2023) · EPFL Global Health Institute
Analytical workflow development for translational cohorts
Built reproducible statistical and computational workflows across infectious, inflammatory, genomic, and multi-omic cohort studies.
Cohorts up to 5,000 participants, R, Python, Linux, high-dimensional modelling, rare variant analysis, data visualisation, reports, figures, and collaborative scientific outputs.
Working fit
Biomedical software teams need maintained workflows where data, method, report, and user action stay connected while preserving the underlying science.