Available nowMexico City · remote, worldwide

Eduardo Aguilar Cortés

Software Engineer. Most recently at Qualtrics. Before that, Globant — Software Architect from 2022.

Good code is a handover. I write mine for the next engineer, and the agent.

Based
Mexico City · open to relocation
Works
Remote, worldwide · overlaps US hours · hybrid in Mexico City
Open to
Software Architecture · Technical Lead · Senior Engineer
Languages
English · Spanish
Writing software
Since 2017

Professional Experience

01 · 2025 — 2026Enterprise SaaSRemote · Mexico CitySoftware Engineer

Qualtrics

A net-new enterprise module, built from requirements nobody had settled yet, shipped to Early Availability. The frontend architecture set there is the one the team built on.

  • Early Availability launch

    Greenfield work against six systems: five on code old enough to be AngularJS, and one API being built in parallel, so the target moved while we integrated with it. The patterns established there are what the rest of the module follows.

  • Accessibility Champion

    The team's designated champion. WCAG is checked at architectural review, where it is cheap, rather than at audit, where it is a rewrite.

  • Q&Able ERG

    Co-Chair · Mexico City

    Co-chairs the Mexico City chapter of the Q&Able employee resource group.

02 · 2017 — 2024Software Architect from 2022

Globant

Four clients, one employer — ending as Software Architect with three direct reports across frontend and infrastructure.

  • Cerifi

    2022 — 2024

    A multi-tenant database carrying more than twenty schema variations: deployments were unpredictable and data integrity was at risk. The migration patterns were unified and automated checks put in front of them. The drift went, and it has not come back — the checks are what keep it out.

  • Smile Direct Club

    2020 — 2022

    Mandatory 90-day patient check-ins ran on a third-party vendor that billed every month and could not be changed. The data collection moved in-house onto PostgreSQL through the Django ORM, HIPAA-compliant throughout. The vendor's bill went to zero, and the product team could iterate on the flow for the first time.

  • Cars.com

    2018 — 2020

    The 'Sell It Yourself' and 'Quick Offer' funnels — the paths a seller actually walks on Cars.com — moved onto a modern stack without a pause in traffic.

  • Discoverflow

    2017 — 2018

    Greenfield integration design, worked out in person with the client's program managers in Miami. Offshore and onshore shipped against one definition of done instead of two.

What I bring

Where it all comes together.

Where I learned it, and what I bringleads toRunning on this site
Qualtrics · 2025 — 2026Architecture the team built on, accessible by defaultThe frontend architecture set on a net-new module is the one the team built on. As the team’s Accessibility Champion, WCAG was checked at architectural review, where it is cheap.One document per subject, each held to the code by a check the build runs, so the next engineer builds on rules rather than guesses.
Cerifi · 2022 — 2024Drift caught by automation, not by peopleAutomated checks in front of more than twenty schema variations kept data drift out, instead of cleaning it up after.The build checks the rules the code is written to. Break one and the failure names the rule you broke.
Smile Direct Club · 2020 — 2022Owning what the business depends onPatient check-ins moved off a vendor that billed every month and could not be changed, in-house and HIPAA-compliant throughout. The vendor’s bill went to zero.Every outside vendor enters through one door, so replacing one is a change in one place.
Cars.com · 2018 — 2020Change without stopping the businessThe seller funnels moved onto a modern stack without a pause in traffic.Merging updates the database schema and then the site in one step, so the live site and the code never disagree.
Discoverflow · 2017 — 2018One definition of doneOffshore and onshore teams shipped against one definition of done.Every pull request to master runs the same naming rules, the full test suite and a production build, for people and for agents alike.

Exhibit · this site

Don’t take my word for it.

This site is where all of it runs at once, built the way I would build yours: clear boundaries, every dependency pointing down, and a build that fails when one doesn’t. Pick a slice and try to break it.Pick a change and watch the build refuse it.

Pages — compose verticalsVerticals — sealed from each otherAdapters — one door per outside vendorShared — depends on nothing above itevery arrow points down ↓PagePagePageVertical AVertical BVertical CSign-inDatabaseFilesVendor’s SDKUI kitUtilitiesTranslations
01 · Build fails

Vertical A reaches into Vertical B

Verticals never reach into each other. Either one can be rewritten, or handed to a new team, without breaking the other.

FAIL  architecture/dependency-direction.test.ts  › keeps verticals unaware of each other
AssertionError: expected [ …(1) ] to deeply equal []
Outer ring · watched from outside
read Nov 4, 2026
Pages — compose verticals
  • Page
  • Page
  • Page
Verticals — sealed from each other
  • Vertical A
  • Vertical B
  • Vertical C
Adapters — one door per outside vendor
  • Sign-in
  • Database
  • Files
  • Vendor’s SDK
Shared — depends on nothing above it
  • UI kit
  • Utilities
  • Translations

Vertical AVertical B

01 · Build fails

Vertical A reaches into Vertical B

Verticals never reach into each other. Either one can be rewritten, or handed to a new team, without breaking the other.

FAIL  architecture/dependency-direction.test.ts  › keeps verticals unaware of each other
AssertionError: expected [ …(1) ] to deeply equal []
Watched from outside · read Nov 4, 2026

Tech Stack

warnI am fluent in JavaScript; although sometimes the browser does not understand my accent.

Show what I used at

Frontend

in the browser
  • React
  • Redux
  • Angular
  • AngularJs
  • Vue.js
  • D3
  • Sass
  • Less
  • CSS

Backend

on the server
  • Node.js
  • hapi
  • Django
  • Drupal

Data

where it’s kept
  • PostgreSQL
  • MongoDB

Cloud and delivery

where it runs
  • AWS
  • Docker
  • Kubernetes
  • Next.js
browser and server
  • TypeScript
  • JavaScript
languages · both sides
  • Python
language
Testing and shipping · across every tier
  • Jest
  • GitHub