Selected work

The work, and the thinking behind it.

Three examples of how I approach customer needs, technical decisions, and delivery. Each distinguishes my contribution, the project’s current state, and the evidence available.

01 / Enterprise delivery

Technical continuity, from client requirements to release.

LUXURY & FASHIONProduction delivery
Enterprise commerce.
  1. 01Requirements
  2. 02Solution & build
  3. 03UAT & release
Customer-facing engineering
My role
Software Engineering & Technical Delivery
Context
Global Luxury & Fashion Brand (Anonymized)
Project state
Production delivery

The problem

Modernization and feature extension of a digital commerce platform for a global luxury brand, requiring coordination across distributed teams and alignment with evolving commercial requirements.

The outcome

Delivered validated platform enhancements aligned with client requirements, with a documented implementation approach and support through UAT, production release, and hypercare.

My contribution

  1. 01

    Customer Clarification

    Directly interfaced with client domain leads in English to clarify operational requirements and business constraints.

  2. 02

    Technical Solution & LLD

    Authored low-level design documentation translating business requirements into the technical solution and implementation approach.

  3. 03

    Implementation

    Implemented the required backend and technical changes, collaborating with the wider delivery team across frontend, UX/UI, QA and project management.

  4. 04

    Test Planning & UAT

    Defined structured test scenarios, collaborated on cross-functional validation, and supported client business users through UAT.

  5. 05

    Production Release & Hypercare

    Supported the production release and post-release hypercare, helping validate stability and address issues during the initial rollout.

Technical Solution DesignLLDClient Communication (EN)UAT SupportBackend & SystemsProduction Hypercare
Explore delivery documentation
02 / Product discovery & build

A clearer path from hotel enquiry to follow-up.

HOSPITALITY OPERATIONSWorking pilot
Koordinato.
  1. 01Enquiry
  2. 02Quote
  3. 03Follow-up
Discovery · AI · Product engineering
My role
Product Engineering & Domain Discovery
Context
Independent Hotels & Hospitality Operators
Project state
Working pilot

The problem

Independent hotels receive direct requests across email, WhatsApp, and forms. Quotes and follow-ups can remain untracked when teams are busy, creating operational friction and recoverable opportunities that are easy to miss.

The outcome

Built a working pilot and a focused first-flow model for validation with hospitality operators.

My contribution

  1. 01

    Domain Discovery

    Used hospitality experience and operator conversations to map the direct-request flow: intake, missing information, quotes, follow-up, and team handoff.

  2. 02

    Solution Design

    Designed an AI-assisted operating layer above existing channels that can prepare replies, quotes, and follow-ups inside hotel-approved rules while escalating cases that need human judgment.

  3. 03

    Full-Stack Build

    Built and iterated the working pilot, product flows, data model, and operator-facing experience.

  4. 04

    Focus Correction

    Narrowed the product around a concrete first flow — direct requests, unconfirmed quotes, and follow-ups — rather than trying to automate the whole hotel at once.

Domain DiscoveryAI-Assisted WorkflowsProduct EngineeringBusiness Process ModelingUser Validation0-to-1 Execution
Visit the product
03 / System design & engineering

Physical touchpoints. Durable digital memories.

PHYSICAL-TO-DIGITAL SYSTEMSWorking product
Connecting Beyond.
  1. 01Activation
  2. 02Ownership
  3. 03Content access
Architecture · Data · Product engineering
My role
Co-Founder & Software Engineer
Context
Digital Heritage & Physical-to-Digital Experiences
Project state
Working product

The problem

Connecting physical media and locations to durable digital memory experiences requires separating physical distribution, license activation, user ownership, and digital-content linking while keeping state transitions safe and traceable.

The outcome

Produced a working product system and a public technical disclosure that makes one of its core physical-to-digital mechanisms inspectable.

My contribution

  1. 01

    System Modeling

    Co-designed relational data and lifecycle models separating physical Memory Links, digital licenses, ownership, and content relationships.

  2. 02

    Activation & Claiming

    Designed intermediary activation, intended-owner association, authenticated claim flows, and dynamic state resolution.

  3. 03

    Integrity & Security

    Documented idempotent creation, race-safe claiming, authentication and authorization boundaries, and security controls.

  4. 04

    Public Technical Disclosure

    Authored a dated prior-art specification containing architecture, API surface, state transitions, and implementation excerpts.

System ArchitectureRelational Data ModelingLifecycle DesignConcurrency & IntegrityAuth BoundariesAPI Design
Visit the productRead the public architecture
The next conversation

Good work starts with a real problem.

Looking for an engineer who can work directly with customers and carry the solution into delivery? Let’s talk.