Skip to content
Luis Cardeña

Case studies

Work, with the detail left in

Client names are withheld where the engagement is under NDA — described by sector instead. The open-source work is named, public, and you can read every line of it.

Early-stage startup

Confidential

Product company · small engineering team

2025 – present

SDET & QA / Developer

Owning the quality layer at a startup shipping fast

The problem

A small engineering team shipping quickly with no dedicated quality function. Testing was manual and ad hoc, nothing ran automatically on a change, and the cost of that was starting to show up as rework rather than as obvious bugs.

What I did

  • Built the first automated test coverage in a codebase that had none
  • Set up CI so the suite runs on every change instead of before a release
  • Introduced release verification the team can run without me
  • Build product features alongside the quality work, as the team needs

Tinyboard

Own product

My own product · school–family communication

2025 – present

Sole engineer — architecture, delivery and quality

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

The problem

The app my child's school used posted children's photos behind plain, guessable URLs — anyone who got hold of a link could reach them. I wanted to build the same daily-updates experience for families without that exposure, which meant treating media access control and children's data as architectural constraints rather than features to bolt on later.

What I did

  • Built it as a monorepo: an Expo / React Native app for guardians and a Next.js admin for school staff, over shared typed packages
  • Enforced access in Postgres itself with row-level security, so a bug in a client cannot expose another family's data
  • Designed a media pipeline where no photo is reachable from a plain URL — every asset is served through a signed, authorised path
  • Covered the row-level security policies with pgTAP tests, so the security model is verified by tests rather than by intention
  • Wired the full check suite: lint, typecheck, Vitest, database security tests and an end-to-end backend smoke run
  • Built the release path to TestFlight and Play internal testing through EAS, with a written runbook

Property listings with 3D tours

Personal project

Personal side project · in progress

2025 – present

Built independently, in my own time

A property site with immersive 3D tours

The problem

I wanted to see whether a listing page could let someone walk a property remotely rather than scroll a gallery of photos, and what that does to the browsing flow.

What I did

  • Built the listing platform with embedded interactive 3D property tours
  • Designed the browsing and enquiry flow around mobile visitors first

B2B wholesale commerce platform

Confidential

Enterprise retail SaaS

2024 – 2025

Senior QA Engineer

Release readiness across multiple environments for an enterprise commerce platform

The problem

A wholesale commerce platform used by major retail brands ships on a continuous release cycle across several environments. Each cycle needed functional and non-functional verification without becoming the thing that delayed the release.

What I did

  • Ran functional and non-functional testing across 3+ environments and successive release cycles
  • Built and optimised automated frameworks covering web and mobile surfaces
  • Identified the high-value regression scenarios worth automating first, instead of automating everything indiscriminately
  • Reviewed automated test code from across the team to keep maintenance cost down

Decentralised messaging platform

Confidential

Web3 instant messaging

2022 – 2023

Software Development Engineer in Test

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

The problem

A small team was shipping a decentralised messaging platform simultaneously as a web app, a macOS and Windows desktop app, and a Flutter mobile app. Every release meant manually re-testing chat, friend requests, calls and screen sharing on all of them. Nothing was automated, and regression testing was eating the schedule.

What I did

  • Designed and built test automation frameworks for all three platforms, rather than treating mobile and desktop as untestable
  • Wrote a Playwright E2E suite for the web client covering video calls and screen share — the flows everyone assumed couldn't be automated
  • Built the first Appium coverage for the Flutter mobile app after researching the strategy from scratch
  • Set up and maintained CI/CD pipelines so the suites ran on every change instead of on request
  • Reviewed test code from other engineers and wrote the documentation the team still works from

Disability claims management

Confidential

Insurance · data engineering

2015 – 2020

QA Engineer, then QA Lead

Data quality for ETL pipelines where a wrong number means a wrong payment

The problem

One of the largest disability claims managers in its market ingested HR and payroll data from client companies to drive payment processing. If an ETL interface silently mangled a record, someone's payment was wrong — a class of bug that UI testing never catches.

What I did

  • Created, maintained and executed test plans for the ETL interfaces
  • Wrote SQL and OpenEdge Progress scripts to validate processed data against source
  • Led a small distributed team of testers while continuing hands-on validation work
  • Trained new team members on SQL scripting and test plan design

Get in touch

Want this kind of detail on your own release process?

A fixed-scope audit gets you a written assessment of your suite, your pipeline and your release process in a couple of weeks.

Email — scheduling link coming soon