ATTORNEY — LARGE LOSS / EXCESS

KHYATHI INFORMATICS LLC; Philadelphia (Philadelphia County); On-site; USD 150,000 - 190,000; Full time

Job summary

KHYATHI INFORMATICS LLC is seeking a QE Test Architect for 100% onsite work in multiple US locations (Irving, TX / Jacksonville, FL / Tampa, FL). The role leads end-to-end testing governance across projects and releases, coordinating between analysts, sponsors and testing teams to ensure quality and timely delivery.

The ideal candidate will have 12+ years in testing leadership within banking, TOGAF certification or Karat assessment, and ability to drive testing artifacts and decision-ready

Qualifications

• 12+ years of experience in QA/testing within banking or financial services.
• Active Public Trust clearance eligibility; US citizens only; no sponsorship.
• TOGAF certification or Karat technical assessment, at Lead level with Java/Python or manual track.

Responsibilities

• Review project scope and determine need for End-to-End testing.
• Lead discussions with Business Analysts and sponsor to define ETE scenarios.
• Coordinate Testbed readiness and environment alignment with release calendar.
• Drive Test Data Management preparation so data is ready before execution.
• Own and distribute Testing Status communications during Unified Testing.
• Ensure all test scripts, user stories and Fix Versions are correctly aligned in JIRA/Zephyr.

Skills

ETE testing governance

Stakeholder coordination

Test planning

Risk assessment

Education

TOGAF certification

Tools

JIRA

Zephyr

Confluence

Job description

A client of ours is Hiring for an \"QE Test Architect\" Full-Time Onsite role in Irving, TX / Jacksonville, FL / Tampa, FL locations.100% On-Site

Required Domain or Industry:Banking

ELIGIBILITY STRICT: US Citizens with an active Public Trust clearance. Unfortunately no sponsorship is provided.

Experience: 12+years

CERTIFICATION / ASSESSMENT REQUIREMENT

TOGAF certification OR a pass on the Karat technical assessment at

Technical Lead level (Java, Python or Manual track).

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 is the central point of coordination between Business Analysts, Business Sponsors, testing teams and project stakeholders, ensuring testing is well planned, properly executed and aligned with release objectives. The role drives testing quality, monitors progress and defect resolution, and produces the key testing artifacts that 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.


• - Where ETE testing is required: schedule and lead conversations with Business Analysts and the Business Sponsor to build a shared understanding of ETE scenarios and identify all impacted teams early; bring testing teams in to finalize scenario steps and clear open questions; target full ETE scenario sign-off and resolved questions no later than one week before the start of UAT / Unified Testing.


• - Coordinate Testbed (TBED) criteria pull readiness by reminding testing teams to submit for UAT1 and UAT2 environments in line with the Release Calendar.


• - Drive Test Data Management (TDM) preparation by coordinating or submitting requests through the designated SharePoint site, so test data is ready before execution begins.


• - Own and distribute the Testing Status email during Unified Testing, calibrating frequency to project risk (low-concern projects: the day before or morning of the weekly Project / Scrum of Scrums call; medium/high-concern projects: increased cadence).


• - Send timely reminders to testers before release start to upload user stories and test scripts to the correct Zephyr Release Fix Version, aligned to the matching Fix Version in JIRA. For non-Zephyr teams, direct testers to build test scripts in Excel and provide the Required Testing and Test Exit Report Input document.


• - Monitor testing team progress for any slippage and intervene early so testers have the time and support needed to meet release milestones.


• - Oversee defect health in JIRA: track aging defects, drive timely updates and facilitate resolution. For defects tied to a vendor or partner fix, ensure accountability sits with the applicable as per client Developer as the primary point of 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 user stories and test scripts are loaded and ready for execution.


• - Lead the closure phase: generate the TER Readiness Checklist and own the Test Exit Report (TER), the release-level document describing the 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 engaged later in the project lifecycle, so no testing effort goes undocumented.