QA Test Engineer (Manual Testing)

PVKL Tech Services Pvt Ltd; Pune District; On-site; INR 600,000 - 900,000; Full time

Job summary

PVKL Tech Services Pvt Ltd in Pune is seeking a manual QA tester to design and execute test plans, report defects with precision, and own the quality gate for releases.

You will work with developers, product managers, and the implementation team to understand expected behavior and break the product from a user perspective.

This role emphasizes thoughtful testing, regression cycles, API checks with Postman, and cross-browser validation to ensure robust software delivery.

Qualifications

• Design test cases from requirements and user stories.
• Execute functional and regression tests across platforms.
• Document defects with steps, expected vs actual, and environment details.
• Coordinate with developers and PMs for timely releases.
• Support UAT activities and release sign-off.
• Identify data/test environments and maintain test data.

Responsibilities

• Design comprehensive test cases and scenarios including edge cases.
• Execute tests on web app and APIs; report defects precisely.
• Perform cross-browser and cross-device testing.
• Verify fixes and perform targeted regression.
• Coordinate with teams for go/no-go release.
• Improve testing processes and checklists.

Skills

Test planning

Test case design

Regression testing

Bug reporting

Cross-browser testing

API testing

UAT support

Tools

Postman

Jira

Job description

Role summary

This is a manual testing role. You'll design test cases, execute them methodically, report bugs with precision, verify fixes, and own the quality gate for releases. You'll work closely with developers, product managers, and the implementation team to understand what's being built, how it should behave, and what could go wrong. You'll need to think like a user who's trying to break the product, not like someone who's trying to confirm it works.

What you'll do

Test planning & case design

• Analyse product requirements, user stories, and design documents to understand what's being built and define what needs to be tested
• Design comprehensive test cases and test scenarios: positive paths, negative paths, edge cases, and boundary conditions - a feature isn't tested until the unlikely paths are tested too
• Maintain and organise the test case repository - keep it current, structured, and reusable so regression testing doesn't start from scratch every cycle
• Identify test data requirements and set up test environments for each testing cycle

Test execution & bug reporting

• Execute functional test cases manually across the platform - web application, APIs, and workflows - for every new feature, enhancement, and bug fix before it goes live
• Run regression testing before every release to ensure existing functionality hasn't been broken by new changes
• Perform cross-browser and cross-device testing to ensure the platform works consistently across different environments
• Report defects with precision: clear steps to reproduce, expected vs actual behaviour, screenshots or screen recordings, severity classification, and environment details - a developer should be able to reproduce the bug from your report alone
• Verify bug fixes after developers resolve them - retest the specific issue and run related regression checks to confirm nothing else was affected

API & integration testing

• Perform basic API testing using tools like Postman: validate request/response structures, status codes, error handling, and data accuracy
• Test integrations between platform modules and with third-party services - ensure data flows correctly across systems and edge cases are handled
• Validate database-level data integrity for critical workflows - confirm that what the UI shows matches what's stored

Release quality & sign-off

• Own the quality gate for releases: no build goes to production without your sign-off based on completed test execution and acceptable defect status
• Prepare release test reports: test cases executed, pass/fail rates, open defects, risk assessment, and go/no-go recommendation
• Coordinate with developers on defect priority and resolution timelines during release cycles - balance thoroughness with release deadlines
• Support UAT coordination with the implementation team when client-specific testing is needed before go-live

Process improvement

• Identify recurring defect patterns and raise them with the engineering team - if the same type of bug keeps appearing, the process needs fixing, not just the code
• Improve and standardise testing processes: checklists, test templates, bug reporting standards, and regression suites
• Document testing procedures and best practices so the QA process is repeatable and not dependent on one person's knowledge
• Collaborate with developers to shift quality left - help them understand common failure points so fewer bugs reach QA in the first place