Software Engineer & Systems Builder Mexico · Working globally
I build complex systems
that work in the real world.
I’m an electronics engineer turned software engineer. I design distributed platforms, data pipelines, integrations and APIs that must operate reliably under real-world constraints. My research, Koba and Kopo, asks what such a system means before it runs.
Professional experience
A career across
systems and scales.
Most recent first, from enterprise billing at Oracle to merchant catalogs at Pinterest.
- PinterestSoftware EngineerMerchant catalogs & Shopify
- BluecoreInfrastructure teamCore event processing
- ZillowProduct Engineer, Home LoansLoan & lead flows
- BrightcoveStaff EngineerVideo distribution
- ValoreoSoftware ArchitectCommerce integration platform
- LyftSoftware EngineerSupport pipeline
- ReinvsolSenior Software DeveloperReal-time pricing platform
- OracleJava Developer → Senior Java DeveloperSubscriptions & billing
Selected systems
Systems over
technology lists.
The strongest work first: what the system needed to do, the constraints it lived under, and how it reached production.
Commerce integration platform
Designed a distributed, event-driven platform connecting Amazon, Mercado Libre, Shopify, Walmart and Liverpool with NetSuite.
Merchant catalogs & Shopify
Connected external commerce systems, backend services and merchant-facing experiences—from feed ingestion to operations.
Real-time pricing platform
Built horizontally scalable price ingestion and live distribution, while leading a multidisciplinary engineering team.
Subscriptions, billing & reconciliation
Built middleware spanning REST, XML, CSV and JMS integrations to improve the speed and accuracy of subscription operations.
Projects / Research
One meaning,
many projections.
What a system is once the framework, the transport and the vendor are taken away. Each line of work states what is proven and what is still a direction.
Systems from ordinary functions
Ordinary functions plus a contract, compiled into an execution plan. HTTP, WebSocket, Kafka and in-process calls are projections of the same operations.
Haskell on the go
A lazy, typed functional language hosted in Go: typed immutable Core, a call-by-need machine, and access only to what the host grants.
A decision or an accident?
A specification and implementations in Java, Python and TypeScript test which parts of the model are the model and which are Go.
Blog
The code,
release by release.
Entries that explain my research through its code, one concept per entry, each anchored to the release that realized it.
Describe, don't route
A walk through the release where the interface became a value of its own: the API described — routes, verbs, parameters, documentation — beside the functions, checked when described, and served by consuming the description. Then the abstractions underneath it: one plan compiled once, two interchangeable compilers, and a committed OpenAPI document that cannot drift. The polls service that runs through this series, as that release could express it; what the description finally fixed, and what it could not yet check.
The HTTP method follows the signature
A walk through the first release of what is now Koba: a small Go library built on two rules, an API is a value whose exported methods are endpoints, and the HTTP method follows the signature. The polls service that runs through this series, as that release could express it; what the code derives, what its tests record, and what it could not yet say.
A series about Koba
I have been working on Koba since 2021 and I will write its evolution here, one idea per entry, each anchored to the code that realized it. What it is, where it stands, what is coming, and where it began.
Ways I can help
Architecture to implementation.
Software to physical systems.
- Backend & distributed systems
- Data & commerce integrations
- Infrastructure & production
- System design & technical leadership
- Embedded & physical engineering
Have a system that’s difficult to make sense of?