QE Test Architect

Role: Quality Engineering (QE) Test Architect

Client: Citi

Work arrangement: Onsite

Job type: Full-time

Salary: Not specified

Eligibility requirements

Applicants must be U.S. citizens and hold an active Public Trust clearance. Applicants with other work authorizations are not eligible for this role.

Position overview

The QE Test Architect (QE-TA) is a strategic testing leader responsible for overseeing end-to-end testing governance across projects and releases. The QE-TA coordinates Business Analysts, Business Sponsors, testing teams, and project stakeholders to ensure testing is well planned, properly executed, and aligned with release objectives. The role drives testing quality, monitors progress and defect resolution, and produces key testing artifacts to support decision-making throughout the software delivery lifecycle.

Key responsibilities

• Review the Project Scope document in PTS and, where available, the Project Feature document in Confluence to determine whether end-to-end (ETE) testing is required.
• When ETE testing is required, lead discussions with Business Analysts and the Business Sponsor to align on ETE scenarios and identify impacted teams. Work with testing teams to finalize scenario steps and resolve open questions, targeting sign-off no later than one week before UAT / Unified Testing begins.
• Coordinate Testbed (TBED) criteria-pull readiness by reminding testing teams to submit requests for UAT1 and UAT2 environments in line with the Release Calendar.
• Coordinate or submit Test Data Management (TDM) requests through the designated SharePoint site so test data is ready before execution.
• Own and distribute the Testing Status email during Unified Testing, adjusting its frequency based on project risk.
• Remind testers before release start to upload user stories and test scripts to the correct Zephyr Release Fix Version, aligned with the corresponding JIRA Fix Version. For teams not using Zephyr, direct testers to create test scripts in Excel and provide the Required Testing and Test Exit Report Input document.
• Monitor testing progress, identify slippage, and intervene early to help teams meet release milestones.
• Oversee defect health in JIRA by tracking aging defects, prompting timely updates, and facilitating resolution. For defects requiring a vendor or partner fix, ensure the applicable Citi Developer is the primary point of contact.
• Initiate the Test Plan Input during the first impacted Sprint.
• For teams using Zephyr, validate that the Zephyr Release aligns with the User Stories Fix Version and that user stories and test scripts are loaded and ready for execution.
• Lead closure activities, including generating the TER Readiness Checklist and owning the Test Exit Report (TER), which documents testing performed for the project’s production release.
• Use the JIRA TA Dashboard or targeted JIRA queries to confirm all impacted Scrum Teams are accounted for, including teams that join later in the project lifecycle.

Certification or assessment requirement

TOGAF certification or a passing score on the Karat technical assessment at Technical Lead level (Java, Python, or Manual track) is required.