Other

QE Test Architect

Techridge, Inc.Tampa, FL🇺🇸United StatesPosted Oct 7, 2026

Quick Overview

Seniority

Mid Senior

Work mode

On Site

Location

Tampa, FL, United States

Posted

16 hours ago

ScrumConfluenceJavaJiraPython

Job Description

Job Title: QE Test Architect

Location: Irving, TX / Jacksonville, FL / Tampa, FL(Onsite)

Position Type: Fulltime Opportunity

Job Description:

The QE Test Architect (QE-TA) is a strategic testing leader responsible for overseeing end-to-end testing governance across projects and releases. The QE-TA is the central point of coordination between Business Analysts, Business Sponsors, testing teams and project stakeholders, ensuring testing is well planned, properly executed and aligned with release objectives. The role drives testing quality, monitors progress and defect resolution, and produces the key testing artifacts that support decision-making throughout the software delivery lifecycle.

Key Responsibilities:

Review the Project Scope document (in PTS) and, where available, the Project Feature document (in Confluence) to determine whether End-to-End (ETE) testing is required.
Where ETE testing is required: schedule and lead conversations with Business Analysts and the Business Sponsor to build a shared understanding of ETE scenarios and identify all impacted teams early; bring testing teams in to finalize scenario steps and clear open questions; target full ETE scenario sign-off and resolved questions no later than one week before the start of UAT / Unified Testing.
Coordinate Testbed (TBED) criteria pull readiness by reminding testing teams to submit for UAT1 and UAT2 environments in line with the Release Calendar.
Drive Test Data Management (TDM) preparation by coordinating or submitting requests through the designated SharePoint site, so test data is ready before execution begins.
Own and distribute the Testing Status email during Unified Testing, calibrating frequency to project risk (low-concern projects: the day before or morning of the weekly Project / Scrum of Scrums call; medium/high-concern projects: increased cadence).
Send timely reminders to testers before release start to upload user stories and test scripts to the correct Zephyr Release Fix Version, aligned to the matching Fix Version in JIRA. For non-Zephyr teams, direct testers to build test scripts in Excel and provide the Required Testing and Test Exit Report Input document.
Monitor testing team progress for any slippage and intervene early so testers have the time and support needed to meet release milestones.
Oversee defect health in JIRA: track aging defects, drive timely updates and facilitate resolution. For defects tied to a vendor or partner fix, ensure accountability sits with the applicable Citi Developer as the primary point of contact.
Initiate the Test Plan Input at the first impacted Sprint.
For Zephyr-executing teams, validate that the Zephyr Release aligns with the User Stories Fix Version and that all user stories and test scripts are loaded and ready for execution.
Lead the closure phase: generate the TER Readiness Checklist and own the Test Exit Report (TER), the release-level document describing the testing performed for the project's production release.
Use the JIRA TA Dashboard or targeted JIRA queries to confirm all impacted Scrum Teams are accounted for, including teams that engaged later in the project lifecycle, so no testing effort goes undocumented.