Fortune 500 Contracts: Enterprise Testing at Scale
Contract SDET work for Meta, Blue Cross Blue Shield, and major enterprises
How I built a Playwright framework from scratch and transformed a manual QA team
Concluded:
See it liveWhen I joined CooperVision, there was no test automation. None. The QA process was 100% manual - spreadsheets, checklists, and hope. Every release was a gamble, and the team was drowning in regression testing that consumed entire sprints.
The company needed someone who could build a test automation framework from scratch, integrate it with their development workflow, and - perhaps most importantly - bring the existing manual testers along for the journey.
Within the first week, I had the first automated test running. Within a few months, we had a production-ready framework. The key was moving fast enough to prove value while building sustainably.
I architected and built a complete test automation framework using Playwright and TypeScript, integrating Git for version control and establishing patterns that the team could extend without my direct involvement.
The technical framework was only half the battle. The bigger challenge was human: transforming a team of manual testers into automation engineers.
I led a team of 5 (2 US-based, 3 offshore) and implemented a mentorship program focused on patience, clear communication, and psychological safety. The results spoke for themselves:
The company had a legacy C#/Selenium test suite that was slow and flaky. I led the migration to Playwright with TypeScript, improving test execution speed by 40% and dramatically reducing maintenance burden.
Why Playwright over Selenium? Native TypeScript support, built-in waiting mechanisms, and the fact that Microsoft's framework receives the latest improvements first. The decision has proven right - the team spends time writing tests, not debugging flaky locators.
The biggest lesson from CooperVision? The first test is the hardest - not technically, but politically.
Once leadership saw automation catch a real bug that would have made it to production, everything changed. Buy-in followed results. Investment followed buy-in. And suddenly, the team that had no automation was asking for more.
If you're building automation from scratch, focus on quick wins first. Prove value. Then scale.
Duration: August 2020 – Present
Location: San Diego Metropolitan Area
Role: Lead Software Engineer in Test (promoted from SDET in 2021)
Industry: Healthcare / Medical Devices
Contract SDET work for Meta, Blue Cross Blue Shield, and major enterprises
Building compliant test automation for the Department of Conservation
Pre-release testing for Apple Card and new product launches