Are you a QA professional looking for your next career opportunity in software testing or test automation? FreeChargeBiz is hiring QA Engineers – Manual Testing and SDETs – QA Automation to help build reliable, high-quality digital products.
This opportunity is suitable for professionals with 2–3 years of experience who want to strengthen their testing expertise, contribute to product quality, and collaborate with engineering teams in a hybrid work environment. Candidates with manual testing, API testing, database validation, Java, Selenium, and REST Assured experience should explore the role that best matches their skills.
🏢 About FreeChargeBiz
FreeCharge is associated with India’s digital payments and fintech ecosystem, offering digital payment-related services. The FreeChargeBiz name in this hiring announcement suggests a business-focused technology context; however, the exact employing entity, product team, and project responsibilities have not been independently confirmed.
📌 Job Overview
- Company: FreeChargeBiz
- Position 1: QA Engineer – Manual Testing
- Position 2: SDET – QA Automation
- Experience Required: 2–3 years for both roles
- Preferred Location: Bangalore
- Additional Location: Gurugram
- Work Mode: Hybrid
- Manual QA Skills: Functional, regression, integration, system, UAT, REST API, Postman, and database testing
- SDET Skills: Java, Selenium, automation framework development, API automation, and REST Assured
- Salary: Not disclosed in the hiring announcement
- Openings: Number of vacancies not specified
🎯 Why Are These Roles Good for Experienced Professionals?
1. Opportunity to deepen practical QA expertise: Manual QA professionals can strengthen their ability to analyse requirements, identify edge cases, validate business workflows, and manage regression coverage.
2. A pathway towards automation engineering: The SDET position is relevant to testers who want to build maintainable automation frameworks and expand their programming and API testing skills.
3. Exposure to end-to-end quality: Both roles require more than checking whether a feature works. Candidates can demonstrate their ability to identify integration issues, investigate failures, validate data, and prevent defects from reaching production.
4. Stronger technical problem-solving: Postman, SQL, Java, Selenium, and REST Assured provide opportunities to develop debugging and troubleshooting skills that are valuable across technology companies.
5. Fintech-related testing experience: If the assigned project involves digital payments, QA professionals may gain experience testing transaction workflows, error handling, data integrity, and reliability-sensitive functionality.
🧪 Skills Required for Each Position
1. QA Engineer – Manual Testing
- Manual and functional testing: Requirement analysis, test scenarios, test case design, positive and negative testing, and exploratory testing.
- Regression testing: Identifying impacted features and ensuring existing functionality remains stable after changes.
- Integration and system testing: Validating communication between components and checking complete application behaviour.
- User Acceptance Testing (UAT): Supporting business users with scenario validation, issue reporting, and acceptance criteria.
- REST API testing: Using Postman to validate HTTP methods, status codes, headers, authentication, response payloads, and negative scenarios.
- Database testing: Writing SQL queries, validating records, checking data consistency, and verifying backend changes after transactions.
2. SDET – QA Automation
- Java programming: OOP concepts, collections, exception handling, strings, loops, and debugging.
- Selenium WebDriver: Locators, waits, dropdowns, browser handling, web elements, and dynamic application interactions.
- Framework development: Page Object Model, reusable utilities, test data management, configuration, reporting, and maintainable test design.
- API automation: REST Assured, HTTP methods, request specifications, response assertions, authentication, and schema validation.
- Automation strategy: Selecting stable, repeatable test cases for automation and investigating flaky tests.
- Version control and delivery: Git fundamentals and basic CI execution knowledge are valuable additional skills, although they are not explicitly listed as mandatory in the announcement.
💰 Expected Salary Range
- QA Engineer – Manual Testing: ₹4–8 LPA
- SDET – QA Automation: ₹6–12 LPA
These figures are estimates for comparable roles, not verified FreeChargeBiz salary bands. Actual offers may vary based on technical expertise, current compensation, interview performance, location, and the hiring budget. Candidates with strong Java, Selenium, REST Assured, and framework development experience may be positioned differently from candidates focused primarily on manual testing.
🧠 Preparation Tips
For Manual QA candidates:
- Prepare test cases for login, payment initiation, failed transactions, duplicate submissions, session timeouts, and transaction history.
- Practise writing SQL queries to verify transaction records and identify missing, duplicate, or inconsistent data.
- Use Postman to demonstrate positive and negative API testing, response validation, authentication checks, and error handling.
- Revise severity versus priority, defect lifecycle, regression scope, integration testing, and UAT scenarios.
For SDET candidates: - Practise Java coding questions involving strings, arrays, collections, duplicate elements, and exception handling.
- Build a small Selenium framework using Page Object Model, explicit waits, reusable methods, and clear assertions.
- Prepare REST Assured examples covering GET, POST, PUT, and DELETE requests, response codes, JSON validation, and authentication.
- Be ready to explain how you choose automation candidates, organise test data, handle flaky tests, and maintain framework reliability.
- Understand how automated tests can run in a CI pipeline, even though CI/CD is not listed as a mandatory skill.
📝 Expected Interview Rounds
- Recruiter screening: Discussion of experience, preferred role, location, hybrid work arrangements, notice period, and compensation expectations.
- Technical interview: Manual QA candidates can expect testing concepts, scenario-based questions, API testing, and SQL. SDET candidates should prepare for Java, Selenium, framework architecture, and REST Assured.
- Practical assessment: This may involve designing test cases, debugging an automation script, writing SQL queries, or creating API assertions.
- Project or managerial discussion: Expect questions about real project challenges, defect investigation, collaboration with developers, prioritisation, and ownership of quality.
- HR discussion: Compensation, joining timeline, work arrangements, and other employment details may be discussed.
📄 Resume Tips to Improve Your Selection Chances
- Manual QA applicants: Highlight functional, regression, integration, system, UAT, API, and database testing in your skills section.
- SDET applicants: Put Java, Selenium, REST Assured, and framework development prominently near the top of your resume.
- Include real project examples explaining the feature tested, your responsibilities, tools used, and defects identified.
- Quantify achievements wherever possible, such as test cases executed, regression effort reduced, automation coverage improved, or critical issues detected.
- Mention SQL validation and API testing alongside the relevant project rather than listing these skills without context.
📩 How to Apply
👉 Application Link: Click Here
Clearly mention whether you are applying for QA Engineer – Manual Testing or SDET – QA Automation, along with your total experience, current location, preferred location, notice period, and relevant technical skills.
🌟 Final Thoughts: FreeChargeBiz offers two distinct opportunities for QA professionals with 2–3 years of experience. Choose manual testing if your strengths lie in test design, API validation, and database testing; choose SDET if you enjoy Java programming, automation frameworks, Selenium, and API automation. Tailor your resume to the chosen role and prepare practical examples that demonstrate how you contribute to software quality.
