Role & seniority
- Strategic Testing Leader (8–10 years experience; broader work experience range: 10–15 years)
Stack/tools
- PTS (Project Scope documents)
- Confluence (Project Feature documents, where available)
- SharePoint (Test Data Management request submissions)
- UAT planning terminology: UAT1/UAT2, Unified Testing
- Artifacts/communication: testing status emails; coordination forums (e.g., SoS calls)
Top 3 responsibilities
- Oversee end-to-end (ETE) testing governance across projects/releases and ensure alignment with release objectives.
- Coordinate ETE need assessment and scenario readiness: review scope/feature docs, align with BAs/business sponsors, and finalize scenarios with testing teams.
- Drive readiness for execution: testbed criteria pull readiness (UAT1/UAT2), test data management preparation, and provide testing visibility via status emails during Unified Testing.
Must-have skills
- End-to-end testing governance and release-aligned test planning
- Cross-functional coordination (BAs, business sponsors, testing teams, project stakeholders)
- Defect/progress monitoring and quality ownership
- Ability to lead scenario sign-off and resolve blockers ahead of UAT
- Stakeholder communication and risk-based cadence calibration
Nice-to-haves
- Strong familiarity with project documentation workflows (PTS/Confluence)
- Experience managing test environments and data

Full Description

Job Requirements

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

Work Experience

10-15Years

Test Architect

Full Description