QA Automation Engineer
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.
Test a system you are not allowed to read the data in.
Release-gating authority that is genuinely enforced
In the design conversation, not handed finished features
Adversarial testing of an append-only, tamper-evident ledger
Failures here are logical rather than visual
What you'll actually do
What you'll own
- The framework: API and UI automation, built as a codebase with the same standards as the product
- The regression suite — fast 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
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
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 inside somebody else's
- Strong programming in Python, TypeScript or Java — an engineer who specialises in testing, not a tester who scripts
- Playwright, Cypress or Selenium at depth, and API testing with RestAssured, Postman/Newman or equivalent
- Tests wired into CI as a gate that can genuinely block a release
- Test design as a discipline: risk-based coverage, boundary and negative cases, and the judgement to say what is not worth automating
- Hands-on use of AI-assisted testing tools, and a clear view of where they help and where they lie
Preferred
- Contract testing between services — Pact or equivalent
- Performance and load testing with JMeter, k6 or Locust, and the ability to interpret the numbers
- Security testing fundamentals: OWASP Top 10, authentication and authorisation edge cases, injection paths
- Mobile test automation, ideally Flutter
- ISTQB certification
How we work
- Hybrid working style with anchor at our Grandthum office in Greater Noida, Tech Zone IV
- Defined core collaboration hours — outside that, flex your day around its natural shape
- Architecture decisions get written down and argued in the open. Small, reviewable changes. Depth is valued over volume
- Company-issued devices and approved tooling for anything touching customer or compliance data. Given what we build, we hold ourselves to the standard we sell
The practical details
- Location: Grandthum, Tech Zone IV, Greater Noida West, Gautam Buddha Nagar, Uttar Pradesh
- Employment type: full-time, permanent
- Reports to: Head of Engineering
- Education: B.E./B.Tech or M.Tech in CS/IT, or equivalent demonstrated experience — we mean the second part
- Offers are subject to standard background verification, which we will explain before we ask for anything
How we'll interview you
- A 30-minute conversation with our Head of Engineering
- A code and architecture discussion on something you have built and can talk about honestly
- A conversation with the founder about the company, the regulation and where this goes
- Four stages. We aim to complete them inside two weeks and to give you a decision either way
You'll thrive here if this sounds like you
Consequence appeals to you rather than frightens you
You think adversarially about systems that claim to be tamper-evident
You want to be in the design conversation, not downstream of it
You build test tooling to the same standard as production code
You are comfortable early: eighteen people, pre-revenue, and a product that must be right before a regulator looks at it
Tell us about yourself
Share a few details and your CV. We read every application, typical response within two weeks.
BUILD THE SYSTEMS
THAT ENABLE PROGRESS.
Partner with ASCENRA to create infrastructure designed for long-term growth.