TEST ARCHITECT L1(CONTRACT)

Wipro; Irving (TX); Vor Ort; USD 80.000 - 158.000; Vollzeit

Zusammenfassung

Wipro Limited in Irving, TX seeks a Quality Engineering Test Architect (QE-TA) to oversee end-to-end testing governance across projects and releases. You will coordinate with BAs, Business Sponsors, testing teams, and stakeholders to ensure testing is well-planned, executed, and aligned with release objectives.

The role drives testing quality, tracks progress and defects, and produces key testing artifacts to support decision-making throughout the software delivery lifecycle.

Qualifikationen

• Quality Management experience required.
• 8–10 years of relevant experience stated.
• Familiarity with testing governance and release processes.

Aufgaben

• Oversee end-to-end testing governance across projects and releases.
• Coordinate between Business Analysts, Testing Teams and stakeholders.
• Lead test planning, data management, and defect tracking activities.
• Ensure timely testing artifacts and readiness for releases.

Kenntnisse

Quality Management

End-to-End testing

Test governance

Stakeholder coordination

Tools

JIRA

Zephyr

Confluence

Jobbeschreibung

Wipro Limited (NYSE: WIT, BSE: 507685, NSE: WIPRO) is a leading technology services and consulting company focused on building innovative solutions that address clients’ most complex digital transformation needs. Leveraging our holistic portfolio of capabilities in consulting, design, engineering, and operations, we help clients realize their boldest ambitions and build future-ready, sustainable businesses. With over 230,000 employees and business partners across 65 countries, we deliver on the promise of helping our customers, colleagues, and communities thrive in an ever-changing world. For additional information, visit us at www.wipro.com.

Job Description

Role Purpose

The purpose of this role to analyse client technology environments, create low-level design inputs, and integrate technology components to existing client environment for a specific technology.

Area of Responsibility

• Requirement Analysis-Participate in client discussions to gather information regarding platform constraints, technology stacks, and performance expectations of a specific technology.
• Designing-Create low-level design inputs for assigned technology and provides technical viewpoints for specific components as per the standards and best practices.
• Integration assessment and support-Assess and evaluate client technology environment to support integration of technology components and ensure system-level technical compatibility.
• Troubleshooting-Support testing activities for technology components and work with developers and infrastructure teams to troubleshoot errors during deployment phases.

The Quality Engineering Test Architect (QE-TA) is a strategic testing leader responsible for overseeing and orchestrating end-to-end testing governance across projects and releases. The QE-TA serves 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. The QE-TA drives testing quality, monitors progress and defect resolution, and produces key testing artifacts that support informed decision-making throughout the software delivery lifecycle.

Key Responsibilities

• 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) testing is 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 before the start of UAT/Unified Testing — setting the team up for a clean, confident testing entry.
• Strategically coordinateTestbed (TBED) criteria pull readiness 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 email duringUnified 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.
• Champion testing readiness by sending timelyreminders to testers prior to the release start, ensuring user stories and test scripts are uploaded to the correctZephyr Release Fix Version — aligned to the matching Fix Version in JIRA.
• Fornon-Zephyr teams, provide clear direction by notifying testers to build their test scripts in Excel format and equipping them with theRequired Testing and Test Exit Report Input document — ensuring no team is left without a clear path forward.
• Maintain a sharp eye ontesting team progress, actively monitoring for any signs of slippage that could jeopardize completion timelines. Intervene early and decisively to ensure testers have the time and support needed to meet release milestones.
• Overseedefect health in JIRA — tracking aging defects, driving timely updates, and facilitating resolution with a sense of urgency. For defects tied to aVendor or Partner fix, ensure accountability is correctly placed with the applicableCiti Developer serving as the primary point of contact.
• Establish a strong quality foundation by initiating theTest Plan Input at thefirst impacted Sprint — setting the tone for structured, disciplined testing from the outset.
• ForZephyr-executing teams, validate that:
• The Zephyr Release aligns with theUser Stories Fix Version.
• All user stories and test scripts are successfullyloaded into Zephyr and ready for execution.
• Lead the closure phase with rigor — generate theTER Readiness Checklist and take full ownership of creating theTest Exit Report (TER), a Release-level document that tells the complete story of testing performed for the project's production release.
• Leverage theJIRA 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 that no testing effort goes undocumented or unvalidated.

The Quality Engineering Test Architect (QE-TA) is a strategic testing leader responsible for overseeing and orchestrating end-to-end testing governance across projects and releases. The QE-TA serves 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. The QE-TA drives testing quality, monitors progress and defect resolution, and produces key testing artifacts that support informed decision-making throughout the software delivery lifecycle.

Key Responsibilities

• 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) testing is 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 before the start of UAT/Unified Testing — setting the team up for a clean, confident testing entry.
• Strategically coordinateTestbed (TBED) criteria pull readiness 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 email duringUnified 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.
• Champion testing readiness by sending timelyreminders to testers prior to the release start, ensuring user stories and test scripts are uploaded to the correctZephyr Release Fix Version — aligned to the matching Fix Version in JIRA.
• Fornon-Zephyr teams, provide clear direction by notifying testers to build their test scripts in Excel format and equipping them with theRequired Testing and Test Exit Report Input document — ensuring no team is left without a clear path forward.
• Maintain a sharp eye ontesting team progress, actively monitoring for any signs of slippage that could jeopardize completion timelines. Intervene early and decisively to ensure testers have the time and support needed to meet release milestones.
• Overseedefect health in JIRA — tracking aging defects, driving timely updates, and facilitating resolution with a sense of urgency. For defects tied to aVendor or Partner fix, ensure accountability is correctly placed with the applicableCiti Developer serving as the primary point of contact.
• Establish a strong quality foundation by initiating theTest Plan Input at thefirst impacted Sprint — setting the tone for structured, disciplined testing from the outset.
• ForZephyr-executing teams, validate that:
• The Zephyr Release aligns with theUser Stories Fix Version.
• All user stories and test scripts are successfullyloaded into Zephyr and ready for execution.
• Lead the closure phase with rigor — generate theTER Readiness Checklist and take full ownership of creating theTest Exit Report (TER), a Release-level document that tells the complete story of testing performed for the project's production release.
• Leverage theJIRA 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 that no testing effort goes undocumented or unvalidated.

Mandatory Skills: Quality Management.Experience: 8-10 Years.The expected compensation for this role ranges from $80,000 to $158,000 .Final compensation will depend on various factors, including your geographical location, minimum wage obligations, skills, and relevant experience. Based on the position, the role is also eligible for Wipro's standard benefits including a full range of medical and dental benefits options, disability insurance, paid time off (inclusive of sick leave), other paid and unpaid leave options.Applicants are advised that employment in some roles may be conditioned on successful completion of a post-offer drug screening, subject to applicable state law.Wipro provides equal employment opportunities to all employees and applicants for employment and prohibits discrimination and harassment of any type without regard to race, color, religion, age, sex, national origin, disability status, genetics, protected veteran status, sexual orientation, gender identity or expression, or any other characteristic protected by federal, state, or local laws. Applications from veterans and people with disabilities are explicitly welcome.Reinvent your world. We are building a modern Wipro. We are an end-to-end digital transformation partner with the boldest ambitions. To realize them, we need people inspired by reinvention. Of yourself, your career, and your skills. We want to see the constant evolution of our business and our industry. It has always been in our DNA - as the world around us changes, so do we. Join a business powered by purpose and a place that empowers you to design your own reinvention.

We are an Equal Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race, color, caste, creed, religion, gender, marital status, age, ethnic and national origin, gender identity, gender expression, sexual orientation, political orientation, disability status, protected veteran status, or any other characteristic protected by law.

Wipro is committed to creating an accessible, supportive, and inclusive workplace. Reasonable accommodation will be provided to all applicants including persons with disabilities, throughout the recruitment and selection process. Accommodations must be communicated in advance of the application, where possible, and will be reviewed on an individual basis. Wipro provides equal opportunities to all and values diversity.