The right stack
for your
product.

Backend + Infrastructure.
Systems built to outlast the contract.

At Uappi, I rebuilt a feature that was timing out. Changed the data model, optimized the query, deployed the fix. Response time went from 10 seconds to 300ms — 10× the performance target. That's not luck. That's knowing when to redesign instead of patching. Now at Grupo Leveros, I work full-cycle: I design the API contract, build the microservice, write the Kubernetes manifest, and set up the CI/CD pipeline. That combination is rare. Most engineers hand off to ops. I own the entire delivery pipeline.

Small teams move fast because they have clarity, not because they skip decisions. I work with product and design from day one — not to approve specs, but to shape the API and data model so the system scales without rewrites. When you own both backend and infrastructure, you make better bets on architecture early. That saves months later.