The mission:
The project is structured in 4 applications, aggregated into a powerful BPM System, where all the processes are modelled and configured:
• Front End System (web application used by offices and branches to sell products and services);
• Back Office System (web application used by all users from head office operational departments);
• Call Centre System (web application used by users from the call center department);
• NARC (new developed front-end system were we are migrating the functionalities from the other 3 legacy front-end applications).

Area & application type:

We are talking about a suite of internal applications, developed in C #, respectively the applications used in Front Office, Back Office and Call center – all for the corporate clients segment.

Team & Way of working: There is a separate development chapter, coordinated by Alex, but people work co-located with different teams (squads).The chapter is made up of specialists from the same profession, reports to a Chapter Lead who is also part of a squad and works on delivery.
This squad includes ~ 2-3 backend developers, ~ 1-2 QAs, 1 colleague 2nd line support, ~ 1 feature engineer (or BA), a Product Owner and a Product Manager

Tehnologies & ideal candidate:
For the first part the role will be one of manual testing and automatic testing using
SpecFlow and Gherkin, later, having the opportunity to implement new methods in the testing framework that is written
in C #.

Other details and soft skills description:

This role will participate in discussions with the business, as a result it is important to see people who can do this easily. Experience in automated testing is not mandatory, but we would like to see technical people who understand certain concepts about operators, APIs, SQL, testing notions. Also, we wantsomeone intereste to transition towards automatic testing (implementation of methods, integrations with APIs) and tonot have a specific preferred language (for example, someone who wants to do strictly in Java, will not be happy with an internal toolwritten in C#. At the same time, if the person did not used SpecFlow before, it is quite easy to learn – the language is very close to human language – the tests created can be understood by business people. Experience in manual testing should be at least 2-3 years. Also, an interesting profile could be a person who has done scripting / programming (at least one year) in some proprietary tool and wants to move to the automatic testing area.