๐ฏ Kuku FM is hiring QA Engineers (Manual & Automation) in Bengaluru! If you have 1โ3 years of software testing experience and enjoy working across mobile, web, APIs, automation, and payment workflows, this opportunity could be relevant to your profile. The role combines strong manual-testing fundamentals with automation using Rest Assured, Cucumber, Selenium, and Postman.
๐ Job Details
๐ข Company: Kuku FM / Kuku
๐ผ Role: QA Engineer โ Manual & Automation
๐ Location: Bengaluru, Karnataka
๐งโ๐ป Experience: 1โ3 Years
๐ง Work Areas: Mobile Testing, Web Testing, API Testing, Automation, Payment Testing
โ๏ธ Automation: Rest Assured, Cucumber, Selenium, Postman
๐ณ Domain: Payments / Fintech exposure preferred
๐ Employment: Full-time
๐ฐ Expected Salary: Approximately โน8โ15 LPA, based on a current public listing for this specific Kuku FM QA Engineer role; actual compensation can vary according to experience, interview performance and company offer.
๐ข About Kuku
Kuku is an Indian mobile-first storytelling and content company founded in 2018. Its ecosystem includes Kuku FM, Kuku TV, Storizz, Wow TV and Guru, covering audio, video, short-form storytelling and learning. Kuku says its platforms have reached 400M+ installs across 1,000+ cities and towns, while Kuku FM focuses on audio storytelling across fiction, romance, mythology, self-growth and other categories.
For a QA professional, this means exposure to a consumer-facing product where reliability across mobile applications, backend APIs and user journeys can directly affect the customer experience.
๐ก Why This Role Is Good for Your Experience
This is not limited to writing basic manual test cases. The JD covers a broad QA engineering workflow. You would work with mobile, web and API testing, while also contributing to BDD automation frameworks.
๐ณ The payment-testing component is particularly useful because you would validate complete journeys such as Login โ Cart โ Checkout โ Payment โ Confirmation, along with UPI, cards, net banking and wallets.
๐ You would also test payment failures, timeouts, retries, refunds, reversals and duplicate transactions, giving you practical experience with negative testing and real-world transaction scenarios.
๐ ๏ธ Backend validation using server logs and database checks can strengthen your debugging and API-testing skills. Working with developers to reproduce defects also gives you experience beyond traditional test execution.
๐งโ๐ป Skills Required
๐น Manual Testing across Mobile, Web and API applications
๐น Strong understanding of STLC and Defect Life Cycle
๐น Test-case, test-scenario and test-plan preparation
๐น Functional and regression testing
๐น API testing using Postman
๐น Automation with Selenium
๐น REST API automation using Rest Assured
๐น BDD concepts and Cucumber
๐น SQL/database validation
๐น Server-log analysis and defect debugging
๐น Payment gateway testing concepts
๐น Risk-based testing and traceability matrices
๐น Strong communication and collaboration
๐น Ability to understand requirements and identify edge cases
๐ฏ Preparation Tips
๐ฑ 1. Prepare mobile-testing scenarios: Be ready to explain how you would test an audio/content application, including login, search, playback, downloads, network changes, interruptions and subscription-related flows.
๐ณ 2. Master payment testing: Prepare scenarios for successful and failed UPI/card transactions, timeout, retry, refund, reversal and duplicate-payment situations. This is one of the most role-specific areas in the JD.
๐ 3. Revise API testing: Practice GET, POST, PUT and DELETE requests, status codes, headers, authentication, request/response validation and negative API testing.
๐ค 4. Revise automation: Understand Selenium, Cucumber BDD structure and Rest Assured. Be prepared to explain how you would design maintainable automation rather than simply writing individual scripts.
๐๏ธ 5. Practice SQL validation: Know SELECT queries, WHERE, JOIN, GROUP BY and basic data validation because the role specifically mentions database checks.
๐ 6. Prepare real defect examples: Have 2โ3 examples ready covering how you identified a bug, reproduced it, collected evidence, communicated with developers and verified the fix.
๐ Resume Tips
๐ Put QA Engineer / Software Testing prominently in your resume headline.
๐ Mention Mobile + Web + API Testing instead of only saying “Manual Testing.”
๐ Add specific tools such as Selenium, Rest Assured, Cucumber and Postman wherever you genuinely have experience.
๐ If you have worked on payments, mention specific scenarios such as UPI, cards, refunds, failed transactions or payment gateways.
๐ Include measurable automation achievements, such as test cases automated or regression execution time reduced.
๐ Highlight SQL, database validation and log analysis if applicable.
๐ Describe projects using action + technology + result, rather than generic responsibilities.
๐งฉ Expected Interview Rounds
1๏ธโฃ Recruiter/Initial Discussion: Resume, experience, notice period and role fit.
2๏ธโฃ QA Technical Round: Manual testing, STLC, defect life cycle, test scenarios, API testing, SQL and automation.
3๏ธโฃ Practical/Domain Discussion: Payment-testing scenarios, automation framework and debugging situations.
4๏ธโฃ Hiring Manager/Final Discussion: Project experience, communication, ownership and collaboration.
๐ How to Apply
Interested candidates can DM toย Sowmya KSย and share updated resume if their experience matches the job requirements.
๐ฉ The hiring post asks interested candidates to DM to Sowmya KS apply or refer someone suitable. Keep your latest resume ready and clearly mention your experience, Bengaluru availability, automation tools, API-testing experience and payment-testing exposure.
๐ฅ Final Takeaway
The Kuku QA Engineer opening is centered around a combination of manual testing + automation + API testing + mobile/web testing + payment validation. Candidates with 1โ3 years of experience should particularly focus on payment edge cases, Rest Assured, Cucumber, Selenium, Postman, SQL and practical defect-debugging examples before interviewing. The publicly listed salary indication for this specific role is โน8โ15 LPA, but the final offer should be confirmed directly with Kuku.
