About
About
The path
Before moving into formal software roles, I had already been building software through academic and independent projects. My formal career began as a Senior Developer at Softsimphony, building a biometric access-control system in C# where the software decided whether a physical door opened. After a period in networking and infrastructure at Medrent, I worked on enterprise Java systems at MOPEGA TI, including SOAP and XML services for a production integration between public-sector entities. At Cheil México / Samsung, as IT Manager / Lead Developer, my scope expanded beyond implementation into formal team leadership and cross-functional technical delivery, while I remained hands-on across commerce, logistics, payments and enterprise integrations. Today, as a Backend Developer at Corebiz / VML, I work on Adobe Commerce and VTEX, loyalty integrations and payment architecture.
The problems
The common thread is systems where a mistake is expensive: a decision with a physical side effect, data crossing between systems that were not designed together, a payment that must never run twice. The scope has grown from one system, to integrations between systems, to the guarantees a payment flow has to keep.
The approach
I start from constraints and failure modes rather than features: what happens on a retry, under concurrency, or when a dependency fails halfway. I prefer a decision that can be explained and defended to a number that cannot.