Enterprise Testing and Deployment Architect

Role: Enterprise Testing and Deployment Architect
Location : Hybrid Attendance 3/ Week from client office In Dallas/Irving, TX or Jacksonville, FL.

Duration: Expected minimum Duration Of 6 Months, W/ strong Possibility of extension
Must Have 7+ Yrs of closely applicable Work experience.

Qualification: Banking & Capital Marketing Industry Experience, Specifically In The Fraud Domain.

Responsibilities & Required Qualifications

• Own review of the Project Scope document (PTS) and Project Feature document (Confluence) to determine whether End-to-End (ETE) testing is required.
• Where ETE testing is required, schedule and lead alignment conversations with Business Analysts and the Business Sponsor to build shared understanding of ETE scenarios and identify all impacted teams early.
• Bring testing teams into scenario discussions to finalize steps and clear open questions before they become blockers, targeting full ETE scenario sign-off no later than one week before UAT/Unified Testing begins.
• Coordinate Testbed (TBED) criteria pull readiness, reminding teams to submit for UAT1/UAT2 environments in line with the Release Calendar.
• Drive Test Data Management (TDM) preparation, coordinating or submitting requests through the designated SharePoint site.
• Own and distribute the Testing Status email during Unified Testing, calibrating cadence to project risk (day-before/morning-of for low-concern projects; increased cadence for medium/high-concern projects).
• Send timely reminders to testers ahead of release start to upload user stories and test scripts to the correct Zephyr Release Fix Version aligned to the JIRA Fix Version; for non-Zephyr teams, direct testers to build Excel-based scripts using the Required Testing and Test Exit Report Input document.
• Monitor testing team progress for slippage risk and intervene early to protect release milestones.
• Oversee defect health in JIRA, tracking aging defects and driving resolution; for Vendor/Partner-owned defects, ensure accountability sits with the responsible internal developer contact.
• Initiate the Test Plan Input at the first impacted Sprint.
• For Zephyr-executing teams, validate that the Zephyr Release aligns with the User Stories Fix Version and that all stories/scripts are loaded and execution-ready.
• Lead closure: generate the TER Readiness Checklist and own creation of the Test Exit Report (TER), the release-level record of testing performed.
• Use the JIRA TA Dashboard / targeted JIRA queries to confirm all impacted Scrum Teams — including late joiners — are accounted for.
• Extensive experience in test management or test architecture roles on multi-team release programs.
• Deep familiarity with JIRA and Zephyr (or equivalent test management tooling), including fix-version alignment and dashboarding.
• Strong facilitation skills across business, testing, and delivery stakeholders.
• Experience producing release-level testing artifacts (Test Plan, TER Readiness Checklist, Test Exit Report).