Senior QA Engineer | Madrid, ES

Senior QA Engineer

As a Senior QA Engineer, you get a chance to take a lead in development of our digital banking platform with focus on a quality deliverable. You astonish your team and key stakeholders with your drive for product quality. As a quality ambassador, you promote quality within the team in alignment with the QA Guild and ensure quality solutions are being delivered during the whole product, subsystem or project development cycle.

Meet the job

You create the initial test strategy for the product, subsystem or project you are working with based on the overall Test Strategy from QA Guild. You present and justify the test strategy and decision to clients and stakeholders. You conduct test plans and define test designs for difficult or advanced technological concepts. You are responsible for developing and executing manual and automated tests that cover functional and non-functional requirements (e.g. performance, security). You test functionality and systems by applying different testing methodologies and different test levels. You ensure that automation testing for the components of our web and mobile solutions are in line with the standardized tools and languages introduced by the QA Guild. You act as a part of the agile team, take part and contribute to Agile ceremonies and work closely with the product owner and various team members. You drive the discussion with clients and stakeholders and the team by leveraging test evidence, defect metrics and reporting on the complete QA process and communicating on potential risks based on previous experience. You hold a strong testing and DevOps mindset to be able to understand and work with our tooling in environments and CI/CD. You are keen to explore different testing types and methodologies.

You contribute to the Chapter and Guild, if possible, by taking part in defining internal QA goals (e.g. evaluation of new tools, setting up new processes and training of new hires). You are a point of contact for all QA activities in your area of responsibility. You also play a key role in selecting candidates for QA roles as well as onboarding and mentoring new hires.

How about you

1. 4-7 years of experience in a QA role;
2. Bachelor in Information Technology, Computer Sciences or similar/related technical field, or equivalent practical experience;
3. English language, written and spoken.

1. Performs at the highest level in their team, sharing their knowledge with other QA Engineers, the team, VS and support channels;
2. Knows more than one programming language, the ones used internally, in a sufficient level to create automated test cases in the tools used by the organization;
3. Advanced knowledge of the main testing frameworks and basic understanding of other related or similar frameworks;
4. Suggests, plans and performs technical improvements related to the discipline of QA;
5. Understands the different testing levels and testing types (functionals and non-functionals) and contributes to the Test Strategy of the organization by suggesting/contributing to/in the QA community;
6. Designs tests with the usage of test methodologies by applying different testing types (functional, non-functional) in alignment with the acceptance criteria;
7. The designed test cases for functionality cover positive and negative scenarios as well as edge cases and errors;
8. Can write automated test cases in different testing levels not only for a single functionality but also for the whole system under test;
9. Contributes to the testing framework, common libraries or other tooling of the QA Guild;
10. Is the go-to person for technical questions and issues;
11. Stays up to date with changes in their discipline and their industry;
12. Has the ability to write all kinds of tests, uses all kinds of tools, provided internally, that improve the overall quality of the code and the software;
13. Understands the CI/CD phases and does major contributions for the workflows/pipelines;
14. Acts as an advocate for all the NFRs important for product readiness;
15. Advocates finding security vulnerabilities by executing simple security tests as instructed by the security team;
16. Uses the accessibility knowledge and the available tools to test the product for accessibility;
17. Contributes to the product's performance by either creating performance tests or analysing performance results with the selected performance tools (e.g. k6.io);
18. Is able to provide workarounds and give clear feedback to the team on how the product should be improved;
19. Exposed to all capabilities of the Backbase Platform;
20. Understands all aspects of how the software is built, assembled, tested and run in production;
21. Is capable of implementing and proposing improvements to the existing tooling and processes for automated testing phases;
22. Is involved in product support and CS/RnD collaboration;
23. Is well known in their chapter and becomes known in the guild, by supporting guild initiatives whenever possible;
24. Supporting other less senior QAs and passing knowledge;
25. Is able to interact with the stakeholders and support them with the issues they have on the capabilities the team owns;
26. Anticipates and communicates potential implementation issues in refinement sessions, aiding preemptive problem-solving;
27. The results of testing are reported in a language that is understandable by technical and non-technical stakeholders;
28. Prioritizes the test scenarios execution based on risk, time and expectations;
29. Reviews tasks critically and ensures they're appropriately sized also for the necessary testing activities;
30. Ensures tasks are prioritized correctly, and that dependencies are noted;
31. Can identify when a ticket is not ready and challenges their PO/BA before planning its work;
32. Helps BAs and POs write clear tickets based on the acceptance criteria;
33. Reviews the automation code and provides comments to assist in improvements;
34. Has regular working sessions with engineers from other teams, throughout the SDLC e.g. technical test design sessions, PoCs, etc.

1. Is able to provide workarounds and give clear feedback to the team on how the product should be improved;
2. Exposed to all capabilities of the Backbase Platform;
3. Understands all aspects of how the software is built, assembled, tested and run in production;
4. Is capable of implementing and proposing improvements to the existing tooling and processes for automated testing phases.

1. Is involved in product support and CS/RnD collaboration;
2. Is well known in their chapter and becomes known in the guild, by supporting guild initiatives whenever possible;
3. Supporting other less senior QAs and passing knowledge;
4. Is able to interact with the stakeholders and support them with the issues they have on the capabilities the team owns;
5. Anticipates and communicates potential implementation issues in refinement sessions, aiding preemptive problem-solving;
6. The results of testing are reported in a language that is understandable by technical and non-technical stakeholders;
7. Prioritizes the test scenarios execution based on risk, time and expectations;
8. Reviews tasks critically and ensures they're appropriately sized also for the necessary testing activities;
9. Ensures tasks are prioritized correctly, and that dependencies are noted;
10. Can identify when a ticket is not ready and challenges their PO/BA before planning its work;
11. Helps BAs and POs write clear tickets based on the acceptance criteria;
12. Reviews the automation code and provides comments to assist in improvements;
13. Has regular working sessions with engineers from other teams, throughout the SDLC e.g. technical test design sessions, PoCs, etc.