Career Highlight
Introducing QA at InQuicker
QA Lead / Customer Support — InQuicker / Stericycle
Built a lean quality practice for patient-facing healthcare software, making releases more predictable and reducing reactive post-release work.
The Starting Point
I joined as the first dedicated QA hire. Releases happened only every few months, and developers regularly had to respond to production issues because there was no dedicated testing function.
What I Changed
- Created the team’s initial QA processes and introduced a lean Agile quality workflow.
- Established acceptance criteria and test points for each feature and pull request.
- Made quality and risk visible earlier in the delivery process, before releases reached production.
- Partnered with product, engineering, customers, and external partners to investigate issues across systems and workflows.
Release Outcome
The team moved from infrequent, reactive releases to a reliable Monday deployment cadence. Planned validation replaced the recurring post-release fire drills that had previously pulled developers away from product work.
Testing Scope
Product Experience
UI and UX testing for patient-facing workflows, responsive web behavior, and release validation.
Data & Reporting
Report and data validation, including investigation of patient-availability discrepancies.
Integrations
Workflow and interoperability testing with Epic, athenahealth, NextGen, and eClinicalWorks, plus Twilio notification delivery.
Key Takeaway
The most effective quality improvement was not a heavyweight process. It was creating clear acceptance criteria, practical test coverage, and a predictable release rhythm that helped the team prevent issues instead of responding to them afterward.