Portfolio
Nine systems across healthcare, industrial IoT, ticketing, retail and marketplaces. Each appears here exactly once, with the decision that made it work and what that decision cost.
2025
Active developmentA product studio built as one monorepo — shared auth, config, UI, and utilities under six apps, so a new product starts with a working login instead of an empty folder.
Outcome
The second product shipped without rewriting the first product’s foundation.
Role
Founder & Principal Engineer
2026
ProductionCart, checkout, CMS, and loyalty flows for a production retail app serving Germany and Austria across the mobile and API layers.
Outcome
Market rules stayed in shared APIs rather than being duplicated per country in the app, which made releases safer to trace.
Role
Senior Software Engineer
2025
ProductionA ticketing and event-management platform across Rails, React, and Flutter — organizer dashboards, ticket shops, and mobile entry on one backend model.
Outcome
Pricing phases, discounts, and scanner validation followed one set of rules instead of three client-side copies.
Stratos One · 2025
Released v1.0.1Care coordination where families and professional carers log the same person’s day into one typed record — 6 categories, 65 subtypes, and a severity scale that survives an audit.
Outcome
A handover between a family member and an agency carer no longer loses information — every event carries a category, a severity, and an author.
Role
Founder & Principal Engineer
Stratos One · 2025
Released v1.2.1A marketplace for rentable storage space in Germany — map discovery, a listing wizard, and Stripe subscriptions settled in Supabase Edge Functions rather than on the phone.
Outcome
The mobile client never holds a payment secret, and the Android permission set was cut to only what the product can justify to a reviewer.
Role
Founder & Principal Engineer
Kewazo · 2024
ProductionReplaced 30-second polling with live telemetry operators could trust on a construction site — across the ingest, storage, and dashboard layers.
Outcome
Operators acted on the dashboard instead of walking to the machine, and could see when a reading was stale instead of trusting it silently.
2024
ProductionTurned spreadsheet-based clinical analysis into a reproducible web workflow that produced audit-ready reports in minutes instead of a day.
Outcome
Every analysis stored its dataset version, parameters, and pipeline version — so a clinician could regenerate a result and defend it later.
2023
ProductionModelled complex relationship graphs and consent states for a production dating product built around polyamorous relationships.
Outcome
Partnered users, group consent, and matching rules fit one structure instead of a pile of special cases.
2023
Personal projectA tower-defence strategy game in Unity — and an exercise in updating hundreds of entities every frame without dropping below 60fps on mid-range hardware.
Outcome
Late-wave simulation stayed smooth once entity pooling and a spatial hash removed the GC churn from the hottest loops.
9 projects