
Chicago, IL • Remote
I build quality that survives real users.
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.
My approach is simple: catch the right risks early, and keep CI trustworthy.
Risk is made explicit in planning, not discovered in regression.
Fast, meaningful feedback loops beat fragile, flaky test suites.
Stable selectors, clean POM, reliable test data, and CI pipelines teams trust.
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.
I help teams move from reactive fire-fighting to intentional, repeatable releases that everyone can trust.
I surface what's at stake early so teams make confident go/no-go decisions before release pressure hits.
I build testing systems that scale with the team, giving engineers ownership and making quality a shared responsibility.
I reduce production surprises by tightening CI signal and validating the right paths before customers do.
Made quality and risk explicit early, enabling faster, more confident engineering and product decisions
Rebuilt testing strategy around risk and critical paths, dramatically reducing production surprises and regression churn
Transformed automation from brittle test suites into reliable delivery infrastructure that teams trusted and depended on
Became the go-to quality leader for release decisions, risk tradeoffs, and system stability during high-pressure delivery moments

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."
Tools
Result
Reduced regression effort by ~50% through higher-signal automation + stronger test planning, and increased confidence on high-impact customer journeys without slowing delivery.
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.
Tools
Result
Established repeatable release confidence for mission-critical driver workflows, reducing last-minute scramble and improving clarity on what's risky and why.
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.
Tools
Result
Reduced environment collisions, improved shared awareness across squads, and strengthened release readiness through earlier risk surfacing and better coordination.
Code: Private / proprietary