Build and own the automation framework and the regression suite that decides whether a release reaches production. You are the person who can stop a deployment, and that authority is real.
Apply now
Location
Greater Noida
Hybrid
Type
Full time, permanent
Reports to
Head of Engineering
Experience
4+ years
Why this role
Test a system you are not allowed to read the data in.
01
Release-gating authority that is genuinely enforced
02
In the design conversation, not handed finished features
03
Adversarial testing of an append-only, tamper-evident ledger
04
Failures here are logical rather than visual
The work
What you'll actually do
01
What you'll own
The framework: API and UI automation, built as a codebase with the same standards as the product
The regression suite — quick enough that people run it, trustworthy enough that a red build means something
Release gating:
pre-production validation and the criteria for going to production, defined and enforced
Contract and integration tests across services and across the boundary with connected organisations
Quality signal: defect triage, coverage and escape metrics that leadership can act on rather than admire
02
The hard part
Testing blind — your test data strategy, fixtures and failure diagnosis all have to work without looking at the payload
Proving a negative: testing that the ledger works is easy; testing that it cannot be quietly subverted is the actual job
Withdrawal propagation — verifying that guarantee across a distributed system, including the failure paths
Consequence: a defect here is not a bad release, it is a reportable event with a regulator attached
03
Minimum qualification
4 years building test automation as software, or 3 years with an advanced degree — or equivalent practical experience
You have designed an automation framework from scratch, not only written tests insid