01
Backend Systems
APIs, workers and services designed to stay correct when the happy path is no longer the common path.
- TypeScript
- Node.js
- Python
- REST APIs
- Distributed systems
Currently building @ Loopa Finance
I build systems that turn complex problems into reliable products.
Software Engineer focused on backend systems, cloud infrastructure and AI-powered products.
Based in Buenos Aires, Argentina.
About
I’m a Software Engineer from Buenos Aires working across backend engineering, cloud infrastructure, automation and applied AI.
I enjoy designing systems, understanding how they fail, and turning ambiguous product problems into software that can actually operate reliably.
00
Years shipping
00
Live products
2021
At Loopa since
01 / Origin
Buenos Aires
02 / Craft
Backend & infrastructure
03 / Focus
Applied AI
04 / Now
Loopa Finance
What I work on
01
APIs, workers and services designed to stay correct when the happy path is no longer the common path.
02
AWS systems with as few moving parts as possible — and the ones that remain are observable.
03
Models placed behind real workflows: retrieval, embeddings, tools and evaluation — not demos.
04
Turning ambiguous product problems into software a team can operate, debug and improve.
Experience
Aug 2021 — Present
Current
Loopa Finance · Remote
Building backend infrastructure, AI systems and internal products for a technology-driven litigation finance company. Work spans legal data pipelines, RAG and document intelligence, AWS, automation, and the platforms the team actually operates on. Selected for the AWS CTO Fellowship LATAM.
Jan 2021 — Oct 2021
Accenture · Buenos Aires
Intensive professional program focused on data analysis and machine learning. Worked with Python, pandas, NumPy and Spark, SQL / MySQL, Hadoop, and Google Cloud Platform for managing and scaling projects.
Jan 2020 — Jan 2021
Pipet · Buenos Aires
Contractor on a web and mobile product. Built interfaces and services with React and Node.js, using Firebase for realtime data and HTML, CSS and JavaScript for the client.
Selected work
Project 01
A document intelligence platform that transforms unstructured legal information into searchable, AI-ready knowledge.
Architecture
Project 02
Systems for collecting, normalizing and processing large-scale legal data across multiple jurisdictions.
Architecture
Project 03
Applied AI systems that assist users with document understanding, extraction, classification and decision-support workflows.
Architecture
Live product 04
A personal finance product for accounts, credit cards, installments, recurring payments and monthly projections — with an AI assistant on top.
guitaapp.comArchitecture
Live product 05
A Formula 1 prediction platform where people pick race results, create private championships and compete for points across GP, sprint and qualifying.
f1prode.comArchitecture
Engineering principles
01
The system you can explain at 2am is the one that survives.
02
Users do not experience your architecture. They experience whether it works.
03
Latency, cost, failure domains and the shape of the data come before the diagram.
04
A model is a component. The product is the workflow around it.
Writing
Future technical writing. These are titles I intend to publish — not articles that already exist.
Designing reliable asynchronous workers
Queues, visibility timeouts, and the difference between retryable and poison work.
What I learned building RAG systems
Chunking, retrieval quality, and why the index is more important than the prompt.
Queues, retries and idempotency
How to make work safe to run twice — and expensive to run wrong.
Building AI features that survive production
Evaluation, fallbacks, and keeping a model from becoming a single point of failure.
When I’m not building software