Overview
Senior QA Test Engineer
Responsibilities
* Test Strategy & Planning: Define and implement a comprehensive testing strategy for microservices or APIs.
* Automation: Develop and maintain automated test scripts using Cucumber for integration with continuous integration/continuous deployment (CI/CD) pipelines.
* Collaboration: Work closely with developers, QA engineers, and product managers in an Agile environment to identify issues.
* Analysis & Reporting: Analyze test results, identify functional and nonfunctional issues, and provide recommendations.
* Tooling & Frameworks: Evaluate and recommend new tools, frameworks, and methodologies to enhance testing efficiency and effectiveness.
* Mentorship: Provide guidance and mentorship to junior test engineers, fostering a culture of continuous improvement and knowledge sharing.
Qualifications
* Experience: couple of years of experience in software testing, with a focus on manual testing and test automation.
* Typescript/Java: Proficient in TypeScript/Java, with the ability to write and maintain test automation scripts.
* Experience in Node.js frameworks such as Playwright or Cypress or other Node.js automation frameworks in JavaScript.
* Cucumber: Solid experience with Cucumber and BDD (Behaviour-Driven Development) practices.
* Agile Methodologies: Proven experience working in Agile/Scrum environments, collaborating effectively with cross-functional teams.
* CI/CD: Experience integrating performance tests into CI/CD pipelines, using tools like Jenkins, GitLab, or similar.
* Non-functional skills: A good working knowledge of non-functional areas such as performance, accessibility & security.
* Cloud skills & other tools: AWS, Grafana, Splunk.
* Experience with MongoDB would be good but not essential.
* Problem-Solving: Strong analytical and problem-solving skills, with the ability to diagnose and resolve complex testing/automation issues.
* Communication: Excellent verbal and written communication skills, with the ability to articulate complex technical issues to both technical and non-technical stakeholders.
#J-18808-Ljbffr