Patrick Chau

Patrick Chau

QA Automation Engineer

Chicago, IL • Remote

I build quality that survives real users.

About Me

I'm a Quality Engineer who builds and implements QA processes that scale. I've partnered with engineering and product teams to define testing strategies, introduce automation where it creates leverage, and embed quality into day-to-day development.

My focus is practical systems with clear processes, fast feedback loops, and confidence at release time, not just more tests.

Quality is not proven by tests. It is earned through design and decisions.

How I Approach Quality

My approach is simple: catch the right risks early, and keep CI trustworthy.

Quality is designed in

Risk is made explicit in planning, not discovered in regression.

Signal over volume

Fast, meaningful feedback loops beat fragile, flaky test suites.

Automation as infrastructure

Stable selectors, clean POM, reliable test data, and CI pipelines teams trust.

Right checks at the right layer

API/contract tests for speed, UI tests for confidence, smoke tests for release readiness.

Operating model: risk review → layered checks (API + UI) → CI gates → release smoke → production validation.

What Teams Rely on Me For

Stabilizing Delivery

I help teams move from reactive fire-fighting to intentional, repeatable releases that everyone can trust.

Making Tradeoffs Visible

I surface what's at stake early so teams make confident go/no-go decisions before release pressure hits.

Building Lasting Infrastructure

I build testing systems that scale with the team, giving engineers ownership and making quality a shared responsibility.

Reducing Production Surprises

I reduce production surprises by tightening CI signal and validating the right paths before customers do.

Impact Highlights

Decision Velocity

Made quality and risk explicit early, enabling faster, more confident engineering and product decisions

Risk Reduction

Rebuilt testing strategy around risk and critical paths, dramatically reducing production surprises and regression churn

Infrastructure Trust

Transformed automation from brittle test suites into reliable delivery infrastructure that teams trusted and depended on

Strategic Leadership

Became the go-to quality leader for release decisions, risk tradeoffs, and system stability during high-pressure delivery moments

Mountain hiking journey

Selected Work

Univar (B2B E-commerce) — Playwright Automation Teams Trusted

Univar Solutions

Problem

Critical revenue flows (search, filters, PDP, quote requests, login) needed high-signal regression coverage across frequent releases. Existing checks were noisy and flaky and not consistently trusted in delivery.

What I Did

Owned risk-based automation strategy for critical paths and stabilized the suite so it behaved like release infrastructure, not "best-effort tests."

  • •Expanded coverage using Playwright + POM patterns for maintainability
  • •Triaged flaky failures and hardened selectors/waits to improve reliability
  • •Embedded runs into CI/CD (Azure DevOps + GitHub Actions) with artifacts for fast debugging
  • •Led cross-functional alignment on what "release-ready" meant, and made risk visible before deploy
  • •Validated content + UX across 27+ region/country variants and browsers

Tools

PlaywrightWebdriverIOJavaScriptPOMAzure DevOpsGitHub ActionsPostmanSQL

Result

Reduced regression effort by ~50% through higher-signal automation + stronger test planning, and increased confidence on high-impact customer journeys without slowing delivery.

Code:Private / proprietary

ePOD Mobile App — Built QA Process From Zero (First/Only QA)

Univar Solutions

Problem

React Native delivery app had no formal QA system (first/only QA). Releases depended on ad-hoc testing and tribal knowledge, increasing production risk.

What I Did

Built the QA foundation and release rhythm from scratch, acting as the quality owner for mobile delivery workflows.

  • •Created structured test cases, regression plans, and release checklists
  • •Implemented risk-based coverage for core flows (signatures, exceptions, sync/offline)
  • •Partnered with Product + Engineering to tighten acceptance criteria and surface risk early
  • •Ran device/platform validation across iOS + Android and ensured consistent release readiness

Tools

JiraFirebaseiOS/Android testingXcodeBrowserStackWebdriverIOAllure

Result

Established repeatable release confidence for mission-critical driver workflows, reducing last-minute scramble and improving clarity on what's risky and why.

Code:Private / proprietary

InsightUI Platform Rebuild — Cross-Squad Quality + Release Alignment

Sphera Solutions

Problem

Multiple Agile squads merged into shared environments, causing collisions (one squad breaking another). Regression became unpredictable, slowing delivery and creating friction.

What I Did

Created lightweight operating rhythm to reduce chaos and improve system-level quality.

  • •Initiated a QA/Dev sync to align merges, environments, and daily risk focus across squads
  • •Improved release coordination so testing validated decisions earlier (not after merges landed)
  • •Supported automation and regression strategy across squads with shared standards and visibility

Tools

Azure DevOpsJiraSelenium WebDriverCypressTestRailPostmanJavaScript

Result

Reduced environment collisions, improved shared awareness across squads, and strengthened release readiness through earlier risk surfacing and better coordination.

Code: Private / proprietary

Let's Connect

Open to quality engineering roles and conversations about building reliable software.

LinkedInEmail
GitHub
Resume