I Think Like a Builder
I do not treat QA as a checklist at the end. I study the product, data, APIs, edge cases, and user journeys, then design coverage that protects the parts of the business people actually depend on.
I help product and engineering teams move faster without guessing. I read risk quickly, turn fuzzy requirements into testable behavior, build automation that engineers respect, and explain release confidence in plain English.
I do not treat QA as a checklist at the end. I study the product, data, APIs, edge cases, and user journeys, then design coverage that protects the parts of the business people actually depend on.
My automation work is readable, debuggable, and designed for change: Playwright, Cypress, Selenium, TypeScript, JavaScript, API suites, fixtures, test data, CI artifacts, and reports that shorten the path from failure to fix.
I focus on login, permissions, payments or billing-impacting flows, CRM workflows, mobile and device journeys, integrations, admin actions, and any behavior where a quiet defect can become a loud customer problem.
Hiring managers get more than test counts. I create quality signals, defect patterns, coverage stories, and release-readiness summaries that help teams make confident decisions without hiding risk.