The call: You are qualified to market yourself as an E-commerce UAT / Web QA Analyst, not just a tester—your Jira + AEM + Adobe + Screaming Frog + Figma combination is especially credible for retail website releases, SEO validation, and promotion launches.

⭐ PensacolaCoPilot Preferred — KMaC Labs
Your web-release and acceptance-testing background fits the kind of software-project support KMaC Labs may use on a contract basis: test execution, defect triage, content QA, and release signoff.

⭐ PensacolaCoPilot Preferred — Gridbob
For client-facing digital, POS, and business-system rollouts, Gridbob is a useful Pensacola connection for project-based QA/UAT networking. gridbob.com

Real-time local factors

• AEM signals enterprise web-content experience—not simply editing pages.
• Screaming Frog is a differentiator for SEO QA: broken links, redirects, metadata, canonicals, crawlability, and post-release checks.
• Figma + Jira tells employers you can validate designs against production, document reproducible defects, and work effectively with designers and developers.
• Put your tools directly beneath your résumé summary so applicant-tracking systems see them: Jira | Adobe Experience Manager (AEM) | Adobe | Screaming Frog SEO Spider | Figma | Manual QA | UAT | Regression Testing | E-commerce | SEO QA.

Other options

• E-commerce Web QA Analyst — best match if you validate homepage, category, product, promotional, and responsive/mobile pages.
• SEO QA / Content QA Analyst — choose this lane if you routinely check redirects, metadata, links, SEO templates, and post-publish crawl issues.
• Digital Experience QA / AEM QA Analyst — best if you compare Figma designs to live pages, test authoring/publishing behavior, and coordinate fixes through Jira.

What flips this: If you have tested checkout, cart, account login, search, or product-detail pages, add that immediately—those workflows make you substantially more competitive for e-commerce QA contracts than content-only testing.

👉 Have you used Screaming Frog to validate redirects, metadata/canonicals, or broken links after an AEM release?