Riskonnect
QA Engineer
QA Engineer at Riskonnect splitting time (~60/40) between writing Playwright test automation and manual testing of the Business Continuity & Resilience SaaS product, working within an Agile sprint team in the Bengaluru office.
- Compensation
- Not disclosed
- Location
- Bangalore Office, Bengaluru, Karnataka, IN
- Work setup
- Not specified
- Seniority
- Not specified
- Employment
- Not specified
- Experience
- Not specified
- Category
- Qa
- Posted
Skills
Must have
- Test automation using Playwright, leveraging existing test framework methods
- Manual testing experience with a testing mindset; identify test cases/scenarios and decide manual vs automated
- Work on a Sprint team, testing functionality manually within a sprint and automating it
- Experience with SaaS web applications
- Experience using AI to expedite test development
- Familiar with CI/CD pipelines and troubleshooting test failures outside development environment
- Familiar with different levels of testing (API, Unit, Integration, GUI) and choosing appropriate automation approach
- Familiar with software development using an Agile process (Scrum, Kanban)
- Effectively communicate with dev team during agile ceremonies (standup, refinement, sprint planning, retrospectives)
- Actively participate in agile story refinement/grooming and identify initial manual test cases
- Familiarity with Azure DevOps, JIRA, etc
Nice to have
- Knowledge of Playwright MCP
- Experience with mobile app testing (Android & iOS), mobile automation frameworks, JS testing frameworks
Full description
- Riskonnect is looking to hire QA resource that will focus on Test Automation using Playwright and manual testing of Riskonnect’s Business Continuity & Resilience product (Resilience).
- These resources will spend most of their time writing test automation, and the remainder doing manual testing (roughly a 60%/40% split). This percentage is subject to change based on the product area, functionality, and delivery timeline of the feature they are working on.
- Resources will need to work on a Sprint team and test functionality manually within a sprint and automate it.
- These resources should have a “testing mindset” and be able to identify test cases/scenarios and decide what should be tested manually vs tested via test automation. They will be responsible for quality of the product area they are testing and will be writing the test automation as well.
- These resources will use Playwright and leverage existing test framework methods.
- Experience with SAAS web applications.
- Experience using AI to expedite test development.
- Knowledge of Playwright MCP is a plus.
- Any experience with mobile app testing (Android & iOS), mobile automation frameworks, JS testing frameworks is a plus.
- Must be familiar with CI/CD pipelines and troubleshooting the test failures outside of development environment.
- Must be familiar with different levels of testing such as API, Unit, Integration, and GUI testing, and choose the appropriate approach for automation. They are not expected to contribute to API/Unit/Integration testing automation but should be able to categorize the testing use cases into the right layer of automation.
- Must be familiar with software development using an Agile process (Scrum, KanBan)
- Must be able to effectively communicate with the dev team during various agile process ceremonies (daily standup, story refinement/backlog grooming, sprint planning and sprint retrospectives, etc)
- These resources are expected to be an active participate in agile story refinement/grooming meetings, and able to identify initial manual test cases based on story refinement.
- Familiarity with Azure DevOps, JIRA, etc