Engineering profile

I build products that scale while keeping database load and AWS costs under control.

I am a Product Engineer with a backend and cloud focus. I work across the interface, application code and infrastructure, especially when product decisions create database pressure or operational risk. I design the system, implement the difficult parts and support it in production.

13M+people served by systems I help run

1.5M/hsustained notification capacity

700+ GBPostgreSQL table maintained online

AWS ProSolutions Architect certified

ProductNext.js, React, tRPC

ProcessingQueues, workers, retries

DataPostgreSQL, Redis, S3

OperationsAWS, CI/CD, incidents

Production results

Four changes with measurable outcomes

Processing54 hours to 41 minutes

Campaign processing after replacing OFFSET scans and changing how batches and links are handled.

MemoryAbout 80% to 4%

Worker resource use after switching to keyset reads, Redis cursors and smaller batches.

Database700+ GB kept online

The product stayed online during bloat analysis, pg_repack and invalid-index recovery.

Cloud37% lower AWS cost

AWS architecture and resource changes for public transport, with 99.9% availability maintained.

Technology

Tools used across product, backend and cloud work

Frontend and product

TypeScriptJavaScriptReactNext.jsTailwind CSSReact Hook FormZodtRPCRadix UIshadcn/uiSSR and CSR debugging

Backend and APIs

Node.jsNestJSExpressRESTGraphQLPythonFlaskQueuesSchedulersMulti-tenant SaaS

Databases and analytics

PostgreSQLSupabaseRedisUpstashMongoDBFirebaseMySQLTinybirdClickHouseAthenaParquet

AWS and delivery

S3SQSSESWAFCloudWatchCloudTrailGlueLake FormationLambdaCloudFormationIAMSNSEC2EBSVercelGitHub ActionsCI/CDLinux

Production AI

MCPAI SDKOpenAIClaudeTool callingStructured outputsPersistent contextAI agentsOllamaOpenHands

Quality and operations

PlaywrightVitestReact Testing LibrarypytestObservabilityIncident responseCode reviewOnline database maintenance

Profile sections

The rest of the engineering profile

Engineering notes

Two decisions worth writing down

AWS migration assessmentWhen the right Graviton recommendation is "not yet"Offline EBS inspection showed that the host needed to be separated before changing CPU architecture.Agents and remote executionAutonomous coding with Ralphie, OpenHands and OllamaRepository memory, bounded run drivers and 48 tests used for external verification.

Availability

I am open to senior Product Engineer roles.

The best fit includes responsibility for backend systems, product architecture, data or AWS. I work remotely from Argentina in English or Spanish.