QA Automation Engineer at Wander
I own end-to-end test automation and CI infrastructure across the wander.com marketplace and the WanderOS direct-booking platform. I treat the test suite as a product: deterministic, cost-aware, and loud in the right way when something breaks.
- Became the top contributor to both Playwright suites, with 131 pull requests and 582 commits from March to July 2026
- Built and now maintain 19 CI workflows covering release gates, production smoke tests, checkout, payments, accessibility, visual regression, API health, and mobile/WebKit coverage
- Created a live, Linear-powered QA analytics dashboard for Marketplace, WanderOS, and Platform teams
- Built production booking and checkout canaries that catch auth, pricing, payment, and booking failures before customers do
- Reduced GitHub Actions spend by approximately 46% in one suite while preserving coverage and merge-blocking gates
- Added Sentry-enriched, plain-English Slack alerts so failures arrive with useful backend context instead of raw noise
- Reliable Playwright end-to-end and API test suites
- Release gates, scheduled monitors, and production canaries
- GitHub Actions architecture and CI cost optimization
- QA observability with Sentry, Slack, traces, and structured test artifacts
- Internal quality tooling with Next.js, Linear GraphQL, and Google SSO
Playwright JavaScript / TypeScript GitHub Actions Next.js Linear GraphQL Sentry Slack API Cypress
WanderSearch - Cypress automation for search functionality, including reusable custom commands, edge-case coverage, test cases, and bug reporting.
Good automation should fail on real defects, not noise. It should be readable, maintainable, economical to run, and clear enough that the whole team can trust the release signal.