Lead Quality Engineer · Test Automation · Quality Platforms · AI-assisted Testing
Open to Lead and Senior QA roles, remote.
Playwright · TypeScript · Cypress · Appium · API testing · Mobile (iOS/Android) · Performance · CI/CD · AI agents
- Automation frameworks that stay fast and readable as the suite grows past a few hundred tests
- AI-assisted QA workflows: agents that read a change, plan the tests, run them, and write the report
- Quality gates in CI, so a broken build stops before it reaches a customer
- Web, mobile and API coverage in one suite
- I chase the odd detail. Most real bugs are the thing that looked slightly wrong and got waved through.
- I instrument before I theorise. One run that prints the real state beats a day of plausible explanations.
- A flaky test is a bug in the test, not weather. I fix the cause, I do not raise the timeout.
ai-qa-engineer — a coding-agent skill that maps a web app from its UI and source, plans coverage at the right layer, runs the tests, and triages each failure with evidence.
capybaraTest — 68 end-to-end scenarios for OWASP Juice Shop using Capybara, RSpec, and Selenium. The self-contained suite found three real defects and runs in parallel on CI.
14 years in QA, from manual testing to building the automation platform a team runs on.
Sole QA across two teams at the Wikimedia Foundation, covering web, iOS, Android and KaiOS, where I built the JavaScript and Cypress framework that ran on CircleCI. Before that I set up a company's QA process from nothing as QA Lead: hired and trained the team, and built the Appium, RestAssured and Espresso/XCUITest suites behind it. Most recently Lead QA Engineer at Chili Piper, owning quality for the chat, concierge and AI agent products.
I have written automation in TypeScript, JavaScript, Java, Kotlin, C# and Ruby. The language is not the hard part.
- Building an agent that turns a URL or a pull request into a test plan, a Playwright run, and a bug report
- Contributing to open source testing tools