Test Engineer (44156)

For a migration project in a telecommunications environment, where B2B wholesale APIs are moving from MuleSoft to the Quickwork platform, we are looking for a Test Engineer. You will act as the independent quality gate of the migration – proving functional parity of the new solutions with the original APIs, validating performance under production load and owning the UAT sign-off before every production cutover. Experience with API testing(Postman/Newman, RestAssured or pytest), performance testing (JMeter, k6 or Gatling) and test integration into GitLab CI/CD is required.

🚀 Project
- migration of B2B wholesale APIs from MuleSoft to the Quickwork integration platform in a telecommunications environment
- independent QA control – functional parity, performance and no impact on non-migrated APIs
- design and execution of parity tests – field-by-field comparison of MuleSoft and Quickwork responses in UAT
- end-to-end testing of multi-step business flows (Feasibility → POQ → Order) with stateful scenarios
- performance tests validating a hard 60-second timeout under production load
- regression testing, synthetic test data and test automation in GitLab CI/CD
- UAT ownership – structured results report and the “UAT passed / failed” decision before every cutover

🎯 Skills
- 5+ years in API integration testing, including at least one project focused on proving parity between two implementations of the same API (migration, re-platforming, parallel deployment)
- Postman / Newman – collections, Dev/UAT/Prod environments, variables for token management, HTML reports
- programmatic API tests in RestAssured, pytest-requests or equivalent (e.g. correlation-ID threading across multiple calls)
- performance testing in JMeter, k6 or Gatling – baseline, load ramp, sustained load and result analysis (p95/p99)
- test design – equivalence partitioning and boundary testing from OpenAPI 3.0 specs, regression suites
- test data management – synthetic data based on TMF/MEF schemas
- integration of tests into GitLab CI/CD, including blocking the pipeline on test failure
- awareness of contract testing (Pact or equivalent)
- Playwright
- English B2

💡 Nice to have
- testing TMF Open API implementations (TMF622, TMF645, TMF673)
- MEF Sonata (MEF87 POQ, MEF121 Address Validation)
- Quickwork journey testing via the Quickwork API and analysis of execution traces in logs
- hands-on contract testing experience (Pact)
- German

#LI-KP1