Functional QA - UVT
emagine
This is a QA Engineer role focused on functional testing of identity, authentication, and registration services across 70+ markets. You will translate business requirements into test scenarios, manage market-specific configurations in DynamoDB, and write BDD integration tests using Cucumber and Pactum. The role acts as a bridge between product and engineering, ensuring quality across multiple brands, channels, and regions. It requires a strong business-functional mindset and hands-on automation.
Brak jawnych widełek — wynagrodzenie do ustalenia podczas rekrutacji.
Brakuje: team size and composition, project duration and timeline.
This is a QA Engineer role focused on functional testing of identity, authentication, and registration services across 70+ markets. You will translate business requirements into test scenarios, manage market-specific configurations in DynamoDB, and write BDD integration tests using Cucumber and Pactum. The role acts as a bridge between product and engineering, ensuring quality across multiple brands, channels, and regions. It requires a strong business-functional mindset and hands-on automation.
- ✓Fully remote work
- ✓Work with modern tools (Cucumber, Pactum, DynamoDB, Xray)
- ✓Opportunity to work on a large-scale system spanning 70+ markets
- ✓Inclusion in a QA Community of Practice for knowledge sharing
- ✓Hands-on involvement in both test design and automation
- !Contract type is 'other' — may indicate B2B or freelance, terms unclear
- !Location is Lisbon but role is remote — timezone expectations or travel may be required, not specified
- !Project name 'UVT' is unexplained — potential short-term or project-based engagement
- ?Brak jawnych widełek — wynagrodzenie do ustalenia podczas rekrutacji
- •Translate business requirements and user stories into comprehensive test scenarios covering real consumer journeys (registration, login, OTP, profile management)
- •Set up and manage per-market, per-channel, per-brand configuration entries in DynamoDB to control feature behavior
- •Write and maintain integration tests using Cucumber (Gherkin) and Pactum for end-to-end API behavior
- •Work closely with Product Owners to clarify requirements, identify edge cases, and ensure testable acceptance criteria
- •Validate multi-market, multi-channel behavior (locales, channels, brands)
- •Manage test data and environments (set up test consumers, configure market settings, prepare ephemeral environments)
- •Track quality and traceability using Xray and Jira (link test cases, manage execution cycles, report coverage and defects)
- •Support release readiness by verifying configuration deployments, running regression suites, and confirming onboarding of new markets or channels
Oferta dla doświadczonych specjalistów (Senior).
A QA engineer with at least 3 years of experience in functional testing, proficient in Cucumber and API testing, and able to independently translate business requirements into test scenarios. They should have basic JSON skills and be comfortable with Jira and Git.
This role is not suitable for junior QA engineers with less than 3 years of experience, nor for those seeking purely manual testing without automation. It also may not appeal to engineers who prefer working in a single product without configuration complexity or who dislike close collaboration with product teams.
- ?How many QA engineers are on the team, and how are responsibilities shared?
- ?Is this a new project or an ongoing one? What is the expected duration?
- ?What does the CI/CD pipeline look like, and how are tests integrated?
- ?What is the balance between manual exploratory testing and automated regression?
- ?Are there on-call or production support duties?
- ?What is the onboarding process for new markets—is there documentation or a standard procedure?
- ?What specific identity/authentication services are involved (e.g., custom built or third-party)?
- −Team size and composition
- −Project duration and timeline
- −Exact contract type (B2B, freelance, etc.)
- −On-call or support requirements
- −Specifics about the product and end client (if any)
Collaborative environment with close interaction between QA, Product Owners, and engineering. Emphasis on shared quality practices through a QA Community of Practice.