Santiago Hernández

I lead products from problem framing and design validation through production.

As a Tech Lead, I work across web, mobile, and AWS, use AI coding agents to deliver, and help teams adopt AI through clear rules.

Santiago Hernández

What I bring to a team

Projects change. These are the skills I bring to each one.

Career path

  1. 2026 - present

    Technical Lead

    • Lead engineering for a Spanish-language reading platform built on microservices across nearly 20 repositories, using NestJS, Java, React, React Native, Vue, and AWS.
    • Migrated the gateway from Spring Boot to NestJS with no downtime.
    • Contributed to an organizational standard of 22 rules for using AI in production and helped engineering, design, product, and QA adopt it through 27 shared skills.
    • In parallel, I lead engineering for a US training company I have worked with since 2023.
  2. 2021 - 2026

    Fullstack Software Developer

    • I built products for clients in the United States and Latin America across healthcare, retail, food, project management, and education. Two products took most of my time.
    • Served as the lead developer for a learning platform built with Meteor and React for a U.S. training company.
    • Built an engineering calculation product for industrial equipment from scratch.
    • Delivered reading analytics, diagnostic assessments, browser audio recording, and payment features for an educational platform.
  3. 2019 - 2021

    Project Manager, part-time

    • Led entrepreneurship education programs in high schools across Uruguay and facilitated workshops.
    • Moved programs online during the pandemic and led and trained volunteer teams.

How I work

I validate the design of each solution before building it, and I build it with TDD and planned edge cases. Agents do much of the work, and the decisions stay with me. This is the process I follow, and I write it into the briefs I give the agents.

  1. Define scope

    MeI define what is in scope and what is not.

    The agentsThe agents read the request, search every involved repository, and return the open questions.

  2. Validate the design

    MeI spend the most time here. I challenge options, validate product decisions with the PM, and remove assumptions before code is written.

    The agentsThe agents propose options with tradeoffs and list every assumption they made. They help turn the selected approach into a spec.

  3. Plan the work

    MeI define the files, tests, exclusions, and contracts between repositories. I set the permissions and TDD requirements for each workstream.

    The agentsThe agents work from repository briefs in their own worktrees. They follow the agreed API and database contracts.

  4. Build with TDD

    MeI require every piece to start with a failing test for the right reason. I make edge cases part of the plan, including empty, zero, negative, duplicate, limit, and error paths.

    The agentsThe agents implement and review each task separately. They do not change a test just to make it pass.

  5. Verify with evidence

    MeI check the evidence against the plan and decide whether the result is ready.

    The agentsThe agents run the test suite and end-to-end checks in QA, and leave the command output, logs, and database state as evidence.

  6. Review and merge

    MeI authorize each merge explicitly and decide whether a rollback is needed after reviewing logs.

    The agentsThe agents perform an exhaustive review before human review and monitor logs after the merge.

Automatic safety net

Hooks run on every agent command to enforce the rules before mistakes reach shared environments.

agent $ git push origin main

BLOCKED: git push to 'main' (current branch 'main').
Changes to master/main need explicit authorization from the human.
Ask the user to run this command themselves with `!`.

Principles

A lab for testing ideas with real products

I do the design, the backend, and the app myself, and I use these products to test ideas before I bring them to a team.

Pila Today screen with the readiness score (sample data)

Pila

iOS · SwiftUI · Beta

Pila reads Apple Health and recommends how much to train based on your own history, calculated on the phone rather than against averages.

PadelBump match detail with the score

PadelBump

iOS · SwiftUI + Python backend · In App Store review

PadelBump brings live professional padel to iPhone through Live Activities, with a backend that checks matches every 10 seconds.

TorneosPadelUy map of tournaments

TorneosPadelUy

iOS and web · Expo, React Native and Supabase · Live

TorneosPadelUy covers amateur padel tournaments across Uruguay, with one Expo and React Native codebase for iPhone and web.

Public engineering controls

I use these tools every day. Several of them enforce rules from the AI standard I contributed to.

Outside work

I live in Montevideo, where I play padel and run. Padel led me to build TorneosPadelUy for amateur tournaments in Uruguay and PadelBump for live professional padel. Running inspired Pila, an app that reads Apple Health and helps me decide how much to train.

Compare notes on AI adoption in engineering

I am open to conversations about AI adoption, architecture, and technical leadership.

Most of my work lives in private client repositories. © 2026 Santiago Hernández