Skip to content

Quality

QA Engineer

Build QA as a discipline here, not just run it: functional testing, UAT coordination, and regression coverage for platforms that ship every week.

Jaipur, India · remote friendly (IST)Full-timeFunctional, UAT, regression — a new capability you'll define

The role

QA is a new capability at Narix — you'll be its first owner, which means defining how quality works here, not inheriting someone's process. The products ship weekly, so quality has to be a system: test plans that catch what matters, regression coverage that makes releases boring, and UAT coordination that keeps clients confident. You'll work across every product we deliver, closest to the engineers, with the standing to hold a release when it isn't ready.

Role details

What you'll do

  • Own functional testing across our client platforms: test plans, execution, and clear defect write-ups engineers can act on
  • Build the regression suite — prioritized by risk, automated where it pays (Playwright or similar), maintained as the product moves
  • Coordinate UAT with clients: scenarios, schedules, and sign-off that means something
  • Define the release gate: what gets checked, what blocks, and what ships — and hold the line when it matters
  • Make quality visible: coverage, escape rate, and the metrics that tell us whether QA is working

What you bring

  • 3+ years in QA on real products: functional, regression, and UAT experience
  • You write defect reports developers thank you for — reproducible, scoped, prioritized
  • Hands-on automation experience with a modern framework (Playwright, Cypress, or similar)
  • Comfort testing APIs directly, not only through the UI
  • The judgment to say "this isn't ready" clearly and diplomatically — and the standing to make it stick

Nice to have

  • Experience testing LLM-powered features, where 'correct' is a distribution, not a string match
  • Experience being the first or only QA in a team — building the function, not joining it
  • Performance or accessibility testing exposure

You'll work with

PlaywrightAPI testingTest planningUAT

What you get

The deal, plainly

Define a discipline: you're the first QA hire, and the function will look the way you build it

Senior-led delivery: your work is reviewed by people who've shipped production systems, and you see how they think

An AI-native workflow — modern AI tooling is standard practice here, with human review as the quality bar

Real products in production: client work that ships weekly and gets used, not internal demos

Async-first, writing-heavy culture on IST, with deliberate US/EU overlap instead of late-night calls

How we hire

Four steps, no gauntlet

  1. Apply

    Send the form on the role page — the cover note and links matter far more than a perfectly formatted CV.

  2. Intro call (30 min)

    A real conversation about the role, your work, and whether the fit is mutual. No trick questions.

  3. Practical round

    A scoped, role-relevant exercise or portfolio deep-dive — designed to respect your time, not a weekend of free work.

  4. Founder conversation & offer

    You meet the person you'll actually work with. If it's a yes on both sides, we move fast.

Apply

Apply — QA Engineer

The cover note and links matter far more than a perfectly formatted CV. We read every application.