Selected work
Engineering experience that informs how we deliver.
Some of the work shown here predates the company and was delivered under prior professional or contract engagements. We describe the engineering honestly without claiming ownership of organizations, products or outcomes that were not ours.
The challenge
The work required more than adding features. Access windows had to reflect property policy and time zones, room and lock relationships had to be explicit, external APIs had to be reconciled safely, and failures had to become visible to staff before they became guest incidents.
Engineering focus
Designed access-code workflows around authoritative system data instead of brittle custom-field dependencies.
Implemented room-to-lock mapping and multi-access-point handling for real property configurations.
Worked on early check-in, late checkout and property-specific access windows.
Improved operational visibility, failure handling and synchronization across external services.
What it reinforced
The engagement shaped how we think about operational software: the hard part is rarely the interface. It is creating dependable behavior across real people, external systems and physical-world consequences.
Technology context
This work predates the company and was delivered under an individual contract engagement. The client is intentionally not named without publication approval.
The challenge
Financial systems carry strict requirements around data integrity, controlled change and failure handling. Shortcuts that look efficient during development become expensive when the software becomes critical infrastructure.
Engineering focus
Backend services using Java and Spring Boot in a microservices architecture.
Enterprise API design and integration across internal systems.
Work around SWIFT-related banking flows and internal applications.
Production-oriented debugging and maintainability in regulated environments.
What it reinforced
That environment created a standard we carry into smaller engagements: architecture should make the next change safer, not merely make today's feature possible.
Technology context
This experience was gained in an employed engineering role and is presented as professional experience behind the company, not as work delivered by the company itself.
The challenge
Early products need rapid iteration, but they also need clear boundaries around data, business rules and integrations so growth does not turn every new feature into a rewrite.
Engineering focus
Full-stack product development with Next.js, TypeScript and Node.js.
Mobile and rapid application delivery with Flutter and FlutterFlow.
Backend and data workflows with Firebase, Supabase and PostgreSQL.
AI-assisted engineering used as an accelerator while retaining human architectural judgment.
What it reinforced
This breadth lets us choose tools around the problem rather than forcing every engagement into one preferred stack.
Technology context
This section combines personal and professional engineering experience. Specific organizations and products are not attributed where publication permission has not been confirmed.
Your problem will be different. The engineering discipline should not be.
Tell us where the operation is breaking down. We’ll start there.
Start a conversation