Full-stack developer · Argentina (UTC-3)

Reliable data collection and automation, built to keep running.

I build scrapers, data pipelines and the systems around them: job queues, retries, recovery after failures and monitoring. I work async, with clear written updates.

what-i-build
collect
web sources · APIs · browsers
queue
Redis job queues, split by type
recover
retries · resume after failure
watch
monitoring · alerts
ship
API + web app
stackTypeScript · Node.js · React · Next.js · PostgreSQL · Prisma · Python · FastAPI · Playwright · Redis
Data source modules
38
Automated tests
~1,700
Built solo
~3 months
Per report
3–4 min

From the case study below. Report time measured on the first 20 reports.

01 / Case study

A due diligence report platform, built solo

A web platform that produces due diligence reports on people and companies. It collects data from 38 source modules in parallel and assembles the results into one report. The client uses it in production, internally. I built the backend, the API and the web app on my own in about three months.

Simplified. Source names are left out for confidentiality.
Isolation

Redis queues are split by type of source, each with its own worker, so a heavy module doesn't hold up the light ones. A dispatcher shares capacity fairly between accounts.

Testing

About 1,700 automated tests, and CI runs on every pull request.

Delivery

An API and a web app in React and TypeScript, used internally by the client in production.

role
Sole developer (backend, API, front end)
sources
38 modules: 21 for people, 17 for companies
queues
Redis, separate queues and workers by type of source
scheduling
Global cap on concurrent reports, fair turns per account
backend
Python (RQ workers), FastAPI, Playwright, Redis
database
MySQL, private, not exposed to the internet
front end
React, TypeScript
quality
~1,700 automated tests · CI on every pull request
timeline
~3 months
report time
~3–4 minutes (first 20 reports)
status
In production, used internally by the client
sources used
Public and third-party web sources

Client and data sources anonymized.

02 / Personal projects

Two things I built for myself

dedudas-app

A debt management app. Log what you owe across credit cards, Mercado Pago and informal debts, then track purchases, installments, due dates and totals for each creditor.

  • React
  • TypeScript
  • Node.js
  • Express
  • PostgreSQL
  • Prisma
  • Zod
  • TanStack Query
  • JWT

Turnealo

An appointment-booking SaaS for any business that runs on appointments. Clients book on their own, each professional has their own agenda and services, and each business gets its own page.

  • Next.js
  • React
  • TypeScript
  • Prisma
  • Supabase
  • Zod
  • Web Push

03 / How I work

Start small, in writing

  1. 01

    You describe the problem by email.

    Tell me what data you need, where it comes from and how often. A few paragraphs is enough.

  2. 02

    We agree on a small fixed-scope pilot.

    One clear deliverable, scope agreed in writing before I start, so you can judge the work before committing to more.

  3. 03

    I work async and report every week, in writing.

    Each week you get a written update on what's done, and we agree on what comes next. If something looks wrong or missing in between, write to me and I'll deal with it.

  4. 04

    Optional: an ongoing retainer.

    Websites and data sources change, and scrapers break when they do. On a monthly retainer I keep the system running and fix what breaks, and you get a written report of the support each month.

04 / Contact

Have a data collection or automation problem?

Send me a short description and I'll reply within one business day with questions or a pilot proposal.