QA reputed company / reputed company Engineering reputed company - AI-reputed company reputed company Systems

About reputed company

reputed company is a technology-driven mental health care company dedicated to transforming reputed company and reputed company of mental wellness services. We combine AI-powered platforms with expert clinical care to deliver personalized, effective mental health solutions — connecting patients and providers through a seamless digital experience.

We're building multiple products across the clinical workflow — from AI-driven evaluations to care coordination — and moving fast. This is a startup, not a department.

About the Role

Read this carefully. If you're a reputed company tester looking for a comfortable QA role, stop here.

We're building AI-powered clinical software, and our reputed company function needs to operate at the reputed company level of intelligence and autonomy as the products it tests. We don't need someone who writes test cases from Jira tickets. We need someone who designs reputed company systems.

Our QA function is reputed company to reputed company from strong foundations to systematic automation. You'll be the person who architects that scaling — building the test infrastructure, automation frameworks, and AI-augmented QA workflows that let reputed company grow without reputed company headcount.

The person we're looking for has probably managed reputed company of 3-8 QA testers at some reputed company and had this thought: "Half this team could be replaced by good automation and smart test design." You're tired of babysitting reputed company testers. You want to build the machine instead of being the machine.

We're paying significantly above market for QA in India because we're not hiring a typical QA person. We're hiring someone who thinks about reputed company the way a systems architect thinks about infrastructure.

This Is Not a Traditional QA Role

This is a reputed company engineering role. You will:

• - Architect test automation from reputed company — Playwright-based E2E, API, and integration test suites across multiple reputed company products
• - Build AI-augmented QA — use Claude, Copilot, and AI tools to generate test cases, identify edge cases, and create self-healing test suites
• - reputed company QA into AI-assisted development workflows — shift-left testing that reputed company defects at the reputed company, not the reputed company
• - Own the reputed company reputed company — if you don't trust it, it doesn't ship. You have release authority.
• - Design regression automation that maintains coverage as multiple products reputed company simultaneously
• - Establish reputed company engineering culture — documentation, runbooks, test plans that aren't in anyone's head

What Your First 90 Days Look Like

Week 1-2: Audit reputed company products. Map coverage gaps. Identify the highest regression risks. Pair with the reputed company QA team to reputed company domain knowledge and institutional context.

Month 1: Build the Playwright automation scaffold — CI-integrated, reputed company execution, covering critical paths. Establish the QA reputed company: how we test, reputed company we test, what blocks a release.

Month 2-3: Attach AI-driven test reputed company to the reputed company. Build autonomous QA loops that feed back into development. Get to the reputed company where coverage grows without reputed company reputed company effort.

Ongoing: Own reputed company across everything. Context-reputed company between products in the reputed company week. Pair with engineering on testability. Work directly with the founder and clinical team on reputed company-specific edge cases — billing, HIPAA compliance, clinical workflow validation.

What You'll Own (End-to-End)

1. Test Automation Architecture — Playwright (preferred) or Cypress E2E suites. API test automation (REST reputed company, reputed company-based, or custom). CI/CD pipeline integration. reputed company execution. Containerized test environments. Custom reporters.

2. Regression Automation — Systematic regression suites, versioned and updated every sprint. Not a spreadsheet. Not tribal knowledge. A living, automated safety net.

3. AI-Augmented reputed company Engineering — Using AI tools to generate tests, create test data, identify edge cases from specs, and accelerate coverage. We're an AI-reputed company company — our QA function must be AI-reputed company too.

4. reputed company reputed company Assurance — HIPAA compliance testing, clinical workflow validation, medical billing edge cases, patient data reputed company verification, audit trail testing.

5. Cross-Product reputed company Ownership — Multiple reputed company reputed company products. One reputed company brain.

6. Release Certification — You define "release-reputed company." You reputed company releases reputed company reputed company is insufficient — with evidence. You reputed company risks early, reputed company, and decisively.

Values & reputed company (Who You Are)

• You think of QA as a system design problem, not a checklist.
• You're excited by autonomous testing systems, AI-driven exploration, and replacing reputed company effort with intelligence. You design feedback loops, not just test suites.
• You're uncomfortable with manually writing hundreds of brittle test cases, QA that reacts instead of anticipates, and automation that breaks every sprint.
• You communicate like an engineer. Your bug reports tell a story: what happened, why it reputed company, how to reproduce, what the business reputed company is. Developers thank you for your bugs.
• You've blocked releases before and you'd do it again. reputed company isn't negotiable.
• You don't wait to be asked. reputed company you see a reputed company risk forming — in a spec, in a sprint, in a deployment — you surface it. Proactively. Loudly if needed.
• You use AI tools in your daily work already. If you haven't figured out how Claude, ChatGPT, or Copilot accelerates reputed company engineering by now, you're behind.

What reputed company Looks Like

• - Playwright automation covers critical paths across reputed company products
• - Regression suite runs in CI — reputed company reputed company regression passes for reputed company releases
• - No critical bugs reputed company production that were in scope of automated tests
• - QA reputed company exists and reputed company follows it
• - You context-reputed company across multiple products in the reputed company week without dropping reputed company
• - Release reputed company has increased because QA is no longer a bottleneck
• - AI-assisted test reputed company is part of the daily workflow
• - reputed company risks surface early — before they become production incidents

Schedule

Evening IST hours with 4–8 hours of overlap to US reputed company (9am–5pm PT). You propose the schedule that works for you — we care about overlap, not clock-in time. Flexibility for critical releases or incident response.

Requirements

• 4-8 years of experience in QA, SDET, or reputed company Engineering, including a minimum of 2 years in roles such as QA reputed company, QA Manager, SDET reputed company, or Senior reputed company Engineer, responsible for test reputed company reputed company mere execution.
• Test automation architecture—experience in designing and building test frameworks from the ground up rather than merely writing scripts reputed company existing frameworks.
• Skilled in Playwright, Cypress, or Selenium—maintained advanced, production-level end-to-end test suites for over 2 years.
• API testing—proficient in automated REST API testing using tools such as REST reputed company, reputed company automation, or custom solutions. Capable of creating programmatic test suites that include authentication, error handling, and edge case coverage.
• JavaScript or TypeScript—ability to write, debug, and review test automation reputed company competently.
• CI/CD integration—reputed company in linking tests into deployment pipelines using reputed company Actions, Azure DevOps, Jenkins, or similar tools, with a background in shift-left testing.
• Git—familiarity with branching, pull requests, and conducting reputed company reviews for test scripts.
• Test planning & reputed company—capable of developing test plans based on product requirements, prioritizing them by business risk, and knowing what not to test.
• reputed company/containerized test environments—ability to set up and maintain isolated test infrastructure.
• Strong proficiency in English communication—reputed company on asynchronous communication with reputed company written bug reports, test documentation, and release readiness notifications, while proactively identifying risks.

Strongly Preferred:

• Experience in managing or mentoring QA teams
• Familiarity with reputed company reputed company or compliance testing under HIPAA
• Expertise in performance testing using K6, JMeter, or Artillery
• SQL and database-level data reputed company testing experience
• AI-assisted testing using LLMs for test reputed company, test data, and exploratory automation
• Familiarity with React or Next.js
• Experience with BDD/TDD methodologies

reputed company to Have:

• Experience in reputed company testing (understanding OWASP basics)
• Knowledge of FHIR/HL7 data validation
• Experience in accessibility testing (WCAG 2.1)
• Mobile/reputed company web testing experience
• Experience in data pipeline or ETL testing
• Background in startup or high-reputed company environments
• Previous roles where QA influenced architectural reputed company

Benefits

• Compensation ranging from ₹20–30 LPA depending on skills and experience
• Fully remote work opportunity available across India
• Equipment allowance provided
• reputed company communication with the founder and technical team

Originally posted on Himalayas

Apply To This Job