Manual QA Tester

Keelzo is an AI-driven global recruiting platform that actively discovers talent, guides recruiters intelligently, and gives candidates full visibility into the hiring process. The platform handles everything from AI-matched job postings and automated assessments to structured hiring pipelines, offer management, and candidate feedback — all in one place.

When something breaks on Keelzo, it doesn't just disrupt a workflow. It affects a candidate's job search, a recruiter's credibility, and a company's ability to hire. That is the weight of what you will be testing.

The Role
We are looking for a meticulous Manual QA Tester who can independently own testing across the Keelzo platform. You will work directly with the Co-founder, be embedded in the product cycle from the start, and be the person who ensures nothing reaches a real user before it's ready.
This is not a role where you inherit a test suite. You build it.

Product Domain
You will be testing across an HR Technology platform and a healthcare insurance domain — two product areas that handle sensitive user data, complex workflows, and high-stakes decisions. Attention to detail, domain curiosity, and an understanding of how real people use these products are essential

What You Will Do
• Write detailed, independent test cases from requirements, design specs, and user stories, covering happy paths, negative scenarios, boundary conditions, and edge cases without hand-holding
• Execute thorough manual testing across all product features and end-to-end user workflows for both recruiter-facing and candidate-facing experiences
• Validate complete user journeys, not just individual features in isolation, but the full flow as a real user would experience it
• Test automated email and notification triggers, verify the right communication fires at the right time, to the right person, with the correct content
• Validate AI-driven features, test scoring logic, ranking outputs, and AI-generated content for consistency, accuracy, and graceful handling of edge cases
• Log defects clearly and completely, steps to reproduce, expected vs actual behaviour, severity, environment, and supporting evidence that a developer can act on immediately
• Retest resolved defects and perform regression testing before every release
• Participate in sprint planning and reviews, flag high-risk areas early, raise questions on testability during feature design, and provide QA estimates for sprint capacity
• Maintain clean test documentation test plans, coverage matrices, test run results, and release sign-off records
• Communicate defect status and testing progress clearly and proactively to the Co-founder and development team

• 4+ years of manual QA or software testing experience on commercial products
• Hands-on experience testing SaaS platforms — you understand role-based access, multi-step workflows, subscription flows, and the complexity of testing systems handling real user data
• Experience testing HR technology, recruiting software, or healthcare/insurance products is a strong advantage — domain familiarity shortens ramp-up time and improves test coverage from day one
• You can write test cases independently — from a requirement, a wireframe, or a conversation, you produce a complete, structured test case that covers what others miss
• You think like a user, not just a tester — you go beyond the obvious paths and ask "what would someone actually do here?"
• Clear, precise defect reporting — your bug reports are complete, reproducible, and actionable without a follow-up call
• Comfortable working directly with founders — no QA management layer; your observations go straight to the people who act on them
• Self-managed and async-capable — remote-first means you hold yourself accountable to outcomes, not just availability
• Kerala-based candidates are strongly preferred — you understand the local context, and being in the same time zone as the core team makes a real difference

Testing Skills Required
• Strong manual testing fundamentals — test case design, test planning, and structured test execution
• Ability to write and maintain test cases, test plans, and coverage matrices independently
• Functional testing — validating that features work exactly as specified across all user roles and permission levels
• Workflow and end-to-end testing — tracing complete user journeys across multiple features and system boundaries
• Regression testing — maintaining and executing a regression pack before every release to ensure nothing that worked before has stopped working
• Exploratory testing — going beyond scripted cases to uncover defects that formal test cases don't anticipate
• Boundary value analysis and equivalence partitioning — structuring test inputs systematically to maximise coverage
• Negative testing — deliberately testing invalid inputs, interrupted flows, and system limits to find failure behaviour
• Defect lifecycle management — logging, prioritising, tracking, and retesting defects through to verified closure
• Basic API testing using tools like Postman — validating endpoint behaviour, response integrity, and error handling without relying solely on the UI
• Cross-browser and cross-device testing — ensuring consistent behaviour across major browsers and screen sizes
• Clear written communication — test reports, release sign-off documents, and defect descriptions that stakeholders at all levels can understand.