Test Architect

Hexaware; United States; On-site; USD 90,000 - 130,000; Full time

Job summary

Hexaware is seeking a QA/Test Lead to own the decision-making for End-to-End (ETE) testing and to review the Project Scope and Feature documents to determine testing requirements. You will coordinate with BAs and the Business Sponsor to establish a shared understanding of ETE scenarios and identify impacted teams early.

You will drive collaboration with testing teams to finalize scenario steps, ensure TBED readiness, manage Test Data via SharePoint, and publish the Testing Status email during

Responsibilities

• Take ownership of reviewing the Project Scope document (PTS) and, where available, the Project Feature document (Confluence) to determine if 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 BAs and the Business Sponsor to build a shared understanding of ETE scenarios and identify all impacted teams early.
• Bring testing teams into the discussion to collaboratively finalize scenario steps and clear outstanding questions before they become blockers.
• Target: full ETE scenario sign-off and outstanding questions resolved no later than one week before the start of UAT/Unified Testing.
• Strategically coordinate TBED readiness by reminding testing teams to submit for UAT1 and UAT2 environments in alignment with the Release Calendar.
• Drive Test Data Management (TDM) preparation by coordinating or submitting requests through the designated SharePoint site, ensuring test data is available before execution begins.
• Own and distribute the Testing Status email during Unified Testing— serving as the team's visibility anchor, calibrating communication frequency to the project's risk posture: Low concern projects: the day before or morning of the weekly Project/SoS call; Medium/High concern projects: increase cadence to reflect urgency and maintain stakeholder confidence.

Job description

Key Responsibilities

• Take ownership of reviewing theProject Scope document(in PTS) and, where available, theProject Feature document(in Confluence) to make an informed determination on whetherEnd-to-End (ETE) testingis required for the project.
• Where ETE testing is identified as necessary:
  • Proactively drive alignment by scheduling and leading conversations withBusiness Analysts (BAs)and theBusiness 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 resolvedno later than one week beforethe start of UAT/Unified Testing — setting the team up for a clean, confident testing entry.
  • Strategically coordinateTestbed (TBED) criteria pullreadiness by reminding testing teams to submit for UAT1 and UAT2 environments in alignment with theRelease Calendar— keeping the team ahead of critical timeline dependencies.
  • DriveTest 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 theTesting Status emailduringUnified 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 weeklyProject/Scrum of Scrums (SoS)call.
    • Medium/High concern projects:Increase communication cadence to reflect urgency and maintain stakeholder confidence.