{"schemaVersion":"jobsearcher.job.v1","id":"1bd97d2f5d76590c940b1909","url":"https://jobsearcher.com/jobs/1bd97d2f5d76590c940b1909","canonicalUrl":"https://jobsearcher.com/jobs/1bd97d2f5d76590c940b1909","title":"Test Architect","description":"Key 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.","company":"Hexaware Technologies","rawCompany":"hexaware technologies","city":"Denver","state":"CO","isRemote":false,"isActive":false,"createdAt":"2026-10-09T10:50:55.848Z","occupations":[{"code":"15-1253.00","title":"Software Quality Assurance Analysts and Testers","slug":"software-quality-assurance-analysts-and-testers"},{"code":"15-1299.09","title":"Information Technology Project Managers","slug":"information-technology-project-managers"},{"code":"13-1082.00","title":"Project Management Specialists","slug":"project-management-specialists"}],"industries":[{"code":"541511","title":"Custom Computer Programming Services","slug":"custom-computer-programming-services"},{"code":"541512","title":"Computer Systems Design Services","slug":"computer-systems-design-services"},{"code":"513210","title":"Software Publishers","slug":"software-publishers"}],"jobPosting":{"@context":"https://schema.org","@type":"JobPosting","title":"Test Architect","description":"Key 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.","datePosted":"2026-10-09T10:50:55.848Z","dateModified":"2026-10-09T10:50:55.848Z","hiringOrganization":{"@type":"Organization","name":"Hexaware Technologies","sameAs":"https://jobsearcher.com"},"jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"Denver","addressRegion":"CO","addressCountry":"US"}},"identifier":{"@type":"PropertyValue","name":"JobSearcher","value":"1bd97d2f5d76590c940b1909"},"url":"https://jobsearcher.com/jobs/1bd97d2f5d76590c940b1909"}}