Architect

Virtusa; Jacksonville (GA); On-site; USD 110,000 - 150,000; Full time

Job summary

Virtusa in the United States is seeking a strategic testing leader with 8–10 years of experience to oversee end-to-end testing governance across projects and releases. You will serve as the central point of coordination between Business Analysts, Sponsors, Testing Teams and Project stakeholders.

You will drive testing quality, monitor progress and defects, produce key artifacts, and ensure alignment with release objectives.

Qualifications

• 8 to 10 years of experience as a strategic testing leader responsible for end-to-end testing governance across projects and releases.
• Act as central point of coordination between Business Analysts, Business Sponsors, Testing Teams, and Project stakeholders to align testing with release objectives.
• Drives testing quality, monitors progress and defect resolution, and produces key testing artifacts to support decision-making.

Responsibilities

• Coordinate with BAs, sponsors, testing teams and stakeholders to align ETE testing across projects.
• Lead conversations to finalize ETE scenarios and resolve blockers before UAT.
• Ensure sign-off one week before UAT start; coordinate TBED readiness with Release Calendar.
• Oversee Test Data Management preparation and share status via testing status emails.
• Act as the team's visibility anchor and adjust communication cadence based on risk.

Skills

Strategic testing leadership

End-to-end testing governance

Stakeholder coordination

Testing artifacts production

Tools

Confluence

PTS

SharePoint

Job description

8 to 10 years of experience as a strategic testing leader responsible for overseeing and orchestrating end-to-end testing governance across projects and releases.

To serve 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.

Drives testing quality, monitors progress and defect resolution, and produces key testing artifacts that support informed decision-making throughout the software delivery lifecycle

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.