Skip to content
Luis Cardeña

Services

Four ways to work together

Every engagement is scoped in writing before it starts, with a fixed price or a weekly rate. You should always know what you're buying.

Quality Audit

Fixed scope · 1–2 weeks

Priced per engagement — ask for a quote.

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

I go through your test suite, CI pipeline and release process the way a new senior hire would — except I report back in two weeks instead of two months. You get a written assessment, a ranked list of what's actually costing you time, and a roadmap you can hand to your own team even if we never work together again.

Best when you suspect something is wrong but can't name it yet.

What you get

  • Written audit of test coverage, suite health and CI configuration
  • Flaky-test inventory, ranked by how often it blocks a release
  • Pipeline timing breakdown with concrete speed-up targets
  • Prioritised 90-day roadmap with effort estimates
  • Live walkthrough with your engineering team
Enquire about Quality Audit

Embedded SDET

Most asked for

Retainer · 10 or 20 hrs/week

Priced per engagement — ask for a quote.

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

I join your standups, your repo and your Slack, and own the automation layer as if I were staff. That means writing and maintaining the suite, keeping CI green, triaging failures before they reach your developers, and documenting it all so the work outlives the engagement. Most clients start here after an audit.

Best when you have a team shipping but no dedicated quality owner.

What you get

  • Test automation written and maintained in your stack
  • CI/CD pipelines kept fast and green, with failure triage
  • Release-readiness checks across your environments
  • Code review on test code written by your developers
  • Documentation and handover built in from day one
Enquire about Embedded SDET

Automation Build

Project · 4–10 weeks

Priced per engagement — ask for a quote.

From zero to a trustworthy suite running in CI.

A greenfield build for teams with no automation, or a rebuild for teams whose suite has stopped earning its keep. I design the architecture, write the first meaningful set of tests, wire it into CI with proper reporting, and train your team to extend it. You own everything at the end — no proprietary tooling, no lock-in to me.

Best when you're scaling and manual regression no longer fits.

What you get

  • Framework architecture chosen for your stack and team's skills
  • E2E coverage of your highest-risk user journeys
  • Parallelised CI execution with reporting and alerting
  • Mobile coverage for iOS and Android where relevant
  • Team training sessions and a written contribution guide
Enquire about Automation Build

Product Engineering

Retainer or project

Priced per engagement — ask for a quote.

Features, integrations and full builds — shipped and tested.

I also build. Years of taking other people's software apart taught me exactly where it tends to break, and I write my own code accordingly. I take on feature work, API integrations and full product builds — increasingly with an AI assistant in the loop from prototype to release, which is how I keep small-team delivery fast without letting quality slide.

Best when you need delivery capacity that won't create cleanup later.

What you get

  • Feature development in TypeScript, React, React Native and Node
  • Third-party API and payment integrations
  • Full builds from prototype to production release
  • AI-assisted delivery, with tests written alongside the feature
  • Mobile app builds and store submission support
Enquire about Product Engineering

Process

How an engagement actually runs

Consulting goes wrong when nobody can tell what's happening. This is the rhythm I keep.

  1. 01

    Intro call

    Thirty minutes on what you're building and what's going wrong. I'll tell you straight away if this isn't a problem I'm good at.

  2. 02

    Scoped proposal

    A written scope with a fixed price or a weekly rate, what you get, and what I need from your team. No open-ended hourly billing.

  3. 03

    First week

    Repo access, environment set up, and a first pass at the problem. You'll see something concrete inside the first week, every time.

  4. 04

    Weekly rhythm

    A short written update every week: what moved, what's blocked, what I need. You never have to ask what I'm working on.

  5. 05

    Handover

    Documentation, a contribution guide and a walkthrough with your engineers. The work has to keep running once I'm gone.

Toolkit

What I work in

I'll recommend based on your stack and your team's existing skills, not on what I most enjoy using.

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

Questions

Frequently asked

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.

Do you touch production environments?

Carefully, and only with explicit agreement on what I'm allowed to run. I'd rather build a realistic staging environment than test against production, but I've worked in plenty of places where some verification has to happen on the real thing.

How do engagements usually start?

A short call to find out whether I'm actually the right person for your problem. If we both think so, most clients start with a fixed-scope audit — it's a small commitment and you get something useful out of it whether or not we continue.

Do you offer fixed prices?

For audits and defined build projects, yes. Ongoing embedded work is a weekly retainer, because the point of it is being available for whatever this week's problem turns out to be.

Will your work survive after you leave?

That's the main thing I'm being paid for. Documentation and handover are part of every engagement, not an afterthought, and I'd rather train your engineers to extend the suite than make you dependent on me for it.

Where are you based, and which hours do you work?

Mérida, Mexico, on UTC−6. That overlaps a full working day with both US and Latin American teams, and gives a few hours with Europe in my mornings. I've worked remotely with distributed teams for years.

What does your availability look like?

It varies, and I deliberately take on a small number of engagements at a time so the ones I'm in get proper attention. The honest answer depends on when you ask — so it's worth asking.

Can you share code from your client work?

Not for client work — that's all confidential. My own projects are on GitHub and are a fair sample of how I build; beyond that, I'm happy to walk through architecture and approach on a call.

Get in touch

Tell me what's breaking

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