Lead QE.
Ship hours.
I build the test infrastructure that takes a team's release cycle from days to hours: strict types, lean UI E2E, contract checks at every seam.
- perm · contract
- remote · worldwide
- available now
- github ↗
I'm wrapping up at Sony Interactive Entertainment on 12 June 2026, and from 13 June I'm available for remote work worldwide, perm or contract. My day-to-day is test automation across web, API, and mobile; I'd rather push validation into the API and contract layer than fight flaky UI flows. As Lead QE at Sony I run a team of three and set the engineering bar that keeps our release cycles down to hours: strict typing, linting, hooks, tight PR practice.
- Oct 2022 – now
- lead of 3 QEs
- Playwright · WDIO
- ships in hours
From the blog.
Where Test Health Belongs: CI Logs or an Observability Backend
Your suite emits pass rate and flake count every run, then buries them in a CI log nobody scrolls; export them over OTLP and a dashboard catches the rot.
Retrying a flaky test deletes the evidence of a real bug
A bug that fails one run in four passes CI 99.6 percent of the time under three retries. Quarantine the test instead and keep the signal.
Three caching changes that take 80% off a GitHub Actions build
A cached ~/.npm drops a cold Node install from four minutes to thirty seconds, and two more cache changes take the rest of the pipeline down with it.
This site runs the tests it ships.