Senior Product Engineer
From domain rules and API boundaries to deployment and release ownership — I ship systems that stay correct under real business load.
Hospitality SaaS with booking integrity, payments, multi-tenant delivery, and operational tooling. One person across product architecture, implementation, and infrastructure.
Flagship case study
A multi-tenant hospitality SaaS I design, build, deploy, and operate — protecting availability and revenue for operators who sell across direct and OTA channels.
Product Engineer / Full Stack Owner
I own the product architecture, guest booking flow, operations dashboard, backend API, deployment model, and the domain rules that prevent double-booking and pricing drift.
Visit aloja.casaProduction Architecture
Operators need a direct booking channel without losing availability consistency across Airbnb, Booking.com, VRBO, and on-site reservations.
Multiple hospitality brands run from one codebase with payments, OTA synchronization, and day-to-day operational tooling operators rely on.
Each decision exists because a business invariant had to hold in production — not because a framework was available.
Why: Operators cannot sell the same night twice across channels. The engine searches feasible night-by-night combinations, ranks results to reduce property switches, and respects occupancy, blocked dates, holds, and existing reservations.
Why: Payment confirmation arrives asynchronously. A temporary hold during checkout lets the system wait for webhooks without letting two guests reserve the same dates.
Why: Operators need explainable totals, not black-box quotes. Weekday base rates, date overrides, guest surcharges, early check-in, late check-out, and minimum price rules produce the same total in the UI and API.
Why: Forking per brand does not scale operationally. Hostname resolution delivers brand-specific behavior from one platform without duplicating the codebase.
Why: Operational users need scoped access, not a single admin gate. JWT sessions, refresh rotation, Redis-backed invalidation, two-factor authentication, and role-based access control protect internal workflows.
Why: Separate public and operations surfaces optimize for different users. Docker and Nginx route traffic to Next.js for SEO-sensitive guest flows and SolidJS for a dense operator calendar — each tuned for its job.
Why: The product has to run reliably without a separate ops team. I manage DNS, SSL, Linux servers, AWS SES email delivery, Route53 records, Lightsail hosting, and Amplify deploys — and own release troubleshooting when something breaks in production.
A custom booking domain model took longer than a reservation plugin, but made availability, pricing, and OTA rules explicit and testable.
JSON snapshots plus normalized booking rows add write complexity, but protect historical financial records while keeping availability queries efficient.
Two front-end apps increase deployment surface, but let each optimize for its user: conversion for guests, density and speed for operators.
Engineering highlights
Architectural choices, implementations, and operational responsibility for the flagship platform — not every project in the portfolio shares this depth.
Hostname-resolved brands from one codebase — each with its own domain, visual identity, and operational configuration.
Availability, holds, reservations, and OTA sync modeled as explicit invariants instead of ad hoc database flags.
MercadoPago integration with webhook-driven confirmation tied to hold sessions so inventory stays consistent.
Role-based access for operational users — scoped permissions across dashboard, calendar, and configuration workflows.
NestJS REST boundaries with shared TypeScript contracts so public booking, operations UI, and backend agree on domain models.
Multi-property calendar over years of booking data — grid virtualization, cache-window quantization, and fine-grained SolidJS updates for operator confidence at scale.
AWS SES, Route53, Lightsail, and Amplify — plus DNS, SSL, and Linux server operations when the product needs to stay online.
Containerized deployments with Nginx routing — repeatable releases across public and operations applications.
Short-lived booking holds, session state, and token invalidation — operational state that should not live in PostgreSQL.
Relational booking data with normalized rows for availability queries and snapshots for historical pricing integrity.
Rendering strategies chosen per surface — SEO and conversion for guest flows, virtualization and cache discipline for operator tools handling large datasets.
Release ownership and troubleshooting when deployments or integrations fail — monitoring through operational use, not passive dashboards.
Previous engineering work
Previously built and maintained a reusable React component library with Storybook, Chromatic, Rollup, and TypeScript. Although it is no longer part of the current production stack, it demonstrates experience designing reusable UI contracts, documenting component APIs, and maintaining shared frontend infrastructure.
Storybook made behavior inspectable — forms, layout, feedback, navigation, and data-display primitives with TypeScript-first contracts instead of hidden implementation details.
Rollup bundling and versioning let independent applications consume the same primitives without copying source files across repositories.
Chromatic supported review of interface changes before they spread across consumers — a workflow for keeping shared UI trustworthy as it evolved.
The library was private infrastructure for reducing duplicated UI decisions. It has since become outdated and is not used by the current aloja.casa production apps — but the engineering patterns remain relevant.
Production work
aloja.casa is the deepest engineering work. Other projects are smaller in scope — marketing sites and community platforms — and are presented at the depth they actually have.
Multi-tenant SaaS
These hospitality businesses run on the same platform — shared booking integrity, payments, availability control, and operations tooling, with hostname-resolved branding per tenant. They are not unrelated standalone builds.
Marketing MVP
Hospitality
Community
Engineering expertise
Grouped by what I am accountable for in production — not a technology bingo card.
Booking rules, pricing logic, multi-tenant behavior, workflow translation from business needs to system design.
Public booking surfaces and operations dashboards on aloja.casa — rendering strategies matched to guest conversion vs. operator density.
APIs, authentication, payments, relational data integrity, and integration boundaries between channels.
Deployment, DNS, SSL, container routing, email delivery, and release troubleshooting when production misbehaves.
Operational dashboards for occupancy, revenue, and cancellation behavior — connected to decisions operators make weekly.
Previously built a private React component library — Storybook documentation, Chromatic visual review, and Rollup packaging. Not part of the current aloja.casa production stack.