QA Lead
The Role
We're hiring a QA Lead to own quality across the entire engineering organisation.
This is a player-coach, IC-lead role. You won't manage a large QA team on day one —
you'll build the foundation. That means designing the automation architecture,
establishing the QA Guild, and working directly inside squads to raise the quality bar
from the ground up.
Every squad currently has (or will have) an embedded QA engineer who sits day-to-
day with that squad. You are their dotted-line manager: you set the standards, tooling,
and frameworks they work within — while each embedded QA's solid-line reporting
stays with their squad lead.
Key Responsibilities
QA Guild & Standards
Establish and lead the QA Guild — the cross-squad forum where embedded QAs
align on tooling, frameworks, and practices.
Define and maintain the organisation-wide test strategy: what gets unit tested,
what gets integration tested, what gets E2E tested, and where those tests live in
the CI pipeline.
Set coverage standards and review embedded QAs' work against them
Document and evangelise testing best practices across the engineering org
Automation Architecture
Design the automation framework for the codebase (currently Vitest for unit tests,
GitHub Actions for CI)
Build out integration test coverage for the tRPC API layer — the backbone of all
frontend-to-backend communication
Establish E2E test coverage for critical user flows in the Next.js web app (flow
creation, trigger setup, target configuration, webhook delivery confirmation)
Define testing patterns for SQS-driven async workflows — these are the most
failure-prone paths in the system (webhook ingestion → queue → Lambda
consumer → delivery)
Embedded QA Coordination
Dotted-line manage embedded QA engineers across Platform, Apps, and Custom
squads
Review and approve the test approaches embedded QAs propose for each squad's
work.
Ensure embedded QAs have the tooling, training, and runway to be effective within
their squads
Be the escalation point when a squad's embedded QA identifies a systemic quality
issue
Hands-On Testing
Own testing for high-risk releases — especially database schema migrations
(Drizzle ORM, MySQL), new third-party connector additions, and changes to the
core webhook delivery pipeline
Perform exploratory testing on new features before they ship to production
Write and maintain test suites where no embedded QA is yet in place
CI/CD & Release Quality
Work with the Platform Squad to harden the GitHub Actions CI pipeline
Define the quality gates that must pass before code reaches staging and
production
Monitor test flakiness and own the process for keeping the test suite trustworthy
Requirements
Proven experience designing and implementing test automation frameworks from
the ground up — not inheriting one, building one.
Strong TypeScript skills — tests in this codebase are TypeScript-first, no
exceptions.
Experience testing REST APIs and webhook-based integrations — you need to
understand request/response cycles, payload schemas, and failure modes.
Familiarity with CI/CD pipelines and defining quality gates within them (GitHub
Actions experience preferred).
Experience with async/event-driven systems — SQS, queues, retry logic, eventual
consistency; these are where the hardest bugs hide
Ability to read and understand application logs to diagnose failures (CloudWatch,
structured JSON logs)
Experience in a player-coach or lead capacity — you've mentored other QA.
Pay: ₹1,000,000.00 - ₹1,100,000.00 per year
Application Question(s):
- 1. How many years of experience do you have as a QA Lead ?
2. Do you have a strong exposure in Typescript skills test ?
3. Are you familiar with CI/CD Pipelines and Github Actions ?
4. Do you have experience with async/event-driven systems — SQS, queues, retry logic, eventual Consistency ?
5. What is your current ctc ?
6. What is your expected ctc ?
7. What is your official notice period ?
Work Location: Remote
