QA / Test Engineer

Project overview

API Integration, Parity & Performance Testing

The QA/Test Engineer owns the test suite and produces the UAT sign-off that serves as the cutover gate condition. The role works closely with the Integration Developers, the Technical Lead, and the MuleSoft SME.

Responsibilities

Parity & End-to-End Testing

Test Design, Performance & CI/CD

UAT Ownership & Reporting

Requirements / Skills

API Testing (core – deep expertise required)

Performance Testing (required)

Test Design & CI/CD

• Define "parity" per API (same HTTP response code, same schema, semantically equivalent response body)
• Run response comparison tests between MuleSoft (UAT) and Quickwork (UAT), field by field, and document differences with a disposition (expected difference vs. defect)
• Design edge-case test inputs together with the MuleSoft SME (T-Systems)
• Design and implement a stateful end-to-end test for the FPWP business flow (Feasibility ? POQ ? Order)
• Determine which scenarios require mocked backends and which require live backends in UAT
• Derive test cases from OpenAPI 3.0 specs, including boundary conditions, optional-vs-required field combinations, and error cases
• Design a regression suite confirming that non-migrated APIs are not affected by a cutover
• Design or obtain synthetic test data for B2B wholesale APIs conforming to TMF/MEF schema structures
• Run load tests simulating production peak traffic and validate the TARDIS 60-second timeout constraint (p99 ? 55 seconds)
• Integrate Postman/Newman collections into the GitLab CI/CD pipeline so that failed tests block a pipeline stage
• Own UAT test execution and declare "UAT passed" or "UAT failed" with evidence
• Document UAT results in a structured report (test case, input, expected output, actual output, pass/fail) for review by the Technical Lead
• 5+ years in API integration testing, including at least one project proving parity between two implementations of the same API (migration, re-platform, or parallel deployment)
• Postman / Newman: collections, environments for Dev/UAT/Prod, collection variables for token management, Newman HTML reports
• RestAssured, pytest-requests, or equivalent for programmatic API tests
• Contract testing awareness (Pact or equivalent); implementation experience is a strong plus
• JMeter, k6, or Gatling: at least one delivered project with baseline measurement, load ramp, sustained load, and result analysis
• Ability to distinguish application latency, network latency, and test harness overhead
• Equivalence partitioning, boundary testing, and regression test design
• Test data management
• GitLab CI/CD integration with test results as a pipeline gate

Project details

• Start: ab sofort
• Remote: remote
• Location: Hamburg, Deutschland, DE