Lead SDET

Sprinto is an Autonomous Trust Platform that centralizes trust requirements across security frameworks, vendors, and customers.

Sprinto autonomously executes tasks needed to maintain trust across compliance, audits, risk management, vendor risk, privacy, and AI governance, enabling organizations to maintain a strong, reliable trust posture without draining operational bandwidth and resources on repetitive tasks.

Backed by top-tier investors such as Accel, Elevation, and Blume Ventures, we’ve raised $31.8M in funding to fuel our mission. Trusted by over 4,000 organizations across 75 countries, Sprinto helps organizations stay audit-ready, manage real-time risks, and scale fearlessly. With 300+ native integrations and AI-driven automation, Sprinto supports 200+ global security standards natively, including SOC 2, ISO 27001, GDPR, HIPAA, PCI-DSS, and more. Sprinto's extensible architecture enables organizations to build and support an infinite number of custom integrations and frameworks.

Founded in 2020 by second-time founders Girish Redekar and Raghuveer Kancherla, Sprinto powers compliance for organizations like Whatfix, Encora, Anaconda, Whatnot, Ultrahuman, WeWork, Everstage, AI Foundation, HackerRank, and many more.

Life as a Sprinter -

Nobody succeeds at Sprinto by staying in their lane.

We are organized around problems, not job titles. Sprinters take ownership beyond their role, solve hard problems, and care deeply about the impact they create. If something can be improved, fixed, or built, we don't wait for permission; we step in.

Being remote means we rely less on proximity and more on trust. We write things down, communicate openly, and move quickly because great teams aren't built by sitting together, they're built by pulling in the same direction.

We believe progress beats perfection, feedback is a gift, and doing the right thing matters, even when nobody is watching.

And while we move with urgency, we never move alone.

The mission -

Where you'll leave your mark?

• Own quality outcomes, not activities - the question is never "how many test cases did you write this sprint," it's "what quality metric moved and what did you build to move it."
• Drive CI pass rate to 90%+ and keep it there - the percentage of pipeline runs that pass without manual intervention.
• Own bug leakage rate - target under 2-3% of bugs escaping QA to staging or production, with a root cause analysis you own for every bug that gets through.
• Build the system that keeps flaky tests out of the suite - preventing flakiness from entering and quarantining it when it does.
• Shape automation coverage at the right layer - E2E where it matters, API where it's faster and more reliable, unit where developers should own it - not just chasing a coverage percentage.
• Stay 50-60% hands-on - writing Playwright TypeScript to evolve the framework, building diagnostic tools that analyse test-run data for flakiness patterns, and reviewing PRs to catch structural problems in AI-generated test code.
• Build AI-native quality infrastructure - systems that use LLMs, agents, and AI tooling to solve quality problems at scale, like pipelines that auto-analyse every PR for risk across security, product, and UX dimensions.
• Deliver engineering-wide quality impact - at least one initiative per quarter that changes how developers or PMs ship, not just how QA tests. Our current guardrail system prevents 90 bugs per month without manual QA; that's the bar.
• Partner and present - sit with product engineers to define quality gates before features ship, and present quality metrics (CI pass rate, bug leakage, flaky test trends) to engineering leadership.

The kind of builder we're looking for -

• An engineer who has chosen quality as their specialisation - this is not a pure coding role and not a management role; it lives exactly in between (~40-50% strategy, cross-functional collaboration, and mentoring).
• Engineering-wide in scope, not QA-internal - you want to improve how the entire engineering organisation thinks about quality, not just how the QA team works.
• AI-native, not AI-assisted - you don't just use Copilot for test authoring; you build quality systems on LLMs and agents, and you can test AI features themselves - validating agent behaviour, checking LLM output quality, and handling non-deterministic systems.
• A test pyramid thinker, not just an E2E automator - with developers now writing feature automation themselves, you push testing responsibility to the developer layer while QA owns integration, workflow, and AI feature quality. A candidate who only thinks Playwright and E2E is too narrow.
• Fluent in the modern stack - Playwright, TypeScript, CI pipelines, and the data behind them.
• Comfortable influencing without authority - defining quality gates with product engineers and changing developer behaviour through systems, not mandates.