Renzo Mayer

Software engineer, tech lead, builder

Building Web Platforms That Grow On Purpose

Renzo Mayer • Software Engineer & Tech Lead

Currently Frontend & Data Engineer at Howdy.com. Before that I led engineering across 200+ revenue-critical web properties at OnPoint, running the whole stack — AWS infrastructure as code, the platforms on top of it, and the analytics that told us whether any of it worked. Four legs to the practice: growth, infrastructure, product and data. Open to interesting conversations, so feel free to reach out.

Get in touchAbout meWorkWriting
Focus
Growth engineering, cloud infrastructure, product, data
Stack
Next.js, TypeScript, Node, Postgres, BigQuery, Terraform, AWS
Status
Frontend & Data Engineer at Howdy.com — building on the side
Based
Montevideo, Uruguay — remote, GMT-3

01Practice

Four disciplines rather than one title. Most of the interesting work happens where two of them overlap.

  • 01Growth

    Marketing that ships as code and gets measured properly.

    Growth work is engineering with a shorter feedback loop. Acquisition channels, content distribution, brand surfaces, landing pages — built fast, instrumented properly, and killed without ceremony when the numbers say so.

    • Acquisition and distribution surfaces built as real code, not one-off pages.
    • Instrumentation that survives contact with live campaigns.
    • Experiments with a defined outcome before they ship.
    • Performance treated as a conversion feature, because it is.
    • Acquisition
    • Content distribution
    • Landing pages
    • Analytics
    • SEO
    • Core Web Vitals

  • 02Infra

    Cloud infrastructure as code, for fleets rather than single apps.

    Five years operating hundreds of revenue-critical properties taught me that anything done by hand eventually gets done wrong, at scale, on a Friday. So provisioning, networking, delivery and CI live in version control and get reviewed like any other code.

    • AWS in depth: ECS, EC2, RDS, S3, CloudFront, WAF, Route 53.
    • Terraform and Terragrunt for environments that are reproducible, not remembered.
    • CI/CD on GitHub Actions and Jenkins — one pipeline shape for every property.
    • Automated provisioning, operations and testing across a 180+ site fleet.
    • GCP where it fits: BigQuery, GA4 exports, scheduled transforms.
    • AWS
    • GCP
    • Terraform
    • Terragrunt
    • ECS
    • CloudFront
    • GitHub Actions
    • Observability

  • 03Product

    The whole path from database to the thing someone actually touches.

    I do not think of frontend and backend as separate jobs. A feature is an API shape, a data model, a rendering strategy and an interaction — decided together. I have led teams doing this and still write the code myself.

    • Next.js and TypeScript end to end: server components, edge, caching strategy.
    • Backend and APIs: Node, Express, Postgres, MySQL, integration work.
    • Interface craft: accessibility, motion, design systems, responsive behaviour.
    • Technical leadership — architecture, review culture, mentoring, stakeholder contact.
    • Next.js
    • TypeScript
    • Node
    • Postgres
    • Design systems
    • Accessibility
    • Tech leadership

  • 04Data

    Read more →

    Foundations first: get the data right, then let people ask it questions.

    The leg I am pushing hardest right now. Ingestion and modeling before anything clever, a semantic layer so a metric means one thing everywhere, a conversational surface on top, and agents evaluated against recorded outcomes instead of vibes.

    • Ingestion and modeling: idempotent loads, explicit grain, replayable history.
    • A typed metric layer that both humans and models read.
    • Conversational access, so the person with the question does not need SQL.
    • Agentic evaluation against ground truth — correctness, cost, consequence.
    • BigQuery
    • Postgres
    • GA4
    • Semantic layer
    • Evaluation
    • Agents

02Selected work

All work →

03Writing

All writing →

04Contact

Working on something in this territory? Let us talk.

Open to conversations about growth engineering, cloud infrastructure, product work, data platforms — and the occasional strange side project.