Test Architect

HEXAWARE • United States,

8h

About The Position

The Test Architect will take ownership of reviewing project scope and feature documents to determine the necessity of End-to-End (ETE) testing. When ETE testing is required, this role will proactively drive alignment by leading discussions with Business Analysts and the Business Sponsor to establish a shared understanding of ETE scenarios and identify all impacted teams. The Test Architect will also bring testing teams into the discussion to collaboratively finalize scenario steps and resolve any outstanding questions before they become blockers. The goal is to achieve full ETE scenario sign-off and resolve open questions at least one week before the start of UAT/Unified Testing. Additionally, this role will strategically coordinate Testbed (TBED) criteria pull readiness by reminding testing teams to submit for UAT1 and UAT2 environments in alignment with the Release Calendar. The Test Architect will also drive Test Data Management (TDM) preparation by coordinating or submitting requests through the designated SharePoint site, ensuring test data is available before execution begins. During Unified Testing, the Test Architect will own and distribute the Testing Status email, calibrating communication frequency based on the project's risk posture.

Requirements

• Review Project Scope document (in PTS)
• Review Project Feature document (in Confluence)
• Determine necessity of End-to-End (ETE) testing
• Lead conversations with Business Analysts (BAs) and Business Sponsor
• Build shared understanding of ETE scenarios
• Identify all impacted teams
• Collaborate with testing teams to finalize scenario steps
• Resolve outstanding questions
• Achieve full ETE scenario sign-off
• Coordinate Testbed (TBED) criteria pull readiness
• Remind testing teams to submit for UAT1 and UAT2 environments
• Align with Release Calendar
• Drive Test Data Management (TDM) preparation
• Coordinate or submit TDM requests via SharePoint
• Ensure test data availability before execution
• Own and distribute Testing Status email during Unified Testing
• Calibrate communication frequency based on project risk posture

Responsibilities

• Take ownership of reviewing the Project Scope document (in PTS) and, where available, the Project Feature document (in Confluence) to make an informed determination on whether End-to-End (ETE) testing is required for the project.
• Where ETE testing is identified as necessary, proactively drive alignment by scheduling and leading conversations with Business Analysts (BAs) and the Business Sponsor — building a shared understanding of ETE scenarios and ensuring all impacted teams are identified early.
• Bring testing teams into the discussion to collaboratively finalize scenario steps and clear any outstanding questions before they become blockers.
• Target: Full ETE scenario sign-off and open questions resolved no later than one week before the start of UAT/Unified Testing — setting the team up for a clean, confident testing entry.
• Strategically coordinate Testbed (TBED) criteria pull readiness by reminding testing teams to submit for UAT1 and UAT2 environments in alignment with the Release Calendar — keeping the team ahead of critical timeline dependencies.
• Drive Test Data Management (TDM) preparation by coordinating or submitting requests as applicable through the designated SharePoint site, ensuring test data is available and ready before execution begins.
• Own and distribute the Testing Status email during Unified Testing — serving as the team's visibility anchor.
• Calibrate communication frequency to the project's risk posture: Low concern projects: Send the day before or morning of the weekly Project/Scrum of Scrums (SoS) call. Medium/High concern projects: Increase communication cadence to reflect urgency and maintain stakeholder confidence.

What This Job Offers

• Job Type: Full-time
• Career Level: Senior
• Education Level: No Education Listed