Intervento
An incident management platform that connects its web UI and offline app on one shared domain.
Read case studyLead Engineer & Software Architect — Switzerland
Since 2022 I have built production platforms for emergency response, planning and identity — from database to mobile app.
01 — Selected work
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: offline maps, on-device speech recognition and NFC/BLE integration. Built for places where the network is unreliable and no incident may be lost.
Docker/Compose, CI/CD, database migrations, seeding and structured documentation. Production ownership including on-call duty: I analyse and resolve incidents in live systems myself. Software goes live only when it can also be operated 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 and is read by people and tools.
Offline sync, retries, conflicts and authentication boundaries are considered from the start — not added afterwards.
I take responsibility for the result. Migration, operations and code review are part of the same job.
04 — Skills
Every skill is linked to a project where I used it in production.
System design, technology decisions and technical ownership.
Vue, GraphQL and PostgreSQL working together.
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
Roles at EvoSys — and what I was responsible for in each.
06 — Education
Basic vocational training as a painter and decorator at Kilchherr in Thun.
After basic training, several years working in the painting trade.
Three-year IT programme for career changers, completed in summer 2024. Includes an integrated practical component: internship at EvoSys from January 2022 to December 2023.
One semester at vocational baccalaureate (Berufsmatura) level in mathematics, German and economics; followed by admission to the bachelor’s programme.
Part-time computer science degree focused on software engineering, architecture and information systems.
07 — Contact
I am looking for a position where I can take responsibility for systems and teams as a lead engineer or software architect. Ideally where reliability, data and real-world workflows meet.
Direct and uncomplicated — email is the fastest way.
Location: Switzerland