Test Architect L1

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

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.

• 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 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…