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.
Five steps to a GitHub merge queue that does not stall
A merge queue tests each PR against the ones ahead of it before it lands. Five setup steps keep it moving instead of stalling the day you turn it on.
GitLab 19.0 moves the secrets manager into the pipeline
GitLab 19.0 bundles OpenBao as a native secrets store, so you stop running a standalone Vault just to feed your pipelines.
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.
This site runs the tests it ships.