What I build — at work, and on my own time.

Shift-left API testing

Built a contract-based acceptance testing practice, written before a feature is code-complete, so development validates against a production-ready test suite throughout implementation instead of finding gaps in a regression pass afterward. It wasn't an easy sell at first — developers were wary of QA working directly in the same repo, worried it would become a flaky gatekeeper slowing them down. Within two sprints that concern flipped: developers started actively pointing out how much faster issues were getting caught and resolved, and how much sharper the coverage was on business-rule and endpoint-level detail that used to slip through.

Performance testing platform

Stood up an engineering-owned performance testing platform on k6 and Jenkins with automated reporting, replacing a coordination-heavy process with self-service load testing any team can run on their own. A FY27 goal is scaling that further — bringing at least two more Shopping-portfolio teams onto k6 and shift-left testing, backed by Splunk APM for request-level visibility.

Architecture benchmarking

Used that platform to benchmark legacy and microservice architectures head to head, validating 63–99% latency reductions across key search endpoints and directly informing how we sequenced the production rollout.

Security & dependency management

Built proactive dependency vulnerability monitoring into CI pipelines, so remediation starts before a CVE becomes an org-wide advisory instead of after.

Mentoring

Mentoring an incoming intern whose team owns a business-rules microservice, walking them through the STLC end to end — how to scope a test plan, decide what's worth automating versus testing manually, and build the automation itself.

QA tooling enablement

Most QAs across the org don’t have the consumer and agent apps developers rely on for debugging set up, leaving them limited to logs and traces. A FY27 goal is closing that gap — either a written setup guide or a live session for the broader QA org (20–60 people) — so more QAs can debug with the same visibility developers have.