Skip to content
Luis Cardeña

QA Engineer · SDET · Product Developer

I make shipping safe —then I help you ship.

I'm the engineer teams bring in when releases have become scary. I find what's actually breaking, build automation your team trusts, and get the pipeline green again — then stay to help build the product.

Experience
14 years
Platforms
Web, iOS, Android, desktop
Based in
Mérida, Mexico
Hours
UTC−6 · US & LATAM overlap

Experience

Fourteen years in quality engineering

Employers are described by sector rather than named. 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.

Full history and background →

Selected work

Proof, not adjectives

Client names are withheld where the engagement is confidential. The open-source work is public, and you can read every line of it.

2025 – present

Early-stage startup

Product company · small engineering team

Owning the quality layer at a startup shipping fast

  • Engagement ongoing — details confidential
Read the detail →

2025 – present

Tinyboard

My own product · school–family communication

A school-to-family platform where the privacy model and the test layer were designed first

  • Running in production; store distribution in internal beta while the later phases land
  • Auth, guardian invites and consent, daily posts and the secure media pipeline all shipped
  • Security model covered by automated database-level tests rather than by manual review
Read the detail →

2024 – 2025

B2B wholesale commerce platform

Enterprise retail SaaS

Release readiness across multiple environments for an enterprise commerce platform

  • Release readiness verified every cycle with production issues kept low
  • Regression suite execution time cut through targeted automation
  • Test-code defect rate reduced through consistent review
Read the detail →

2022 – 2023

Decentralised messaging platform

Web3 instant messaging

E2E coverage for a decentralised messenger across web, desktop and mobile

  • Manual testing effort down roughly 40%
  • Build and test execution time down roughly 30%
  • Regression cycle time down roughly 25%
Read the detail →

All case studies →

Also on GitHub

  • Tinyboard — A school-to-family daily-updates platform: schools post what each child did, share a calendar and message guardians — with children's media locked behind signed URLs rather than guessable ones. Expo app, Next.js admin, Supabase with row-level security.
  • pequeguia — A community app for finding kid-friendly things to do nearby. I built it as a father tired of hunting across a dozen sites every weekend, and it covers listings, search by location and community submissions.
  • lastfmdiscogsscrobbler — Scrobbles plays from your Discogs vinyl collection into Last.fm. A full-stack build — Node, Express, React and Tailwind — handling OAuth against two third-party APIs and reconciling their catalogues.
  • spoti2qobuz — Syncs a Spotify playlist into Qobuz, matching tracks across two catalogues that disagree about metadata more often than you'd expect. Built because nobody maintains an up-to-date New Music Friday over there.

All projects →

Skills & tools

What I work in

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
Years in quality engineering
14
Manual test effort removed on a Web3 platform
40%
Faster CI build & test execution
30%
Platforms covered: web, iOS, Android, desktop
4

Consulting

Four ways to work together

Most engagements start with an audit, because it's the cheapest way for both of us to find out whether I can help.

Quality Audit

Fixed scope · 1–2 weeks

A clear-eyed read on why your releases hurt, and the shortest path out.

What's included →

Embedded SDET

Most asked for

Retainer · 10 or 20 hrs/week

Senior quality engineering on your team, without opening a headcount.

What's included →

Automation Build

Project · 4–10 weeks

From zero to a trustworthy suite running in CI.

What's included →

Product Engineering

Retainer or project

Features, integrations and full builds — shipped and tested.

What's included →

What teams call me about

  • The E2E suite is red and nobody trusts it
  • Release day keeps slipping on manual regression
  • Flaky tests get re-run until they pass
  • No mobile coverage before the App Store deadline
  • CI takes 45 minutes and blocks every merge
  • QA is a bottleneck instead of a safety net
  • We find out about bugs from our users
  • Coverage looks high but catches nothing
  • Only one person knows how the tests work
  • The staging environment never matches production

Questions

The things people ask first

Do you only write tests, or do you write production code too?

Both. Quality engineering is my specialism and the reason most people hire me, but I take on feature work, API integrations and full product builds as well. Years of taking other people's software apart is useful training for building software that holds up.

What does 'flaky test' work actually involve?

Finding out why a test is non-deterministic, which is usually a race condition, a shared fixture, or an assertion written against something the app never promised. I fix the cause rather than adding a retry. Retries hide the failure and teach your team to ignore red builds.

Can you work with our existing test suite, or do you want to rewrite it?

I work with what you have by default. A rewrite is expensive and usually unnecessary — most suites need their architecture fixed and their worst 10% deleted, not replacing. If a rebuild genuinely is the cheaper option, I'll show you the arithmetic before you commit to it.

Which frameworks do you work in?

Playwright, Cypress, WebdriverIO and Appium, mostly in TypeScript, plus Selenium and Python where that's what the team already runs. I'll recommend based on your stack and your team's existing skills, not on what I most enjoy using.

Do you test mobile apps?

Yes — iOS and Android, including Flutter and React Native apps. Mobile automation is where a lot of teams give up and go manual, so it's often where the fastest wins are.

Read all questions →

Get in touch

Something in your pipeline is costing you a release

If you can describe the problem in three sentences, I can usually tell you on a first call whether it's a two-week fix or a two-month one.

Email — scheduling link coming soon