Backend Engineer II
Own the backend of the ASCENRA DPDP Consent Manager platform and set the engineering standard the rest of the team builds to. You report to the Head of Engineering and you are the senior-most backend voice in the company.
Own the backend of a system we are legally forbidden from reading.
Anchor backend hire with real architectural authority
Data-blind by design: a statutory requirement, not a preference
Append-only, tamper-evident ledger provable to a regulator
Lead the handover from our external engineering partner in-house
What you'll actually do
What you'll own
- Consent lifecycle — notice, grant, review, renewal and withdrawal, the core state machine of the product
- The ledger and receipts: append-only, tamper-evident records, machine-readable, retained seven years
- Event flows — Kafka/MSK topics and idempotent consumers carrying consent state between services
- Data model and tenant isolation in PostgreSQL/Aurora, where a boundary failure is a reportable breach
- REST APIs specified in OpenAPI 3.0, versioned properly, because organisations integrate for years
- Standards and the team: code review, testing strategy, CI/CD, observability, audit logging and ADRs
The three hard problems
- Data-blind by design — personal data routed through the platform must not be readable by us, and that constrains every service, log line and debugging session
- Provable to a regulator — tamper-evidence is not “we have an audit table”; records must hold up when the reader assumes we are lying
- Withdrawal that actually propagates — reaching every connected organisation reliably, with a guarantee we can evidence
Minimum qualification
- 6+ years building and running production backend systems, with at least 2 in a lead or senior IC role
- Deep production strength in TypeScript/Node.js or Go, and comfort working in both
- Real PostgreSQL depth: data modelling, migrations, query performance, multi-tenant correctness
- Kafka or comparable event streaming in production — idempotency, ordering, replay, poison messages
- Microservices on AWS (we run ECS), with a working view on IaC, observability and cost
- Applied auth: OAuth2, JWT/JWE, mTLS — implemented, not just configured
- A high bar for testing and CI/CD, and the discipline to write a design down before building
Preferred
- DPDP, consent, privacy-tech or fintech domain experience
- ImmuDB or other append-only and verifiable data stores
- Multi-tenant SaaS at meaningful scale
- AWS 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 system-design session on a consent-ledger problem drawn from our actual constraints. No whiteboard algorithms
- 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
You'll thrive here if this sounds like you
You can make architectural calls with incomplete information — and write down why
You have never worked on consent or privacy infrastructure? Fine. Almost nobody has; the category is fifteen months old in India
You can reason about hard constraints rather than pattern-match to previous systems
You want to mentor a junior backend engineer and set the standard for engineers who follow
You are comfortable being early: eighteen people, pre-revenue, uneven hours around MVP, and some rebuilding
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.