Skip to content
Luis Cardeña

About

Luis Cardeña

I'm a QA engineer and SDET, and I've been doing this for fourteen years. I started in manual testing on desktop and IVR systems, moved into data and ETL validation where a wrong number means someone's payment is wrong, then into automation — web, then mobile, then desktop, then decentralised applications where almost nothing behaves the way the documentation promises.

Along the way I've led small distributed test teams, built frameworks from nothing, and spent a lot of time on the specific problem of making a test suite that a team still trusts a year later. That last part is the hard bit, and it's mostly what people hire me for.

These days I also build products. I take on feature work and whole applications, usually with an AI assistant in the loop from first prototype through to release. I like the combination: knowing how to break things well makes me better at building them, and shipping my own software keeps me honest about whatwell-tested actually has to mean when there's a deadline.

I'm based in Mérida, Mexico, which puts me in a full working-day overlap with teams across the US and Latin America. I've worked remotely with distributed teams for most of the last decade.

At a glance

Focus
Test automation, CI/CD, release quality
Also
Product engineering, AI-assisted builds
Platforms
Web, iOS, Android, desktop, Web3
Based in
Mérida, Mexico
Hours
UTC−6 · overlaps US & LATAM business hours
Languages
Spanish (native), English (fluent)

How I think about it

Four opinions I'll bring with me

A retry is not a fix

If a test is flaky, something is genuinely non-deterministic — a race condition, a shared fixture, an assertion against a promise the app never made. Adding a retry hides it and teaches your team to ignore red builds.

Coverage percentage is a vanity metric

I'd rather have fifteen tests that cover the journeys your revenue depends on than four hundred that assert a button is still blue. Risk decides what gets automated, not a target number.

Tests your team won't maintain are worthless

I write test code to the standard of production code and review it the same way, because a suite that becomes unmaintainable gets deleted — usually about a quarter after the consultant leaves.

Quality is not a gate at the end

The cheapest bug is the one caught while the feature is still being designed. I'd rather be in the requirements conversation than handed a release candidate on a Friday.

Experience

Fourteen years, seven teams

Employers are described by sector rather than named — current clients and roles stay confidential. Happy to talk specifics on a call.

  1. 2025 — Present

    SDET & QA / Developer

    Early-stage startup · confidential

    Own the quality layer end to end — test automation, CI and release verification — and build product features alongside the team.

  2. 2024 — 2025

    Senior QA Engineer

    B2B wholesale commerce platform · enterprise retail SaaS

    Release readiness across multiple environments; automation for web and mobile.

  3. 2022 — 2023

    Software Development Engineer in Test

    Decentralised messaging platform · Web3

    Test architecture and automation for web, desktop and mobile clients.

  4. 2021 — 2022

    QA Engineer

    Global software consultancy

    Cypress framework strategy, API automation, SQL and NoSQL validation.

  5. 2018 — 2020

    QA Lead

    Digital transformation consultancy

    Led a distributed test team while owning ETL validation tooling.

  6. 2015 — 2018

    QA Engineer

    Insurance data programme · via consultancy

    ETL interface testing and SQL-based data validation at scale.

  7. 2014 — 2015

    QA Lead

    Beverage distribution startup

    Built the QA process from nothing; led testers for a major beverage brand.

  8. 2012 — 2014

    QA Analyst

    Nearshore software services

    Desktop and IVR application testing; SQL query development.

Education

  1. 2013 — 2014

    Executive Master, Information Technology Management

    Universidad Tecmilenio

  2. 2005 — 2009

    Bachelor, Information Technology Management

    Universidad Autónoma de Yucatán

Toolkit

Test automation

  • Playwright
  • Cypress
  • WebdriverIO
  • Appium
  • Selenium
  • TypeScript
  • JavaScript
  • Python

Pipelines & infrastructure

  • GitHub Actions
  • GitLab CI
  • Docker
  • Google Cloud
  • Parallel execution
  • Allure & custom reporting

APIs & data

  • REST & API testing
  • Postman
  • PostgreSQL
  • MongoDB
  • SQL & NoSQL
  • ETL validation

Product development

  • React
  • React Native
  • Node & Express
  • Tailwind
  • Solidity basics
  • AI-assisted delivery

Get in touch

Think I'd be useful?

The best place to start is a conversation about what you're building and what's getting in the way.

Email — scheduling link coming soon