Skip to content

Product Engineer · Software Architect

From idea to product. And beyond.

I build and modernise digital products – from the first idea through architecture and engineering to reliable operations, combining product thinking with technical ownership.

What it is about

Good software does not start with code, but with a clear understanding of the problem. That is why I look at people, processes and goals first – and only then at technology.

  • Understand

    Clarify the domain, users and constraints before solutions take shape.

  • Decide

    Make trade-offs visible and deliberately choose what really matters now.

  • Deliver

    Build hands-on, ship and keep evolving the product in production.

01 · Product Lifecycle

Ownership across the entire product lifecycle.

I can step in wherever the product currently is – at the first prototype, an architecture decision, in the middle of a modernisation or in live operations.

  1. Prototype

    Make ideas tangible and test assumptions early.

    POCs · Prototypes · Feasibility

  2. Build

    Turn a validated concept into a robust product.

    Architecture · Frontend · Backend · Delivery

  3. Improve

    Reduce technical bottlenecks where they slow delivery down.

    Reviews · Refactoring · Modernisation

  4. Grow

    Add new capabilities without making the system more fragile.

    Features · Automation · Extensibility

  5. Maintain

    Keep production software stable, secure and evolvable.

    Operations · Security · Updates

02 · Selected Work

Real products. Real technical ownership.

The cases are not primarily about technologies, but about which problems were solved, which decisions were made and which systems were evolved in production.

Federal / Domain applicationCase 01

ELO Shot Count Reporting

Problem
Manual workflows and differing organisational logic had to be merged into one reliable digital process.
Ownership
Concept, architecture, full-stack development and production operations.
Solution
A domain application with roles, reporting, exports and clear domain logic.
Outcome
Ein produktiv betriebenes System, das fachliche Sonderfälle nachvollziehbar abbildet, erweiterbar bleibt und zusätzliche Security- und Betriebsanforderungen schrittweise aufnehmen kann.
  • Angular
  • NestJS
  • Nx
  • MySQL
Public SectorCase 02

SIS Portal

Problem
SIS brings the FSO's surveys, data validation and metadata together on one platform. Its grown frontend had to be modernised without disrupting ongoing statistics production.
Ownership
Frontend architecture and technical modernisation in a large agile programme with several teams working in parallel.
Solution
Incremental Angular migration including SSR, a Storybook-based design system, accessibility in the definition of done and deployment on OpenShift.
Outcome
Eine modernisierte und klarer strukturierte Frontend-Plattform mit besserer Erweiterbarkeit und konsistenteren technischen Leitplanken für das Team.
  • Angular
  • SSR
  • Storybook
  • Design System
  • Accessibility
  • OpenShift
Product / SaaSCase 03

MovIT

Problem
Operational processes needed to become simpler, more mobile and more consistent.
Ownership
Product development, UX concept and technical delivery.
Solution
A digital product for daily operations with clear, simple usage.
Outcome
Ein eigenständiges Produkt, bei dem Produktentscheidungen und Engineering eng miteinander verbunden bleiben.
  • Angular
  • Ionic
  • Node.js
OperationsCase 04

ALCO Infra

Problem
Inventory and infrastructure data needed to be accessible and editable directly on site.
Ownership
Frontend development and product concept.
Solution
Mobile inventory management with a clear view of stock and locations.
Outcome
Weniger Medienbrüche und eine klarere Arbeitsoberfläche für operative Aufgaben vor Ort.
  • Angular
  • iPad
  • Product Design

03 · Working Model

In which situation can I help?

What matters is not the method, but where the technical uncertainty or bottleneck currently lies.

AI accelerates the work. Engineering carries the responsibility.

Automation can speed up analysis, prototyping and delivery. Architecture, security, quality and trade-offs remain deliberate engineering decisions.

New product

From an idea to something real users can test.

Translate domain assumptions into a sensible scope and decide early what only needs validating and what must already be production-ready.

  • Prototype / MVP
  • Technical concept
  • Production-ready architecture
Existing product

Modernise without forcing a big-bang rewrite.

Identify technical bottlenecks, set guardrails and slice modernisation so ongoing product development stays possible.

  • Architecture review
  • Migration & refactoring
  • Prioritising technical debt
Engineering team

Additional technical ownership when it is really needed.

Drive architecture decisions, deliver critical topics hands-on and transfer knowledge so the team can continue independently.

  • Architecture & POCs
  • Hands-on engineering
  • Knowledge transfer

04 · Expertise

Technical breadth – applied with focus.

Technologies are tools. What matters is how product decisions, architecture and delivery work together.

Product Engineering

From problem and requirements to working, production-grade products.

Scope · MVP · Workflows · Product Decisions

Software Architecture

Architecture decisions, technical guardrails and systems that can keep evolving.

Boundaries · APIs · Standards · Trade-offs

Full Stack Engineering

Connecting frontend, backend, integration and delivery where the product needs it.

Angular · TypeScript · Node · SQL · CI/CD

Modernisation

Modernising legacy systems step by step, without unnecessary big-bang rewrites.

Migration · Refactoring · SSR · Platform Evolution

05 · About

Technology interests me. Products even more.

I am a product engineer and software architect with more than ten years of experience building and modernising digital products. I am especially drawn to situations where domain requirements, product decisions and technical architecture all have to be considered at once.

I like working hands-on and close to the team: not just documenting architecture decisions but delivering them, making real trade-offs visible and building solutions that hold up well after the release.

“Good architecture shows in how confidently a team can make the next change.”
Role
Product Engineer · Software Architect
Location
Zurich, Switzerland
Way of working
Hands-on, pragmatic, product-oriented
Context
Enterprise · Public Sector · Product

A product, a system or a technical problem that needs to move forward?

Whether it is a new product idea, a modernisation or additional architecture and engineering ownership: a short conversation is usually enough to see whether I can help.