I design and build resilient software across web, cloud, mobile, and Windows — connecting strong engineering decisions with interfaces real people can trust.
Years of experience
Platforms — web · cloud · mobile · Windows
Selected systems shipped
Clouds — Azure & GCP
Scalable SaaS & enterprise web platforms built on deliberate trade-offs.
Secure APIs, data systems, and workflow automation that eliminate manual toil.
Resilient deployment patterns across Azure & GCP with zero-trust principles.
Accessible UX for everyday humans. Clarity over cleverness.
From health tracking to scheduling and operations, I work on the layers most teams avoid: the data model, the workflows, the edge cases, and the interface that makes it all feel obvious.
A low-friction medical tracking experience shaped for older adults and less technical users. Clear navigation, useful defaults, and reduced cognitive load.
Web · Accessibility-first UX · Sensible defaults
A scheduling workflow that connects mentors, clients, Google Calendar, and Google Meet without turning coordination into a full-time job.
Google Calendar API · Google Meet · Workflow automation
Database-driven systems for shifts and duty allocation, designed around heavy roster data and the operational realities behind it.
SQL · Data modelling · Operations tooling
Performant .NET and WPF applications for business operations where reliability, local data processing, and predictable workflows matter.
.NET · WPF · Offline-first architecture
I start with the constraints, not the framework. Then I make the system understandable enough for a team to own and the product simple enough for a person to trust.
Map users, workflows, data boundaries, failure modes, latency needs, and the cost of being wrong before writing a single line of code.
Choose boundaries, storage, APIs, and deployment patterns that leave room for growth without premature complexity or over-engineering.
Remove friction, communicate state clearly, and give people a predictable path through the work — even when the system underneath is highly complex.
Threats, permissions, secrets, validation, and operational visibility belong in the initial architecture — not in the last sprint.
Clean Architecture and domain thinking are useful only when they help a team reason about change and failure, not just to satisfy academic purity.
Software should work for people who are older, distracted, less technical, or using a smaller screen. That is not a niche; it is the baseline standard.
Strong code reviews, shared context, and better technical judgment turn individual output into durable, scalable team capability.
Owning architecture and delivery across web, cloud, mobile and Windows. Leading reviews, mentoring engineers, and turning ambiguous problems into shippable systems.
Shipped SaaS platforms, scheduling automation, data-heavy operations systems and offline-first desktop tools — including the four selected systems above.
Started by building real tools for real users — and never stopped measuring decisions by what they made easier for the person on the other side of the screen.
Tell me what you are building, where it hurts, and what "better" needs to measure. We can start with the architecture — not the sales pitch.