Intervento
An incident management platform that connects its web UI and offline app on one shared domain.
Read case studyTech Lead & Software Architect — Switzerland
Since 2022 I have built production platforms for emergency response, planning and identity — from database to mobile app.
01 — Selected work
No practice projects: production systems with real users, real data and real failure modes.
View all projectsAn incident management platform that connects its web UI and offline app on one shared domain.
Read case studyA Flutter app for field operations that works without a network and synchronises reliably afterwards.
Read case studyAlarm management, dispatch and situational awareness for public safety organisations — four apps, one backend, one shared operational picture.
Read case studyThe authentication and authorisation layer above ZITADEL: web sessions, mobile device sessions and machine access in one model.
Read case study02 — What I do
I work where architecture and delivery belong together. Responsibility does not stop at the API boundary.
System design, technology selection, API and data modelling, authentication boundaries and code reviews. I make decisions that still hold after the next release.
Vue 3 and JavaScript on the front end, Node.js/Express and GraphQL on the back end; TypeScript and NestJS in Heimdall. PostgreSQL, migrations and deployment in between. I deliver features end to end.
Flutter apps with local persistence and a sync architecture designed in-house — from offline maps and on-device speech recognition to NFC/BLE integration. Built for places where the network is unreliable and no incident may be lost.
Docker/Compose, CI/CD, 2,033 migration files, 79 CI pipeline commits, seeding and structured documentation. I do not just make software run; I bring it into production reliably.
03 — How I work
Technical decisions are only as good as the context in which they are made.
I start with workflows, data and failure modes — not with frameworks. Technology follows from requirements; it is not the starting point.
Architecture is documented, interfaces are described and context remains traceable. The documentation lives in the repository — as 18 agent skills with around 3,700 lines that people and coding agents can read.
Offline sync, retries, conflicts and authentication boundaries are considered from the start — not added afterwards.
From the first migration to the code review: I take responsibility for the result, not only for my own part.
04 — Skills
No percentage bars. Every skill is linked to a project where I used it in production.
System design, technology decisions and technical ownership.
From the Vue frontend through GraphQL to the database.
Flutter apps and synchronisation under real network conditions.
Builds, deployments and the infrastructure behind them.
Business contexts in which I have worked in production.
05 — Experience
The projects I have worked on since 2022 — and what I was responsible for in each.
06 — Contact
I am looking for a position where I can take responsibility for systems and teams as a tech lead, software architect or senior full-stack engineer. Ideally where reliability, data and real-world workflows meet.
Direct and uncomplicated — no recruiting forms.
Location: Switzerland