QA Tester (WFH)

About the job:Key Responsibilities:

1. Create and execute test cases for new features and existing workflows.

2. Perform functional, regression, integration, API, and cross-browser testing.

3. Test Python backend APIs, React frontend features, and PostgreSQL data flows.

4. Write SQL queries to verify data and investigate defects.

5. Report bugs with clear reproduction steps, expected results, and supporting evidence.

6. Retest fixes and support testing before each release.

7. Identify opportunities to automate repetitive tests.Who can apply:Only those candidates can apply who:have minimum 1 years of experienceare Computer Science Engineering studentsSalary:₹ 4,50,000 - 7,00,000 /yearExperience:1 year(s)Deadline:[hidden]:59:59Other perks:Health InsuranceSkills required:Python, SQL, Software Testing, Manual Testing, PostgreSQL, React, APIs and Bug TrackingOther Requirements:1. Candidates with 2–3 years of hands-on QA experience who have tested web applications and can investigate issues across the frontend, backend, and database.2. Experience using tools such as Postman and Jira is preferred.3. Experience writing automated tests using Python, Selenium, Playwright, or a similar tool.About Company:Finflock Systems is a leading fintech startup combining the power of advanced technologies such as cloud computing, machine learning, and AI with mathematics, statistics, and operations research. The company generates state-of-the-art decision-enabling analytics and superior research intelligence via its various products, platforms, and services. It offers scalable intelligent solutions for businesses in the finance industry of all sizes.

Responsibilities

Key Responsibilities:

1. Create and execute test cases for new features and existing workflows.

2. Perform functional, regression, integration, API, and cross-browser testing.

3. Test Python backend APIs, React frontend features, and PostgreSQL data flows.

4. Write SQL queries to verify data and investigate defects.

5. Report bugs with clear reproduction steps, expected results, and supporting evidence.

6. Retest fixes and support testing before each release.

7. Identify opportunities to automate repetitive tests.