Holistic approach
System-thinking QA that traces seams from design reviews, planning cadences, usability research, automation frameworks, and release playbooks so the entire lifecycle stays observable and accountable.
I'm that QA engineer/SDET who turns bugs into features and creates Cypress and Playwright plugins that actually make sense. When I'm not breaking things professionally, I'm probably writing about it.
Holistic approach
System-thinking QA that traces seams from design reviews, planning cadences, usability research, automation frameworks, and release playbooks so the entire lifecycle stays observable and accountable.
Results driven
Define success metrics before automation starts, wire suites to those signals, and retire tests once they stop preventing real-world regressions.
Curious & quirky
Prototype offbeat ideas, name labs after cult films, and publish the takeaways as plugins or articles so teams stay playful while chasing reliability.
More than two decades across product, support, and engineering shaped this user-centric, positively skeptical, results-driven QA leader.
I’ve worn almost every hat: analyst, developer, SW engineer, consultant, technical product lead, product manager,and now Staff QA/SDET. Every role tuned another sense, strategic empathy, system-thinking, system-level debugging, and a strong bias for measurable outcomes.
QA became the place where user interviews, service metrics, and code-level debugging intersect. So every experiment starts with real customer context and ends with measurable impact.
"Optimism is allowed. Blind faith is not. I choose positive skepticism every single sprint."
What sets me apart is that I’ve lived each stop in the software lifecycle: requirements, design, build, release, and support. I know how a product must feel for users, how it has to behave for engineering, and how it needs to perform for the business. I bring that full-cycle empathy into QA so teams ship software that not only works but stays loved in production.
Designing frameworks that survive reorganizations, flaky APIs, and vendor musical chairs.
Scenario labs where engineers, designers, and support rehearse unexpected user journeys before they become incidents.
Blog posts, and plugins that turn hard lessons into shared shortcuts.
I write to untangle weird bugs, decode surprising signals, and demystify how teams ship dependable software.
View All ArticlesLoading articles...
Article spotlight
Newsletters, podcasts, and curated digests that amplified these experiments.
A running log of every time the blog wandered beyond dev.to—because good ideas deserve new audiences (and better jokes).
Useful automation helpers (Accessibility, Schema Validation, and other friends) built to remove toil.
View on NPMLoading plugins...
Have a question about testing, automation, or accessibility? Let’s swap notes.
Portland, OR
Staff QA Engineer/SDET keeping teams curious & accountable
Computer Science Engineer
Universidad de Sevilla