Software quality engineer. I build the automation frameworks other people test with.

I have spent 10+ years making sure software actually works before it reaches users — not by standing at the end of the line catching problems, but by getting into the process early enough to prevent them. My background covers UI and API automation, CI/CD pipeline integration, accessibility testing, and coaching engineering teams on how to own their own test coverage. I care about building quality infrastructure that lasts.

Currently based in Chandler, AZ and working remotely.

Automation       Cypress · Applitools · Playwright (actively learning)
API Testing      Postman · REST · JSON/XML contract validation
CI/CD            TeamCity
Observability    Splunk · New Relic · AWS CloudWatch · OpenSearch
Cloud            AWS (EC2 · S3 · Lambda · CloudWatch)
Accessibility    axe browser extension · WCAG 2.x
Browser Tools    Chrome DevTools
Version Control  Git · GitHub
Languages        JavaScript · SQL
Defect Tracking  Jira · Confluence
Process          Agile/Scrum · Shift-Left · Risk-Based Testing · Root Cause Analysis

Imagine Learning · Tempe, AZ (Remote) · Jan 2025 – Sep 2025

I worked directly with product engineering squads on a web and mobile education platform used by students across the country. The part of this role I found most meaningful was the work upstream — sitting in sprint planning, asking the questions that exposed gaps in requirements before anyone wrote a line of code, and helping developers understand what "testable" actually means when you're designing a feature.

• Designed and maintained Cypress end-to-end automation
• Conducted accessibility testing using the axe browser extension against WCAG 2.x standards
• Used New Relic and AWS CloudWatch to monitor production signals and translate real traffic patterns into targeted test coverage improvements
• Mentored junior QA engineers on automation patterns and test design strategy
• Started exploring AI-assisted test generation tools to reduce maintenance overhead on large test suites

Imagine Learning · Tempe, AZ (Remote) · Apr 2022 – Jan 2025

This is where a lot of my framework thinking matured. I learned that the difference between an automation suite that helps a team and one that slows them down is almost entirely in the architecture decisions made early — selector strategy, test isolation, data management. I spent three years getting those things right.

• Maintained and expanded Cypress automation across UI and API layers
• Performed exploratory and edge-case testing alongside automation — knowing when a script can find something and when human judgment is the better tool
• Used Chrome DevTools to debug front-end failures at the root cause level, not just the symptom
• Collaborated with product managers and developers on acceptance criteria during refinement — consistently earlier in the cycle than most QA engineers tend to show up

Imagine Learning · Tempe, AZ · Aug 2019 – Apr 2022

My first senior role at Imagine Learning. This is where I shifted from executing tests to owning the strategy behind them — deciding what to test, in what order, at what risk threshold, and how to communicate that posture to people who aren't QA engineers.

• Led testing across multiple feature areas: wrote comprehensive test plans and cases, set coverage strategy based on risk, maintained quality documentation through each release cycle
• Applied root cause analysis to recurring defect patterns and brought findings to engineering with specific corrective action recommendations
• Built relationships with engineers and product managers that made it easy to have honest conversations about quality tradeoffs before they became release-day decisions

PDS, Inc. — Imagine Learning · Tempe, AZ · Feb 2019 – Aug 2019

Contract role that converted to the full-time Senior QA position above. Joined an Agile squad mid-stream and contributed to sprint ceremonies, requirement reviews, and defect tracking from day one.

Infusionsoft (now Thryv) · Chandler, AZ · Jun 2012 – Feb 2019

Nearly seven years at a fast-growing SaaS CRM company. This is where I built my foundation in API testing and learned what it means to maintain automation at scale over a long period of time — not just building it, but keeping it accurate and useful as the product changes.

• Built and maintained an automated API test suite validating RESTful and XML-RPC contract behavior — JSON and XML validation, authentication flows, error handling — integrated into CI so regressions surfaced before code merged
• Wrote SQL queries to validate backend data integrity alongside API tests
• Monitored Splunk logs daily as part of the testing workflow, using production data to find gaps in pre-release coverage
• Applied root cause analysis to recurring defect patterns — moving conversations from "we found a bug" to "here is why this keeps happening"
• Coached junior QA team members on test design, automation patterns, and how to write defect reports that developers can actually act on

A few things I believe that shape how I work:

Quality belongs in the conversation before a line of code is written. The most expensive defects are the ones that could have been caught in a requirements review. Getting into planning early isn't extra work — it's the highest-leverage thing a QA engineer can do.

Automation is infrastructure, not a checklist. A test suite that nobody trusts is worse than no test suite. The architecture decisions made early — selector strategy, test isolation, data management, folder structure — determine whether automation helps a team or slows it down six months later.

The best metric is whether developers trust the results. If engineers are overriding failing tests or ignoring the CI output, something has gone wrong. Test reliability is not a nice-to-have.

Mentoring is part of the job. A QA engineer who hoards knowledge isn't actually making the product better. The goal is to raise the quality instincts of everyone on the team, not just to catch what they miss.

Currently open to remote QA engineering and SDET roles OR in-person or hybrid QA Engineering and SDET roles in the Phoenix area. If you're building something that needs to work reliably and you want someone who cares about the architecture behind that, let's talk.