68 → 30 DAYS
Regression cycle (man-days)
UP TO 7
QA/SDET engineers led
Led test automation strategy and changes for the a crucial component of a cloud-based compliance archiving service responsible for more than 70% of the company's revenue, leading up to 4 teams and 7 QA analysts and test engineers.
The component's regression cycle was mission-critical, and as such took up to 68 man-days to run by hand. This meant that the QA team was almost constantly stuck in regression testing, while the release cycle was slowed.
Drove the automation roadmap for the component, cutting the regression testing cycle from 68 to 30 man-days.
Designed the service-level and end-to-end integration test frameworks for a new microservices-based product, and owned integration testing across the suite.
Introduced API sanity test suites to catch third-party schema changes within a sprint — instead of customers discovering them in production months later.
Led up to 4 teams and 7 QA/SDET engineers simultaneously; interviewed candidates, ran performance reviews, and mentored junior/intermediate staff.
Formalized quality and release processes for the team and drove company-wide onboarding improvements.
Have a similar problem?
Let’s talk about what’s slowing your team down.
Based in Vancouver, BC, working with clients locally and remotely. Usually respond within one business day.