Manual QA Engineer – Position No. 1730

The Role

We're looking for a hands-on QA Engineer to join our development teams and take ownership of quality across our web-based applications. This is a practical, collaborative role combining manual testing, API testing, database validation, and test automation.

You'll work closely with developers, product managers, and other QA engineers in Scrum teams, participating throughout the development lifecycle — from understanding requirements and identifying risks to designing test cases, executing tests, reporting defects, and supporting releases.

We're looking for someone who can work effectively as part of a team but is equally comfortable taking ownership of tasks independently. You should be curious, self-driven, and able to deal with challenging or ambiguous requirements by asking the right questions, identifying gaps, and thinking beyond the obvious test scenarios.

What You'll Do

• Manual Web Testing: Plan and execute functional, regression, integration, and exploratory testing of web applications. Identify edge cases and potential risks beyond the documented requirements.
• Test Planning & Documentation: Write and maintain detailed Test Cases, STPs, and other QA documentation using test management tools.
• API Testing: Test REST APIs using Postman, validate requests and responses, verify business logic, and identify integration issues between systems.
• Database & Data Validation: Use SQL to validate data, investigate issues and verify data flows between application layers.
• Test Automation: Develop and maintain automated tests where appropriate. Contribute to the automation strategy and continuously expand automated coverage. Strong knowledge of automation is required; hands-on automation experience is a significant advantage.
• Agile / Scrum: Work as an active member of Scrum teams, participating in sprint planning, refinement, daily meetings, reviews, and retrospectives. Collaborate closely with developers and product teams throughout each sprint.
• Defect Management: Identify, investigate, document, and track defects using Jira. Provide clear reproduction steps, relevant evidence, and technical information to help development teams resolve issues efficiently.

What We're Looking For

• 2-4 years of hands-on QA/testing experience in web-based applications.
• Strong understanding of software testing methodologies, including functional, regression, integration, exploratory, and end-to-end testing
• Hands-on experience with Jira and working within Agile/Scrum development teams and sprint-based environments.
• Experience writing Test Cases (TCs), Software Test Plans (STPs), test scenarios, and test documentation, as well as working with test management platforms (like TestRail, X-ray..)
• Strong hands-on experience with Postman and API testing, including validating REST APIs, requests/responses, status codes, and business logic.
• Knowledge of SQL and relational databases, with the ability to query data, validate results, investigate issues, and verify data integrity.
• Strong understanding of test automation concepts and frameworks. Automation knowledge is a must; hands-on experience writing and maintaining automated tests is a significant advantage.

Personal skills required:

• Strong analytical and problem-solving skills - with the ability to investigate issues and identify root causes rather than simply report symptoms.
• A team player who can collaborate effectively - with developers, product managers, and other QA engineers, while also being comfortable working independently and owning tasks end-to-end.
• Ability to self-learn new technologies and systems - quickly understand unfamiliar functionality, and become productive.
• Ability to work effectively with challenging or incomplete requirements - You should be comfortable asking the right questions, identifying missing information, challenging assumptions, and thinking outside the box to determine what needs to be tested.
• Independent Problem Solving - Take ownership of testing challenges, investigate issues independently, and find solutions with limited documentation\info. Know when and what to ask when requirements or information are incomplete.
• Quality Ownership - Think beyond the written requirements and proactively identify missing scenarios, edge cases, risks, and potential production issues. Help improve QA processes, test coverage, and overall product quality.