Skip to main content
Ezequiel Calonge

Ezequiel Calonge

Senior Software Engineer at NaranjaX

About

I'm a Senior Software Engineer at Nave NegociosNave Negocios, where I architect payment infrastructure processing $300B+ ARS monthly — direct integrations with VISA, Mastercard and AMEX, PCI-DSS certified, zero settlement delay. Focal developer on Kausanna, an AI-driven dispute resolution engine, and designer of SONQO, a fully serverless payment gateway on AWS.

Previously, I co-founded MuteadoMuteado (10k monthly views) and FLUX RecordsFLUX Records (100+ artists). You can reach me via email, on LinkedIn, on GitHub, or via my .

Featured

NaranjaX logo
NaranjaXSenior Engineer on payment rails — $300B+ ARS/month, PCI-DSS.
Nave Negocios logo
Nave NegociosFocal dev on Kausanna (AI disputes). Architect of SONQO (serverless gateway).
Muteado logo
MuteadoCo-founder + CTO. Real-time AI political intelligence, 10k monthly views.
FLUX Records logo
FLUX RecordsFounder. Serverless music distribution, 100+ artists, zero marketing spend.
TranscribeIA logo
TranscribeIAFounder + architect. Serverless AI transcription, SQS fanout for large files.
Your project could be here

Current

TranscribeIA

Founded and architected TranscribeIA, a platform that turns meetings, classes, interviews, podcasts, and conferences into editable transcripts with AI-generated executive summaries, action items, and speaker diarization up to 8 voices. 98% accuracy on clear audio across Spanish, English, and 90+ languages. Currently serving 50 users across a Free → Business tier ladder with custom vocabulary, API access, SSO, and DPA.

The hard architectural call: transcribe multi-hour recordings without leaving serverless. I designed an SQS fanout pipeline that splits large uploads into chunks, processes them in parallel Lambdas through Whisper, and reassembles — side-stepping Lambda's 15-min ceiling and payload limits without introducing containers. Whisper for transcription, LLMs for summarization, AES-256 at rest with automatic 24h file deletion. Shipped end-to-end from zero to production.

NaranjaX / Nave Negocios

Senior Software Engineer. Built mission-critical payment infrastructure processing $300B+ ARS monthly transaction volume. Direct integrations with VISA, Mastercard, AMEX card networks and local acquiring banks. PCI-DSS certified. Zero settlement delays.

Focal developer on Kausanna, a real-time dispute resolution engine powered by AI. Architected intelligent decision matrices for fraud prevention, chargeback management, and rapid capital recovery. Designed SONQO, a fully serverless payment gateway on AWS. Hands-on across card network rails and AI-driven risk underwriting models.

Muteado

Co-founded and built the entire technical infrastructure. Real-time AI platform providing political intelligence through news and social media analysis across Latin America. Processing thousands of data sources daily with sub-200ms latency for alpha generation.

Architected serverless ingestion pipelines for Twitter, TikTok, and TV. Custom LLM models for narrative detection, sentiment analysis, and trend prediction with applications in political risk assessment and market positioning. Shipped from zero to production in four months. Featured on Vorterix.

Projects

Marz

Co-founded an AI-powered influencer marketing platform optimizing capital allocation for B2C brands. Fully serverless on AWS. Sub-100ms P99 latency at scale. Automated discovery, negotiation, and performance tracking with real-time ROI analytics.

Reduced customer acquisition cost by 20% vs Meta Ads, delivering superior unit economics. Built GPT-powered negotiators that launch campaigns 10× faster, optimizing burn rate and time-to-market.

FLUX Records

Founded and built a music distribution platform from the ground up. Enabled 100+ independent artists to monetize across 75+ platforms including Spotify, Apple Music, TIDAL. Managing royalty flows and revenue distribution at scale.

Full-stack serverless architecture on AWS and Vercel. Automated royalty settlement pipelines with transparent payment tracking. Product-led growth with zero marketing spend, proving market fit through organic adoption. Built for artists with no technical background.

Tech talks

How I work

  1. I start with the README, not the code

    Before I open the editor I write what the product is supposed to do, wireframe it, diagram it, and run unit economics. If the math doesn't close for the segment I'm trying to solve, not a line gets written. Emails and feedback requests come after that — code is the consequence of a decision already made, not the place where you make it.

  2. Serverless by default, us-east-1, DynamoDB first

    My default stack is serverless on AWS in us-east-1. I start with DynamoDB and migrate to PostgreSQL when the access patterns justify it. Serverless wins when the service is core and has real demand; low traffic, ultra-low latency, or sustained throughput can argue otherwise — but that's the exception, not the rule.

  3. I cut UI polish, I never duct-tape architecture

    Under deadline, the first things to go are UI micro-interactions and non-critical features. What I never negotiate is a one-line patch that quietly rewrites the flow or the architecture. Every improvised patch lives longer than it should, and the debt it creates is the most expensive kind.

  4. Build the core, buy everything else

    If it's core to the product, I build it. If it isn't, I buy it — after comparing the price against the real cost of building it, maintenance included (not just the first sprint). The rule is easy; the discipline is holding it when building-for-fun starts looking tempting.

  5. Unit and integration always, except in throwaway MVPs

    Unit and integration tests are the floor, not the ceiling. They're what keeps you from discovering bugs in production. The only exception is an experimental MVP where the thing being validated is the hypothesis, not the code — and if I'm doing TDD there, the tests stay.

  6. Async and collaborative — but it always ends in an RFC or diagram

    I work in PRs, async but collaborative. For things that don't fit a Slack or email thread, a short call on Discord or Meet, and then the outcome lands in an RFC or diagram. A conversation without an artifact is lost in two weeks; the RFC outlives the team.

  7. LLM → go train → come back with sharper questions

    When I get stuck, I first use an LLM to order the problem. If I'm still stuck, I stop and go train. I come back with the problem solved or with better questions than I started with. The body in motion resolves what a stationary head can't.

  8. Observability beats picking the language of the month

    The Rust vs Go vs TypeScript debate is overrated. Most production bugs get fixed with structured logs, distributed traces, and well-chosen metrics — not by picking whatever language the latest paper recommends. Teams that invest in observability early age well.

Library

Filter
Sort
  • The Pragmatic Engineer

    The Pragmatic Engineer

    Gergely Orosz

    Reading list
  • How to Win Friends and Influence People

    How to Win Friends and Influence People

    Dale Carnegie

    Reading list
  • Steve Jobs

    Steve Jobs

    Walter Isaacson

    Reading list
  • The Subtle Art of Not Giving a F*ck

    The Subtle Art of Not Giving a F*ck

    Mark Manson

    Reading list
  • Staff Engineer

    Staff Engineer

    Will Larson

    Reading list
  • Accelerate

    Accelerate

    Nicole Forsgren, Jez Humble, Gene Kim

    Reading list
  • Building Microservices

    Building Microservices

    Sam Newman

    Reading list
  • Release It!

    Release It!

    Michael Nygard

    Reading list
  • Database Internals

    Database Internals

    Alex Petrov

    Reading list
  • The Pragmatic Programmer

    The Pragmatic Programmer

    David Thomas, Andrew Hunt

    Reading list
  • Designing Machine Learning Systems

    Designing Machine Learning Systems

    Chip Huyen

    Reading list
  • AI Engineering

    AI Engineering

    Chip Huyen

    Reading list
  • Zero to One

    Zero to One

    Peter Thiel

    Reading list
  • The Hard Thing About Hard Things

    The Hard Thing About Hard Things

    Ben Horowitz

    Reading list
  • Working Backwards

    Working Backwards

    Colin Bryar, Bill Carr

    Reading list
  • Hooked

    Hooked

    Nir Eyal

    Reading list
  • The Psychology of Money

    The Psychology of Money

    Morgan Housel

    Reading list
  • Never Split the Difference

    Never Split the Difference

    Chris Voss

    Reading list

Tech Stack

Serverless & Cloud

  • AWS Lambda
  • SQS
  • EventBridge
  • API Gateway
  • S3
  • CloudFront
  • CloudFormation
  • AWS IAM
  • AWS Secrets Manager
  • Vercel
  • Cloudflare

Platform & DevOps

  • Kubernetes
  • Docker
  • Lens
  • HashiCorp Vault
  • GitLab CI
  • BPMN (Camunda)

Data

  • PostgreSQL
  • Aurora Serverless
  • DynamoDB
  • Redis
  • Kafka
  • Snowflake

Languages & Frameworks

  • TypeScript
  • Node.js
  • React
  • Next.js
  • Tailwind CSS
  • shadcn/ui
  • WebSocket
  • Socket.io

AI

  • OpenAI
  • Claude
  • Mistral
  • Llama
  • Qwen
  • Whisper
  • AWS Bedrock

Observability

  • Datadog
  • Sentry
  • CloudWatch
  • PostHog

Payments & Auth

  • Stripe
  • MercadoPago
  • Commet.co
  • Clerk
  • Auth0

Certifications

  • PCI-DSS Compliance

    NaranjaX / Nave NegociosOngoing

    Card data security · Payment compliance

  • Architecting on AWS

    Amazon Web Services (AWS)Aug 2023

  • Amazon API Gateway for Serverless Applications

    Amazon Web Services (AWS)Apr 2022

  • AWS Lambda Foundations

    Amazon Web Services (AWS)Apr 2022

  • Problem Solving

    HackerRank2022be3b24005a01