Tech Lead & Software Architect — Switzerland

Software that works when it matters.

Since 2022 I have built production platforms for emergency response, planning and identity — from database to mobile app.

Years of experience
4+
Products
7
Web platforms
4
Mobile apps
2

02 — What I do

From system design to the last sync edge case.

I work where architecture and delivery belong together. Responsibility does not stop at the API boundary.

01

Architecture & tech lead

System design, technology selection, API and data modelling, authentication boundaries and code reviews. I make decisions that still hold after the next release.

02

Full-stack web

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.

03

Mobile & offline

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.

04

Operations & quality

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

Responsibility for the whole.

Technical decisions are only as good as the context in which they are made.

  1. 01

    The problem first, then the stack.

    I start with workflows, data and failure modes — not with frameworks. Technology follows from requirements; it is not the starting point.

  2. 02

    Make decisions visible.

    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.

  3. 03

    Reliability is not a feature.

    Offline sync, retries, conflicts and authentication boundaries are considered from the start — not added afterwards.

  4. 04

    Own the outcome.

    From the first migration to the code review: I take responsibility for the result, not only for my own part.

04 — Skills

What I actually use.

No percentage bars. Every skill is linked to a project where I used it in production.

Architecture & leadership

System design, technology decisions and technical ownership.

Full-stack web

From the Vue frontend through GraphQL to the database.

Mobile & offline

Flutter apps and synchronisation under real network conditions.

Platform & operations

Builds, deployments and the infrastructure behind them.

06 — Contact

Let's talk about the next role.

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.