QA Engineer Web and Mobile

TechsoIT

Kochi, Kerala, India

Caretech360.ai | PracticeOS | Job description

PracticeOS Quality Assurance

Experience: 4–5 years in software testing

Location: Kochi, Kerala, India

On-site
Full-time

Reports to: Engineering Lead / QA Lead

About Caretech360 and PracticeOSWe are building PracticeOS for small and mid-size medical practices. It connects patient acquisition, engagement, clinical coordination, practice operations, knowledge and training, and intelligence in one platform. It works alongside the EHR as a system of action, knowledge and intelligence, with integrations that connect records to daily work.

The platform includes marketing and CRM, intake and patient communication, prior authorization and coding support, injury care referrals, PACS and imaging, tasks and scheduling, staff onboarding and training, inventory, vendor management, IT and compliance, and analytics. AI assistants and agents help users find information, draft actions and coordinate work with human review. Product maturity varies by module; these roles support both existing experiences and new releases.

The roleOwn hands-on testing of PracticeOS web and mobile experiences, APIs and connected workflows. Work with product, designers and developers to define acceptance criteria, find failures early and give clear evidence of release readiness. The role combines strong manual and exploratory testing with practical automation of stable, high-value regression scenarios.

Core responsibilities· Turn requirements, designs and user journeys into test scenarios and acceptance checks. Cover happy paths, exceptions, permissions, integrations and workflow transitions.

Perform functional, exploratory, integration, smoke, regression and UAT support across desktop browsers, responsive layouts and mobile devices.
Log reproducible defects with steps, expected and actual results, screenshots or recordings, environment details and impact; verify fixes and affected workflows.

PracticeOS testing scope· Test inquiry and referral capture, CRM handoffs, intake submission, patient communication and appointment coordination; verify data reaches the correct record.

Test clinical coordination and prior authorization stages, ownership, deadlines, note correction, submission, approval and scheduling. Check both authorization-required and not-required paths using approved sample rules.
Test injury case referrals, external record uploads, PACS study association and viewer interactions, and access for internal and external roles using synthetic or approved de-identified data.
Test staff onboarding, training assignment and completion, knowledge review and publishing, task creation, inventory and operational workflows for assigned release scope.
Validate backend role permissions and tenant isolation, not only UI visibility. Check direct API access, record ownership, upload and download access, notifications and audit entries.
Test APIs using Postman or equivalent: authentication, schema and payload validation, status codes, pagination, error handling, retries and duplicate events. Use SQL to verify data integrity and state changes.
Test AI features against approved scenarios and expected behaviors. Check context, sources where applicable, draft versus committed actions, approval gates, invalid outputs, unavailable services and safe recovery.
Validate voice and mic interactions where supported, interrupted intake, session expiry, upload limits, slow connections, mobile touch behavior and cross-browser rendering.
Check accessibility basics, including keyboard navigation, visible focus, labels, validation messages and contrast. Collaborate on specialist security, accessibility and performance reviews.
Build and maintain API and UI regression automation; run reliable suites in CI, report failures, and investigate flaky tests. Track release coverage, critical defects and remaining risks.

Required skills and experience· 4–5 years of hands-on testing experience for web applications, with mobile or responsive testing experience and strong manual test design.

API testing with Postman or equivalent and SQL skills for validating records, relationships and transactional updates.
Hands-on automation experience with Playwright, Cypress, Selenium or a comparable framework; ability to maintain tests using JavaScript, TypeScript or another relevant language.
Understanding of authentication, role-based access, multi-tenant applications and integration testing; experience with Git and CI test execution.
Clear defect reporting, risk-based regression selection and ownership of test execution through release; effective collaboration with developers and product teams.

Preferred qualifications· Healthcare software experience, including practice workflows, EHR integrations, prior authorization, patient portals or imaging.

Native mobile testing or Appium experience; familiarity with real-device and emulator testing.
Exposure to AI or LLM evaluation, asynchronous jobs, webhooks, file processing, performance tools and accessibility testing.
Experience testing React front ends, Node.js APIs and PostgreSQL-backed applications; familiarity with FHIR, HL7 or DICOM integration scenarios.

First 90 days· Days 1–30: Understand the product and environments; map critical journeys and role combinations; establish test data, a defect baseline and a release smoke checklist.

Days 31–60: Build a repeatable regression suite for agreed priority modules, API checks and permission tests; automate stable critical paths and support UAT.
Days 61–90: Integrate agreed automated checks into CI, validate an assigned release, document remaining risks and improve coverage based on defects and usage.

Expected outputs and success measuresMaintain a test plan, journey-based test cases, synthetic test data, API collections, automated regression checks, defect reports and a concise release quality summary. Measure critical-path coverage, defect escape patterns, reproducibility, regression reliability and timely risk reporting. Release recommendations should identify what was tested, what remains untested and any unresolved high-impact defects.

How to applySubmit your resume with examples of web and mobile testing, API and SQL validation, and automation work. Describe your personal role in a release, a significant defect you found and how you selected regression coverage. Use sanitized examples that contain no client data or credentials.

Selection processExperience review, a practical test-design and defect-analysis discussion using a sample PracticeOS workflow, and an API or automation exercise. Final discussion covers collaboration and release ownership.

Working arrangementsFull-time, on-site in Kochi, with working-hour overlap for the US team. Compensation will be discussed during the hiring process. The reporting line will follow the engineering and QA team structure

Score my resume against this job, free →