Qa Engineer

Role & responsibilities

The engineer owns test planning and execution for releases across all three platforms:

Review product requirements, user stories and designs; raise gaps and ambiguities early.

Write and maintain test scenarios, test cases and checklists in a test management tool.

Run functional, regression, smoke, sanity, integration and exploratory testing each sprint.

Mobile: Test Android and iOS apps on real devices and emulators/simulators, covering OS versions, screen sizes, permissions, push notifications, offline mode, interruptions and app upgrades.

API: Validate REST endpoints with Postman or similar status codes, payloads, schema, auth tokens, error handling and negative cases.

Web: Cross-browser and responsive testing on Chrome, Safari, Firefox and Edge; basic UI, usability and accessibility checks.

Log clear, reproducible defects with steps, logs and screenshots; track them to closure and verify fixes.

Do basic backend data checks using SQL queries.

Take part in sprint ceremonies and give go/no-go input on releases.

Contribute to building and maintaining automated regression suites over time.

Share test reports and quality metrics (pass rate, open defects by severity) with the team.

Must-Have Skills

Candidates must show strong manual testing across mobile, API and web, backed by real project examples.

Manual Testing Fundamentals: SDLC/STLC, test case design (boundary values, equivalence partitioning, decision tables), regression and exploratory testing.

Mobile App Testing: Android and iOS functional testing, device/OS coverage, install/upgrade, network and interruption scenarios, reading device logs.

Tools: Real devices, Android Studio emulator, Xcode simulator, BrowserStack / LambdaTest

API Testing: REST concepts, HTTP methods and status codes, JSON, auth (tokens, OAuth), collections and environment variables.

Tools: Postman, Swagger / OpenAPI

Web Testing: Cross-browser and responsive testing, browser DevTools (console, network tab).

Tools: Chrome DevTools

Defect and Test Management: Clear bug reports, severity vs priority, defect lifecycle.

Tools: Jira, TestRail / Zephyr or similar

Database Basics: Simple SELECT queries, joins and filters to verify data.

Tools: MySQL / PostgreSQL

Agile Ways of Working: Sprint-based delivery, working closely with developers and product.

Tools: Scrum / Kanban

Preferred candidate profile

Automation experience is a differentiator, not a requirement; a candidate who has written and run real scripts ranks above one who has only read about them.

Web Automation: Selenium WebDriver or Playwright, with Java, Python, JavaScript or TypeScript.

Test Frameworks: TestNG / JUnit, PyTest, or Playwright Test; Page Object Model.

API Automation: Postman/Newman, REST Assured or Playwright API testing.

Mobile Automation: Basic exposure to Appium.

CI/CD: Running test suites in Jenkins, GitHub Actions or GitLab CI.

Version Control: Git basics (clone, branch, commit, pull request).

Performance: Basic load testing with JMeter or k6.

Certification: ISTQB Foundation Level.

Qualifications

Bachelors degree in Computer Science, IT or a related field, or equivalent practical experience.

2–3 years as a QA / test engineer, with at least one shipped mobile app and one web product.

Soft Skills

Strong attention to detail and a habit of thinking through edge cases.

Clear written and verbal communication, especially in bug reports and test summaries.

Ownership of quality: follows defects through to closure without being chased.

Works well with developers, product managers and designers; comfortable pushing back with evidence.

Eager to learn and grow into automation.