Test Automation Engineer

• Create a test plan and define acceptance criteria with the business and development team for each increment, and optimize existing test plans.
• Create, document, and execute integration and end-to-end (E2E) tests.
• Ensure the automation of the execution of created tests, both independently and by supervising their implementation.
• Monitor and maintain existing integration and end-to-end test cases.
• Evaluate and improve test coverage in a reasoned manner.
• Evaluate the priority and criticality of detected bugs and take appropriate measures.
• Support the analysis and development process by providing a critical perspective.
• Participate in the organization of user acceptance tests.
• Scrum master for the team: you ensure the organization and follow-up of agile rituals, in a true "inspect and adapt" spirit.
• Domain Quality steward: you ensure compliance with testing best practices within the 4 teams of the domain.

What they ask

Technical skills.

• Advanced proficiency in test definition (acceptance criteria, test plan creation and execution).
• Test automation techniques (methodology, best practices).
• Advanced proficiency in SQL (medium complexity queries: joins, deltas...).
• Knowledge of test frameworks (test levels, test responsibilities..).
• Active knowledge of an object-oriented language, writing Java code is essential.
• Comfortable with a versioning system such as GIT.
• Active and recent experience in an agile environment.
• Knowledge of the XML language.
• Capable of managing E2E testing of a functionality autonomously and independently.
• Knowledge of several testing tools such as Xray, Postman, Cucumber, Playwright, etc.
• Recent experience in the implementation of complex payment/accounting systems.

Are a plus.

• An ISTQB, TMAP, or equivalent certification.
• A Scrum Master certification.
• Recent experience in the public sector or social security systems.
• Active knowledge of REST and SOAP exchanges.

Behavioral skills.

• Proactive and persistent.
• Assertive.
• Team player.
• Curious.
• Motivated to bring real added value to the organization.
• Professional: you can accept community choices even when they differ from your preferences.
• Open to feedback.
• Able to work completely autonomously.
• Ready to take initiatives.
• Able to define your priorities.
• Communicates clearly with stakeholders (e.g., user counterparts, other development teams).