CooperVision: From Zero Automation to 300% Test Coverage
How I built a Playwright framework from scratch and transformed a manual QA team
Building compliant test automation for the Department of Conservation
Concluded:
See it liveGovernment projects move slowly for a reason. When you're building systems that monitor oil and gas operations across California, "move fast and break things" isn't just a bad idea - it's potentially dangerous and legally non-compliant.
Through OnCore Consulting, I led QA automation efforts for the California State Department of Conservation. The project involved building a web application for monitoring and auditing oil and gas manufacturers - a system that required extensive documentation, regulatory compliance, and bulletproof reliability.
Government QA taught me a different rhythm than private sector work:
I architected, designed, and delivered CI/CD-integrated test automation solutions using Java, Selenium, Maven, TestNG, and Azure DevOps. The focus was on reliability and traceability rather than just speed.
Government work taught me that speed and quality aren't always trade-offs. When you invest in proper documentation, naming conventions, and process rigor, you actually move faster in the long run - because you spend less time debugging and more time delivering.
The skills I developed here - working with regulated industries, maintaining audit trails, and building for compliance - translate directly to healthcare, finance, and any sector where reliability isn't optional.
Duration: April 2019 – August 2020
Location: Greater Sacramento Area
Role: Software Engineer in Test (promoted from QA Automation Engineer)
Client: California State Department of Conservation
How I built a Playwright framework from scratch and transformed a manual QA team
Contract SDET work for Meta, Blue Cross Blue Shield, and major enterprises
Pre-release testing for Apple Card and new product launches