Skip to content

Software engineer & tech lead · AI, data, growth

Renzo Mayer

Building Platforms That Grow On Purpose

Currently Frontend & Data Engineer at Howdy.com, supporting growth with technology and AI. Before that I led engineering across 200+ revenue-critical web properties at OnPoint, running the whole stack, from AWS infrastructure as code to analytics. Four legs to the practice: growth, infrastructure, product and data & AI. Open to interesting conversations, so feel free to reach out.

  • Next.js
  • TypeScript
  • AI SDK
  • Agents
  • Postgres
  • BigQuery
  • Terraform
  • AWS

Companies along the way

Practice

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

  • 01

    Growth

    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
  • 02

    Infra

    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
  • 03

    Product

    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
  • 04

    Data & AI

    Foundations first: get the data right, then let people — and agents — 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
    • AI SDK
    • Agents
    • Evaluation
    Read more

About

Software engineer and tech lead who kept drifting toward the place where data, growth and product meet.

I am a software developer with an enthusiasm and focus on web applications. I care about building immersive, fast, scalable interfaces through carefully crafted code and user-centric design — and about the systems around them: continuous integration, continuous improvement, continuous delivery.

  • Montevideo, Uruguay
  • Spanish
  • English
  • Portuguese
  • French
Renzo Mayer
Years building for the web
12
Web properties delivered
200+
Sites on one install
180+
Languages spoken
4

Selected work

  • building2026 — ongoing

    Data foundation & agentic evaluation

    An ongoing build: modeled data, a typed metric layer, conversational access, and agent runs scored against recorded outcomes.

    • Next.js
    • TypeScript
    • Postgres
    • BigQuery
    Case study
  • live2026 — ongoing

    Growth Engineering Stack

    Marketing and engineering in the same loop: acquisition, distribution, analytics and AI-assisted web experiences.

    • Next.js
    • TypeScript
    • Analytics
    • AI SDK
    Case study
  • planned2026 →

    Lab — 3D, objects and other ideas

    A home for 3D projects, physical goods and the experiments that do not fit anywhere else. Store included, eventually.

    • React Three Fiber
    • Blender
    • 3D printing
    • Commerce
    Case study

Writing

Contact

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.

Get in touch