Engineering close to the problem

From the real processto software that works.

I work alongside users and teams to understand the business, build the solution and integrate it into production. Software, cloud and AI applied to an outcome we can measure.

Córdoba, Argentina Business ↔ Engineering
LIVE / DELIVERY MAPSYSTEM ACTIVE
01
INPUTReal problem
FDEDISCOVER · BUILD · SHIP
05
OUTPUTMeasured impact
SOFTWAREbuild
INTEGRATIONconnect
PRODUCTIONoperate
ADOPTION
real value
01 / APPROACHTHE PROBLEM BEFORE THE STACK

Technology is not my starting point.The bottleneck is.

Code is part of the answer. First, we need to discover what slows people down, where information gets lost, which rules are undocumented and how we will know the intervention worked.

That is where an FDE works: at the boundary between business, data and engineering, accountable from the first question through adoption.

A

Understand the operation

Talk to the people doing the work and observe what actually happens.

B

Build with judgment

Choose the right solution, even when the answer does not require AI.

C

Prove the change

Compare against a baseline: time, cost, quality, risk and adoption.

02 / METHODFROM AMBIGUITY TO PRODUCTION

A short cycle.
End-to-end ownership.

Delivery does not end when a demo appears. It ends when the solution works in context, people can use it and the team has learned something reusable.

01

Observe

Understand the real process, the people, exceptions and constraints before proposing technology.

02

Focus

Turn ambiguity into a clear hypothesis, a baseline and an outcome we can test.

03

Build

Design and implement the smallest solution that addresses the problem’s most important risk.

04

Integrate

Connect data, APIs, identity and infrastructure without ignoring the existing environment.

05

Measure

Validate adoption, reliability, cost and speed; learn and turn the result into a reusable capability.

03 / CAPABILITIESBREADTH WITH DEPTH

Cross the layers
without losing the outcome.

Value does not come from collecting tools. It comes from connecting the ones required for an idea to survive contact with reality.

DISCOVERY

Product and business

Interviews, process mapping, requirements, prioritization, metrics and translation between technical and operational teams.

BUILD

Software and integrations

Backend, APIs, automation, data and complete applications with Go, JavaScript, Java, Python and Rust.

SHIP

Cloud and production

AWS, containers, Kubernetes, CI/CD, observability, IAM, networking and operable architecture decisions.

AUGMENT

Applied AI

Models, agents and automations introduced when they improve the system, with evaluation and human review.

04 / EXPERIENCEPROBLEMS, SYSTEMS AND LEARNING

Applied experience

The experience that matters happens between layers.

I have worked from functional support to backend development, automation and technical research. That combination makes it possible to see both the system and the people who depend on it.

01
Operations

From delivery notes and spreadsheets to a traceable system

I identified a digital transformation opportunity, worked with the people performing the job and built outward from the most critical processes through successive iterations.

02
Automation

Support that understands intent and context

I worked on automating support channels with classifiers, entities and intents before the rise of generative AI.

03
Research

Decide with evidence, not preference

I led research initiatives and MVPs to compare tools, frameworks and strategies through transparent, deterministic metrics.

Working principle

Fewer demos.
More production.

The best solution is not the flashiest one. It reduces friction, can be operated with confidence and leaves the team better prepared than before.

EXPLAINABLE DECISIONSHUMAN ADOPTIONMEASURABLE IMPACT