I build software,
products & systems.
Full-stack engineer focused on backend systems.
AI-native development. Products built for real-world impact.
Selected work · 01—03
A focused look at the products that best represent how I think about engineering, product and delivery.
From booking a court to building a competitive community.
A connected platform for players and clubs: reservations, matches, rankings, leagues and operations designed as one product system.
LIVE PRODUCT
PadelPoint
Discovery, identity and circular fashion in one social experience.
A dark social-fashion marketplace built around discovery, closets, matching, offers and AI-assisted publishing flows.
LIVE PRODUCT
CirculAR
A configurable storefront that turns WhatsApp into checkout.
A multi-tenant commerce platform with isolated stores, dynamic branding, catalog management and a lightweight WhatsApp purchase flow.
LIVE PRODUCT
Volta Store
03 / SYSTEMS · LABS
I use AI, automation and repo-native workflows as part of the engineering system — not as a shortcut around engineering.
A repo-native operating system for coding agents: scoped context, task-specific skills, deterministic preflight, quality gates and durable handoffs. The goal is simple — make AI-assisted delivery repeatable and reviewable.
CONTEXT
repo rules + release state
AGENT
task-specific skills
BUILD
scoped implementation
QUALITY
deterministic gates
SHIP
validated handoff
An auditable research-to-product pipeline that separates evidence from interpretation, versions product context and offers, turns them into blueprints, and prepares generation for explicit QA instead of one-shot prompting.
RESEARCH
discovery + evidence
OFFER
versioned product context
BLUEPRINT
structured deliverables
GENERATE
provider-driven content
QA
claims + consistency
04 / HOW I BUILD
The stack changes. The operating principles should not.
Start from the system, not the screen.
Business rules, contracts, data and failure modes come first. UI should sit on top of a system that can explain itself.
Useful beats impressive.
I care about the path from intent to outcome: what the user is trying to do, what gets in the way and what the software should remove.
AI belongs inside the workflow.
Agents, skills and automation are most valuable when they inherit context, respect constraints and pass the same quality gates as any other change.
Build. Validate. Ship. Learn.
Small feedback loops beat long speculative cycles. I prefer observable increments, explicit validation and a clear handoff to the next decision.
Systems should be understandable, testable and useful before they are clever.
ROSARIO · ARGENTINA · 202605 / ABOUT
Software engineer based in Rosario, Argentina. My background crosses electronics, programming and systems engineering, which shaped how I approach products: understand the system, simplify the path and ship something real.
Backend-first by instinct.
Product-minded by necessity.
AI-native by practice.
A technical foundation for understanding systems from the physical layer up.
Turning that systems mindset into software, automation and backend engineering.
Connecting architecture, product decisions and delivery into one way of working.
06 / NOW · AUG 2026
A small snapshot of the products, systems and ideas getting most of my attention today.
Closing the loop from discovery to closets, matching, offers and exchange.
Deepening match flows, competitive systems and the player-to-club product experience.
Research, evidence, offers, blueprints, generation and explicit QA as one auditable pipeline.
Repo context, agents, skills, deterministic checks and repeatable delivery workflows.
07 / NOTES
This section is ready for the posts I publish next. For now, it shows the ideas I want to write about without pretending drafts are published work.
Context, skills, quality gates and handoffs are the part I want to write about first.
States, failures, feedback and handoffs are where a product starts feeling complete.
The architecture that matters is the one that keeps the next change understandable and safe to ship.
