— Product Engineer
Architecting products.
Great software is not the objective.
SELECTED WORK
Evidence of execution.
From architecture to business value.
EstampaMatch
The Opportunity
Sticker collecting is inherently social, but collection data is usually fragmented and manually managed. This makes useful exchanges difficult to discover.
The Product
A digital collection system that turns missing and duplicate stickers into structured, shareable data for discovery and exchange.
The System
02 / INDUSTRIAL SYSTEMS
Honeywell
Interfaces for complex physical systems.
Built frontend experiences for an automated warehouse platform used to monitor robots, inventory movement and warehouse configurations.
03 / COMMERCE + PAYMENTS
Front Gate Tickets
Live Nation / Ticketmaster
Engineering the path from ticket to event.
Contributed to frontend experiences across ticketing, merchandise, wristbands and checkout flows, integrating payment services including PayPal and Venmo alongside event insurance.
EXPERIENCE ACROSS
EXPERIENCE
Professional Experience.
Ford Motor Company
EOG Resources
Honeywell
Engineering at Scale
Years Engineering
Building production digital products
Production Systems
Built in complex enterprise environments
Industry Domains
From finance to industrial systems
Countries
Collaborating with international teams
HOW I BUILD
A systematic approach to
product creation.
Understand
Every system exists to serve a business objective. Code written without understanding the problem is technical debt from day one.
Architect
Architecture is about deliberate trade-offs. Designing systems around what must be robust, what should remain flexible, and what can stay simple.
Design
Experience is architecture. I design interfaces that feel inevitable, prioritizing clarity, performance, and aesthetic precision.
Build
Good architecture only matters if it survives implementation. Turning decisions into reliable software without losing sight of the product.
Ship
Deployment is a feature. Establishing reliable pipelines and ensuring the system is observable in production.
Learn
Data must inform iteration. Measuring what matters to validate assumptions and refine the product direction.
Scale
Good systems anticipate change without predicting everything. Scaling the technology in lockstep with business growth.
TECHNOLOGY
Product technology architecture.
Experience
Systems & Data
Platform & Product
Intelligence
Engineering
Philosophy.
07 Principles
Business Value First.
Technology exists to solve a problem. Writing code is expensive; maintaining it is even more expensive. Every technical decision must justify its cost through business outcomes.
Architecture With Purpose.
Complexity must earn its place. I avoid resume-driven development. The architecture should be as simple as possible, but no simpler.
Product Over Features.
A collection of features is not a product. A product is a cohesive system where every feature interacts intelligently with the others to serve the user's intent.
Simple Until Scale Demands More.
Do not overengineer on day one. Build cleanly decoupled boundaries so that when the system needs to scale, it can do so without a complete rewrite.
Experience Is Architecture.
The frontend is not decoration. It is the manifestation of the system's logic. Poorly architected data structures inevitably bleed into the user experience.
Build for Evolution.
Good systems anticipate change without predicting everything. Rigid architectures break; flexible ones adapt.
Ship, Measure, Improve.
Software creates value when it reaches users. Ship deliberately, observe how the product behaves, and let real usage inform what comes next.
Architecture Decisions
The Architect's Notebook.
BUSINESS CONTEXT
Software exists within
a business system.
BACKGROUND
The intersection of logic and value.
— ARCHITECTURE & ENGINEERING