Quality Assurance Engineer

Release confidence through pragmatic testing and automation.

QA engineer with 8 years of experience across manual testing, exploratory testing, and UI/API automation for web, mobile, and desktop applications. I work closely with engineering and product to reduce regressions, clarify requirements, and keep releases moving.

View Resume LinkedIn

Reno, NV • Remote

Experience

Highlights from roles where I owned testing, quality, and release readiness.

Quality Assurance Engineer

Worth AI • Remote • Oct 2025 – Present

  • Own release confidence across multiple product areas through risk-based testing and tight feedback loops with engineering and product.
  • Build and maintain Playwright automation for critical workflows and integrate checks into CI to reduce regressions.
  • Validate complex onboarding and decisioning behavior across UI and APIs using Postman and data-level verification.
  • Drive pragmatic QA improvements: regression coverage, test organization, and clearer defect reporting.

QA Automation Engineer

Castiron • Remote • Aug 2022 – Sep 2025

  • Developed and maintained automated UI and API test coverage using Playwright for key workflows across customer-facing web applications.
  • Integrated automated checks into GitHub Actions to support frequent deployments and reduce manual effort.
  • Executed exploratory and regression testing for high-risk features requiring broader coverage.
  • Partnered with engineering and design to clarify edge cases and reduce ambiguity in requirements.

Quality Assurance Engineer

Bottomline Technologies • Remote • Feb 2022 – Jul 2022

  • Built Cypress tests to establish baseline coverage for high-priority workflows in a legacy payments platform.
  • Defined coverage and ran manual tests validating UI behavior and backend data through API calls.
  • Led sprint planning and standups while managing test execution and defect triage.

Software QA Lead

TrainerRoad • Reno, NV (Hybrid) • Apr 2019 – Feb 2022

  • Managed QA across web, desktop, and mobile platforms, leading a team of 10 through weekly release cycles.
  • Migrated 500+ test cases from spreadsheets to TestRail and standardized test structure.
  • Guided transition from GitHub to Jira, reducing triage time by 30%.
  • Expanded E2E coverage using Cypress, Detox, and Selenium.

Software QA Analyst

TrainerRoad • Reno, NV • Sep 2017 – Apr 2019

  • Created and executed manual test cases across iOS, Android, Windows, Mac, and web.
  • Validated features against specs and surfaced issues early through exploratory testing.
  • Maintained test data, tracked bugs, monitored builds, and ran basic SQL/API checks.

Skills

Tools and practices I reach for in day-to-day QA work.

Automation

Playwright, Cypress, Detox, Selenium, TypeScript, Git, GitHub

Testing

Exploratory testing, regression testing, risk-based testing, cross-platform testing, test planning

API and Data

Postman, REST API testing, SQL validation, JMeter

Process

Defect triage, release support, Agile/Scrum, CI/CD integration (GitHub Actions)

Projects

Frameworks I implemented to improve coverage and release confidence.

Playwright E2E Framework

Castiron • End-to-end automation foundation for critical workflows

What I built
  • A maintainable Playwright framework for high-signal, end-to-end coverage.
  • Reusable helpers for auth, test data setup, and stable selectors to reduce flake.
  • CI integration with GitHub Actions for fast feedback during frequent deploys.
Why it mattered
  • Reduced manual regression overhead and improved confidence in core flows.
  • Made failures more actionable with consistent structure and clearer reporting.
Playwright TypeScript GitHub Actions E2E

Cypress UI Testing Framework

Bottomline • Baseline automation for a legacy payments platform

What I built
  • Introduced Cypress tests to cover high-priority workflows and reduce regressions.
  • Conventions for selectors, test structure, and readable assertions to keep tests stable.
  • Coverage aligned to risk areas to complement manual validation for releases.
Why it mattered
  • Established a foundation that made automated regression practical on a legacy system.
  • Improved repeatability and reduced reliance on “tribal knowledge” testing.
Cypress JavaScript UI Automation Regression

Contact

Send a message and I will get back to you.

Or email me at geoffreymajor@gmail.com.