Test automation · Quality engineering · Delivery confidence

Work history

Automation leadership grounded in delivery.

A selected record of building test systems, improving release feedback, and helping teams treat quality as an engineering capability—not a final checkpoint.

Role 01

Booz Allen Hamilton

Senior SDET / Test Automation Lead

to Present

Washington, DC

This role combines hands-on automation engineering with technical leadership in federal delivery environments. I lead framework direction and team execution while continuing to design UI and API tests, diagnose unreliable automation, integrate quality signals into CI/CD, and improve the systems teams use to make release decisions.

Selected engagements

U.S. Department of Veterans Affairs (VA) · Internal Revenue Service (IRS)

  • Led a team of five automation engineers, establishing scalable test strategies, resource planning, and automation standards.
  • Designed and documented Cypress and Playwright automation frameworks for UI and API testing with asynchronous handling, retry logic, and robust assertions.
  • Automated UI and API regression suites using Playwright tracing, network mocking, and auto-waiting to improve failure diagnostics and reduce flaky execution.
  • Built CI/CD pipelines with GitHub Actions and Cypress Dashboard, including artifact management, parallel execution, and dynamic environment provisioning.
  • Implemented automated defect triage through Jira API integration and risk-based failure prioritization.
  • Delivered automation training covering asynchronous execution, event-driven automation, and API-first testing approaches.
  • leadership
  • test strategy
  • cypress
  • playwright
  • framework architecture
  • api testing

Role 02

Chick-fil-A Corporate

Software Engineer in Test

to

Atlanta, GA

I focused on moving quality feedback earlier in the delivery lifecycle by treating automation as an engineering product rather than a collection of scripts. The work connected browser, API, visual, authentication, cloud-environment, and CI concerns into maintainable test systems that could provide faster and more useful release feedback.

  • Architected GitHub Actions CI/CD pipelines integrating Cypress Dashboard and AWS for automated execution and rapid feedback.
  • Designed modular smoke and regression suites with JavaScript, Cypress, and Mocha, including flaky-test mitigation.
  • Integrated Applitools Eyes visual regression testing across multiple resolutions, devices, and browsers.
  • Developed Cypress and Postman API suites with contract testing, schema validation, and dynamic data-driven assertions.
  • Implemented OIDC and Okta MFA automation in Cypress for SSO-based applications.
  • Applied parallel execution, network stubbing, and headless testing to reduce test run time while maintaining accuracy.
  • github actions
  • cypress
  • aws
  • cicd
  • javascript
  • mocha

Role 03

Ally Bank

Software QA Engineer

to

Sandy, UT

This role established the testing foundation that continues to shape my automation work: understanding business intent, designing risk-based coverage, investigating behavior across browsers and environments, communicating defects clearly, and partnering with delivery teams through release validation rather than treating testing as a final checkpoint.

  • Performed manual exploratory, functional, and regression testing of web applications across multiple platforms.
  • Created test plans, test cases, and acceptance criteria aligned with business and functional requirements.
  • Executed cross-browser and responsive UI testing on Chrome, Firefox, Safari, and Edge.
  • manual testing
  • exploratory testing
  • regression testing
  • test planning
  • requirements traceability
  • cross browser

Let’s talk

Need more confidence in the next release?

If you’re strengthening an automation strategy, modernizing a test framework, or scaling quality across teams, I’d be glad to compare notes.