Job Title: Quality Engineering Test Architect (QE-TA)
FULL TIME Role
The Quality Engineering Test Architect (QE-TA) is a strategic testing leader responsible for overseeing and orchestrating end-to-end testing governance across projects and releases. The QE-TA serves as the central point of coordination between Business Analysts, Business Sponsors, Testing Teams, and Project Stakeholders, ensuring that testing activities are well-planned, properly executed, and aligned with release objectives. The QE-TA drives testing quality, monitors progress, delivers resolution, and produces key testing artifacts that support informed decision-making throughout the software delivery lifecycle.
Key Responsibilities
- Review the Project Scope document (PTS) and, where available, the Project Feature document in Confluence to determine whether End-to-End (E2E) testing is required.
- Where E2E testing is required:
- Coordinate and lead discussions with Business Analysts (BAs) and Business Sponsors to establish E2E testing scenarios.
- Ensure all impacted teams are identified early.
- Engage testing teams to finalize scenario steps and resolve outstanding questions before they become blockers.
- Target full E2E scenario sign-off and resolution of open questions at least one week before UAT/Unified Testing begins.
- Strategically coordinate the Testbed (TBED) critical path and ensure readiness by reminding testing teams to submit test scenarios within the required timelines.
- Manage Test Data Management (TDM) preparation by coordinating/submitting requests through the designated SharePoint site and ensuring test data is available before execution.
- Own and distribute Testing Status communications during Unified Testing based on project risk:
- Low-concern projects: Daily updates or weekly Project/Scrum of Scrums (SoS) communication.
- Medium/High-concern projects: Increased communication cadence and stakeholder updates.
- Champion testing readiness by sending timely reminders to testers before release start.
- Ensure user stories and test scripts are uploaded to the correct Zephyr Release Fix Version, aligned with the matching Fix Version in Jira.
- For non-Zephyr teams, provide direction to create test scripts in Excel format and provide the required Testing and Test Exit Report input documents.
- Monitor testing team progress and proactively identify schedule slippage that could impact release milestones.
- Own defect health in Jira, including aging defects, timely updates, and resolution tracking.
- Coordinate vendor/partner-related defects and ensure appropriate accountability is assigned.
- Establish a strong quality foundation by initiating Test Plan input during the first impacted Sprint.
- For Zephyr teams:
- Validate that the Zephyr Release aligns with the User Stories Fix Version.
- Ensure user stories and test scripts are successfully loaded into Zephyr and ready for execution.
- Lead the test closure phase by:
- Generating the Test Exit Report (TER) Readiness Checklist.
- Taking ownership of the Test Exit Report.
- Documenting the complete testing performed for the production release.
- Leverage Jira dashboards and targeted Jira queries to ensure all impacted Scrum teams are accounted for, including teams that join later in the project lifecycle.
Key Skills
Test Architecture | Quality Engineering | E2E Testing | Test Governance | UAT | Unified Testing | Test Planning | Test Data Management | Defect Management | Jira | Zephyr | Confluence | SharePoint | Agile/Scrum | Release Management | Test Exit Reports | Stakeholder Management
