I didn’t start by writing code.
I started by soldering circuits, wiring sensors and trying to understand why things worked.
Over time I traded soldering irons for Kotlin, prototypes for financial products and small teams for platforms used by thousands of people. But the way I think never changed much: understand the system, find the real problem and build something that works when it matters.
Today I design and build digital products across engineering, architecture and product, mostly on mobile, and increasingly with applied AI.
From circuits to software that can’t fail.
I didn’t come to software the traditional way. I came out of curiosity.
Before writing my first app I built circuits, worked with sensors and made prototypes. That’s where I learned something that would end up defining my career: when you build real systems, details matter.
Over the next ten years that idea took me from Android to finance, then to global products, then to founding my own fintech and finally to working on architecture, platforms and artificial intelligence.
Before code, there were circuits.
At the Centro Nacional de las Artes I worked with electronic interfaces, robotics, sensors and prototypes.
That’s where I learned engineering before writing my first app: observe, experiment and understand what happens inside a system.
I found out I could build products.
At Areté Software I went from developing Android to leading teams. I built products for government and companies.
Writing good code was only part of the job: you also had to understand the people who were going to use it.
When a bug costs money.
I moved into finance, working on products for institutions like Banxico’s CoDi, Banco Famsa, Banco Sabadell and Banco Azteca.
I designed transfer security that shipped to production unchanged and took part in rebuilding banking products.
That’s where I understood that quality isn’t perfectionism: it’s responsibility.
I learned to work at global scale.
I worked on products for Disney and Prisma at Globant and then at Citi on Telcel’s RAM project.
Bigger teams, more complex systems and a new lesson:
Architecture is also a tool that lets people work together.
I wanted to build something of my own.
I founded RUUT, an investment fintech, and built its Android MVP from scratch.
But the important change wasn’t technical. I went from asking “how do we build this?” to asking “should we build it?”
I hired and led a team of more than ten engineers and the product reached tens of thousands of installs.
Being a founder changed for good how I understand engineering: code only matters if it solves the business.
Engineering, product and artificial intelligence.
I worked as a Senior Android Engineer for PayPal and then led engineering initiatives for Shell Energy.
In parallel I started exploring a question that now takes up a good part of my work:
What changes when an engineer stops using AI only to write code and starts using it to understand entire systems?
Since then I’ve built my own products and experimented with local LLMs, knowledge retrieval, automation and software development tools.
I don’t build software for its own sake.
Product before feature.
Before writing code I want to understand what problem we’re solving and for whom.
Architecture with a purpose.
Clean Architecture, modularization or any pattern are tools. If they add complexity without solving a problem, they aren’t good architecture.
Mobile is my specialty, not my limit.
Android is where I go deepest, but I think in whole systems: backend, product, design, infrastructure and business.
AI as a multiplier.
I don’t believe artificial intelligence replaces a good engineer’s judgment. I believe it can multiply it.
Ownership.
If something I built fails in production, it doesn’t stop being my problem because my ticket is closed.