11+ years engineering backend systems that need to remain reliable under pressure — and building modern interfaces that make complex products feel simple.
PHP / Laravel · Vue.js / React · Software Architecture
I work across the full application stack, with a strong focus on backend architecture, business rules and maintainable code.
My core experience is with PHP and Laravel, combined with modern frontend development using Vue.js and React. I enjoy working on systems where architecture, performance and long-term maintainability matter.
From modern applications to legacy codebases, my goal is the same: understand the system, reduce unnecessary complexity and deliver software that can evolve.
A condensed view of systems, products and engineering environments I've worked on.
Engineering and scaling back-office systems for franchise networks, WMS workflows and high-throughput point-of-sale operations.
Backend architecture for payment intermediation, business rules and RESTful APIs supporting financial operations.
Fullstack engineering for a large-scale Latin American logistics platform, working across application logic, APIs and user-facing workflows.
E-commerce integrations, SaaS banner engines, custom platforms and application analysis across different business domains.
Independent products and software projects built from architecture and backend systems to interfaces, integrations and deployment.
A software house focused on custom software, SaaS products and API integrations. The platform communicates a developer-first approach combining technology, product thinking and clean engineering.
A scheduling SaaS for service professionals and appointment-based businesses. Customers can book online while businesses manage professionals, services, availability, appointments and finances from a centralized platform.
A platform for tracking movies and TV series. Users can organize their watchlist, track episodes, monitor season progress and maintain a complete viewing history through a focused dark interface.
Code should remain understandable months after it was written.
Business rules deserve structure, boundaries and explicit responsibilities.
Use the simplest solution capable of solving the actual problem.
Legacy systems can evolve incrementally without requiring a complete rewrite.
Open to engineering opportunities, challenging products and teams that care about quality software.