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
I find root causes, not symptoms. Automation that lasts, bug reports that need zero follow-up questions.
profile.spec.ts PASS 4 passed, 0 failed
How I work
Six habits that show up in everything I ship.
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.
Clear repro, device/OS/build, evidence, and a root-cause hypothesis, so the person fixing it starts fixing, not investigating.
Trade-offs and risks laid out, then the smallest, lowest-blast-radius fix recommended first. Decisions, not just findings.
Real failures separated from noise. CI digests and targeted retries for genuinely flaky steps keep the green/red meaningful.
Tests ready before the meeting, scope matched to team bandwidth, and every item tracked to done. Nothing left dangling.
Standardized conventions, remediation tickets, contract validation, and security gates so the same class of bug does not recur.
Day to day
The work behind the outcomes, abstracted from real engagements.
Toolbox
Grouped by job. No invented proficiency scores, just what I use.