Bilal Meddah

Geneva · open to senior and staff roles

Bilal Meddah, Senior Full-Stack Engineer & Tech Lead. I build platforms, interfaces, APIs, test systems, AI features
end to end.

Senior full-stack engineer and tech lead with 12 years in production. I take products from data model to interface, and I build the tests and pipelines that keep them reliable.

See my work Read the résumé
production platforms shipped: research, simulation, healthcare SaaS, mobile
4
LLM assistants shipped to platform users
2
of a new research platform’s web client, built by me
~90%
end-to-end checks guarding every release
300
page load on scientific publication sites
−70%
sign-up conversion on a SaaS landing page
+20%

What I do

Six things I bring to any engineering team.

Open any of them to see the work behind it, across every company.

01

System design & architecture

Service boundaries, data models, migrations and API contracts that let teams change their part safely.

Microservices · FastAPI · REST · GraphQL · data migration · PostgreSQL · Kafka

7 pieces of work 02

Full-stack product engineering

Features shipped end to end, from database schema and API to a fast, consistent interface.

React · Next.js · TypeScript · Python · FastAPI · Node.js · React Native

8 pieces of work 03

Quality & reliability

Test systems and safeguards that catch problems before users do.

Playwright · end-to-end testing · CI quality gates · token lifecycle · Lighthouse

6 pieces of work 04

Applied AI

AI features backed by real tools and data, and AI agents that speed up engineering.

LLM tool use · agents · intent routing · AI-generated tests · image pipelines

4 pieces of work 05

Delivery & developer experience

Fast builds, reliable pipelines and monorepos, so teams ship small changes often.

Vite · Webpack · GitHub Actions · monorepos · Docker · Kubernetes · AWS

5 pieces of work 06

Technical leadership

Technical direction, design reviews and mentoring, while still shipping code.

Tech Lead · team of 5 · design reviews · mentoring · product planning

3 pieces of work

Experience · the last 6 years

Four companies, each in motion.

Every role has its own reel. It plays by itself; pause it or pick a slide any time.

01 · – now Lausanne

Open Brain Institute

openbraininstitute.org ↗

Senior Full-Stack Engineer

Full-stack platform engineering for a cloud research product: the multi-tenant workspace, the legacy data migration, the core APIs, features across every section of the app, and the end-to-end test system that checks it all.

System design & architecture
  • Multi-tenant research workspace on Python/FastAPI microservices: lab and project isolation, fine-grained access control, configurable compute environments.
  • Legacy data migration into the new core: schema mapping, re-runnable backfills, validation passes and a staged cut-over by data type.
  • Service boundaries, domain models and versioned API contracts for the core entity service, one source of truth across services.
Full-stack product engineering
  • Full-stack features across the data, workflows and virtual-lab sections, each shipped from FastAPI endpoint to React screen.
  • ~90% of the new React/TypeScript client: server-state caching, normalized stores, virtualized data-heavy views.
  • Legacy app migrated to a modular core screen by screen, without a feature freeze; frontend tech debt down by more than 60%.
Quality & reliability
  • obi-e2e: 84 scenarios and 300 Playwright cases from plain-English specs, run on preview, staging and production.
  • Credential-lifecycle manager: background token refresh keeps long-running jobs authenticated past expiry.
  • Run hygiene on every test run: service health preflight, self-provisioned projects, automatic cleanup.
Applied AI
  • AI research assistant, built with the AI team: data discovery, summaries, intent-based routing to tools and datasets.
  • AI agents that generate and repair Playwright tests from scenarios, reviewed through pull requests.
  • Image pipelines for scientific artifacts: normalization, compression, model-driven synthesis.
open brain platform · simplifiedarchitecture · request walk
client
Web clientReact · TypeScriptServer-state cachequeries · invalidation
access
Sign-inOIDC tokensPermissionslab · project · resource
services
WorkspaceFastAPI · labs, envsCore entitiesFastAPI · contractsJobsruns · auth managerAI assistantLLM · tool calls
data
Relational storeper-tenant dataObject storageartifacts · images
quality
obi-e2ePlaywright · 300 casesCIGitHub Actions
  1. 1 · A researcher creates a project in the web client
  2. 2 · The token is checked and the lab role resolved
  3. 3 · The workspace provisions the project environment
  4. 4 · The core service writes entities through its contract
  5. 5 · The cache updates, every screen agrees
  6. 6 · obi-e2e replays this path on every release
The platform, layer by layerWhere my work sits, and how one request travels through it.
Under the hoodmulti-tenant isolationcontract-first APIsserver-state cacheE2E on every release
Slide 1 of 7 · illustrative, simplified from the real work

02 · – Geneva

EPFL, Blue Brain Project

bluebrainnexus.io ↗

Software Engineer, then Tech Lead after 4 months

Led the engineering of a distributed simulation platform, brought an LLM assistant to researchers, and made the team’s build and delivery much faster.

System design & architecture
  • Distributed simulation platform: parallel job orchestration, real-time multi-user sessions, streamed results.
  • API layer between the interactive UI and compute: launch, status and results for long-running runs.
Full-stack product engineering
  • Collaborative research tools: shared workspaces and data-driven views for daily research workflows.
  • React 18 concurrent rendering for responsive, data-heavy interfaces.
Delivery & developer experience
  • Publication sites moved from a CMS to JAMStack: 70% faster pages, lower server load.
  • React 16 → 18 and Webpack 4 → Vite 6, upgraded in steps: CI/CD 50% faster, builds 40% faster.
Applied AI
  • LLM assistant for natural-language queries over scientific data, from API design to product UI.
Quality & reliability
  • E2E testing and CI pipelines, shared test libraries and developer utilities.
Technical leadership
  • Tech Lead for a team of 5 engineers: roadmap, design reviews, code-review standards, mentoring.
simulation platform · simplifiedarchitecture · request walk
client
Simulation UIReact 18 · Vite 6Shared sessioncollaborators live
services
Simulation APIlaunch · statusLLM assistantdata queries
compute
Orchestrationparallel runsWorkersmany in parallel
delivery
Publication sitesstatic · CDNCI/CDE2E gates
  1. 1 · A scientist sets up a simulation
  2. 2 · The API validates it and launches the run
  3. 3 · The work is split into parallel jobs
  4. 4 · Results stream to everyone in the session
  5. 5 · Every change ships through tested pipelines
The simulation platformFrom one scientist’s click to results shared with the whole team.
Under the hoodReact 18 + Vite 6real-time collaborationparallel computetested pipelines
Slide 1 of 6 · illustrative, simplified from the real work

03 · – Algiers

Bee-Solutions

beesiha.com ↗

Tech Lead, Senior Full-Stack Engineer

Led the architecture and delivery of a healthcare SaaS platform, from the first module to a product several teams could grow in parallel.

System design & architecture
  • Micro-frontend architecture: an app shell for routing, auth and layout, with product modules built and deployed independently.
  • Reusable backend components for authentication, validation, notifications and audit logging, shared by every module.
  • Role-based access for clinic staff and administrators, enforced on the API and reflected in the UI.
Full-stack product engineering
  • Patient, appointment and billing workflows built from database schema and REST endpoints to the UI.
  • Shared UI kit (forms, tables, scheduling and date components) used across all modules.
  • Landing page 50% faster with HTTP/CDN caching, code-splitting and lazy loading; conversion up 20%.
Delivery & developer experience
  • Monorepo with shared packages and one toolchain; CI builds and tests only what a change affects.
  • Independent, versioned module releases; the shell loads new modules without a full redeploy.
Quality & reliability
  • Unit and integration tests on shared packages, lint and type gates on every merge.
  • Error monitoring and structured logging in production.
Technical leadership
  • Tech Lead for a team of 5 engineers: architecture decisions, design and code reviews.
  • Planning with product: scoped milestones, regular delivery, clear ownership.
healthcare saas · simplifiedarchitecture · request walk
shell
App shellrouting · auth · layout
modules
Patientsmicro-frontendAppointmentsmicro-frontendBillingmicro-frontendReportsmicro-frontend
shared
UI kitshared componentsAPI clienttyped
backend
Backend modulesreusable componentsDatabaserelational
delivery
Monorepo CIaffected buildsBundlesversioned
  1. 1 · The billing team changes their module
  2. 2 · CI builds and tests only billing
  3. 3 · The new bundle is published on its own
  4. 4 · The shell loads it, nothing else moves
A modular SaaSTeams own modules. The shell puts them together.
Under the hoodmicro-frontendsshared UI kitreusable backend modulesmonorepo CI
Slide 1 of 5 · illustrative, simplified from the real work

04 · – Leeds, UK · remote

Riverdone Digital

Senior Software Engineer, Mobile

Cross-platform mobile apps for enterprise clients, built and maintained from one TypeScript codebase.

Full-stack product engineering
  • React Native and Expo apps for iOS and Android from one TypeScript codebase.
  • Shared component library and typed API clients across client apps, including Juice Plus+, Kudos and Fimimus.
Delivery & developer experience
  • One build pipeline producing releases for both app stores.
Quality & reliability
  • Large-scale refactor into feature modules, with documentation next to the code: less maintenance, faster onboarding.
mobile apps · simplifiedarchitecture · request walk
core
Shared corecomponents · stateAPI clienttyped
apps
iOS appReact NativeAndroid appReact Native
build
Buildsboth platformsDocsnext to the code
backend
Client APIsenterprise backends
  1. 1 · A feature is written once in the shared core
  2. 2 · Both native apps pick it up
  3. 3 · One build produces both releases
  4. 4 · The docs change with the code
One core, two appsShared TypeScript code under two native apps.
Under the hoodReact Native + Exposhared TypeScript coreone API client
Slide 1 of 5 · illustrative, simplified from the real work

Prologue · 2014 – 2020

Six years where I learned the craft.

Software Engineer, Prime Minister’s IT Department, Algiers

  1. i.Enterprise systems for several ministries: healthcare, infrastructure and consultancy.
  2. ii.Every stage of delivery: requirements, implementation, testing and deployment.
  3. iii.Code audits and performance reviews for long-term maintainability.