Root cause, not symptom
I chase failures to their origin instead of papering over the surface. A fix that treats the cause holds; one that treats the symptom comes back.
QA Engineer · SDET
Hi, I'm Patricio
I find root causes, not symptoms. Automation that lasts, bug reports that need zero follow-up questions.
Testing since 2017.
root causes, not symptoms How I work
Quality is a way of working, not a phase at the end.
Six habits that show up in everything I ship.
Bug reports engineers act on now
Clear repro, device/OS/build, evidence, and a root-cause hypothesis — so the person fixing it starts fixing, not investigating.
Options + a clear recommendation
Trade-offs and risks laid out, then the smallest, lowest-blast-radius fix recommended first. Decisions, not just findings.
Trustworthy signal
Real failures separated from noise. CI digests and targeted retries for genuinely flaky steps keep the green/red meaningful.
Closes the loop
Tests ready before the meeting, scope matched to team bandwidth, and every item tracked to done — nothing left dangling.
Prevention over patches
Standardized conventions, remediation tickets, contract validation, and security gates so the same class of bug does not recur.
Day to day
What I actually do
The work behind the outcomes — abstracted from real engagements.
Test automation (API + E2E)
Failure triage & root-cause analysis
Release readiness / RC validation
Cross-platform mobile + web parity
API contract & schema validation
CI health & visibility
Quality signal & trend reporting
Security & dependency (CVE) scanning
Cross-team QA ↔ dev ↔ client coordination
Toolbox
Tools I reach for
Grouped by job. No invented proficiency scores — just what I use.
Automation & E2E
PlaywrightCypressAppiumSeleniumWebdriverIO
API & Contracts
PostmanREST AssuredPactOpenAPIJSON Schema
CI/CD
GitHub ActionsGitLab CIJenkinsDocker
Languages
TypeScriptJavaScriptPythonJava
Web
HTMLCSSChrome DevTools
Observability & Debug
GrafanaKibanaSentryCharles Proxy
Security
OWASP ZAPSnykDependabotTrivy