Job Description

Position: API Migration Test Lead

Company: Global Professional Services Organization

Client Industry: Transportation

Location: Dallas, TX or San Antonio, TX

Work Arrangement: Hybrid – Onsite at Client HQ 2 Days per Week

Employment Type: W2 Contract-to-Hire

Engagement Requirement: W2 candidates only; C2C is not permitted

Overview

The API Migration Test Lead will lead the testing strategy and execution required to validate APIs as they move through a complex technology migration for a major Transportation client. The individual will be responsible for ensuring migrated APIs continue to provide the expected functionality, integrations, data behavior, reliability, and performance before they are approved for production use.

This is a hands-on testing leadership role rather than a test-coordination-only position. The successful candidate must be technically capable of working directly with REST and SOAP APIs, using Postman and appropriate automation technologies to design, execute, troubleshoot, and improve API testing. The Test Lead must understand enough about API behavior and migration dependencies to determine why a test failed rather than simply reporting that it failed.

The individual will establish the migration test strategy, identify coverage requirements, coordinate testing across dependent teams and environments, manage defects through resolution and retesting, expand automation where appropriate, conduct or coordinate performance testing, and provide stakeholders with objective evidence of production readiness.

Because this position operates within a Global Professional Services environment, the Test Lead must combine strong technical testing capability with client-facing communication, delivery accountability, and the ability to coordinate engineering, development, infrastructure, integration, and business stakeholders.

Purpose:

Protect a critical technology migration by ensuring APIs continue to work as expected as they transition into the target environment. Your testing leadership will provide the evidence technical and business stakeholders need to determine whether migrated services are genuinely ready for production.

Expand beyond traditional functional QA by working across API migration, REST/SOAP services, test automation, performance testing, integration dependencies, defect management, and production-readiness validation. The role provides significant exposure to complex enterprise migration challenges within a Global Professional Services environment supporting the Transportation industry.

Objectives

1. Establish and Execute the API Migration Test Strategy. Within the first 30–60 days, assess the API migration scope and develop a practical test strategy covering applicable REST and SOAP APIs, functional behavior, integrations, data validation, regression requirements, negative scenarios, automation, performance, dependencies, and migration readiness. Establish traceability between migration requirements, critical API behaviors, test coverage, defects, and readiness decisions so stakeholders have objective visibility into testing progress. Prioritize testing according to business and technical risk rather than treating every API or test case as equally critical. Success will be measured by stakeholder acceptance of the strategy, appropriate coverage of critical migration scenarios, visibility into testing progress, and early identification of significant migration risks. AI-assisted test generation may be used where permitted, with all generated tests independently reviewed for technical relevance and coverage.
2. Validate REST and SOAP APIs Throughout the Migration. Throughout the migration, lead and personally contribute to hands-on API testing using Postman and other approved testing capabilities to verify that migrated REST and SOAP services operate as expected. Validate requests, responses, status behavior, data, error handling, integrations, and other relevant API functionality and investigate differences between source and target environments. Work with engineering teams to determine whether failures originate from the API, migration configuration, environment, data, integration dependencies, or the test itself. Success will be measured by test coverage, defect detection, successful resolution and retesting, and objective evidence that priority migrated APIs satisfy agreed functional expectations.
3. Build Automation and Performance Testing into Migration Validation. During the first 90–180 days, identify repetitive and business-critical API tests that should be automated and establish or improve reusable regression capabilities supporting the migration. Incorporate performance testing for appropriate APIs to identify response-time, throughput, stability, or scalability problems that may not appear during functional testing. Integrate automated testing into the broader delivery process where practical.