Quality Assurance Engineer

Autopay Global is the newest member of the Autopay family, aiming to expand the reach of the group’s state-of-the-art payment integration and payment data technologies to the international market, providing seamless integration with local PSPs, support for multiple currencies and compliance with local frameworks.

• Minimum 5 years of experience in testing and test automation
• Excellent knowledge of testing methods and techniques: TDD, BDD, functional and non-functional testing
• Proven track record of integrating tests with CI/CD pipelines like Github Actions, Gitlab CI/CD, Teamcity
• Comfortable knowledge of Java programming language and using respective testing facilities (JUnit and/or TestNG, RestAssured, Cucumber, Quarkus continuous testing)
• Fluency in using end-to-end testing tools (Playwright, Cypress)
• Good understanding of OpenAPI Specification and/or RAML
• Proven track record of participation in Scrum projects and ability to work in sprints
• Growth mindset and ability to apply new technologies, patterns or solutions to the current workstream (i.e. GenAI-assisted coding)
• Strong communication and interpersonal skills
• Knowledge of English on the B1 level in speech and writing

Nice to have:

• Familiarity with contract testing (Pact, Microcks) and Arquillian
• ISTQB Foundation certification

• Develop an API-focused testing strategy: deriving tests from API specifications (OAS/RAML), API versioning, optionally – contract testing
• Get involved in creating and maintaining test code – either as separate modules or – where applicable – as part of a particular service
• Explore, adapt and deploy methodologies and tooling that maximizes the confidence of delivering code compliant with specifications and regulations
• Automate backend tests as part of their CI/CD pipeline
• Consider the impact of the cloud environment on test performance
• Consider the asynchronous nature of some data exchange
• Develop end-user tests for customer-facing portions of the system
• Develop scenarios driven by user interaction that validate the outcome on the backend side
• For end-user tests, consider the variety of user devices and browsers
• Develop a framework for documenting problems, reproduction and remediation steps