My strongest work is not a gallery of visual variants. It is the engineering story behind Booking Admin, Booking App, FinFlow, InvoiceLab, and PromptFlow: control planes, runtimes, workflow-heavy tools, and AI-enabled products that still behave like software engineering.
I build product systems where the operational model is explicit. The strongest pattern in my work is separating customer runtime from operator authority when that separation improves safety, clarity, and release discipline.
Booking Admin and Booking App are the clearest proof of that thinking. FinFlow, InvoiceLab, and PromptFlow expand the story into finance, document workflows, and AI-era tooling without losing the engineering discipline underneath.
The through line is consistent: workflow depth, typed contracts, hosted verification, and documentation that helps people operate the system instead of decorating it.
The shortlist that currently carries the public portfolio story.
Internal control-plane platform for tenant configuration, release state, runtime inventory, and deploy promotion. This is the strongest proof of systems ownership because it treats operator authority as a first-class product surface.
Customer-facing runtime kept intentionally separate from the control plane. It shows product UX, hosted-lane delivery, same-origin manifest handling, and why the Booking split is an architectural strength instead of a documentation trick.
Cross-platform personal finance app with sync-heavy flows, assistant orchestration, and cloud-backed state. It reads like a real product because the core value is in workflow continuity, not a polished screenshot alone.
German invoice authoring workspace with Chromium PDF rendering and EN 16931 export. The engineering signal comes from document correctness, shared contracts, and a workflow that combines UI, render service, and compliance outputs.
Prompt engineering product surface with web, API, and mobile layers, evaluation workflows, and multi-model tooling. It earns a place in the shortlist because the AI value is carried by product architecture, not by novelty alone.
The same delivery pattern keeps showing up across the strongest work.
Open to roles that care about product depth, systems thinking, and clean operational boundaries.
The best fit is work where product, architecture, and operational clarity all matter. If the team values control-plane thinking, workflow depth, and systems that can actually be operated, that is the right conversation.