Backend Engineer

This is a remote position. About Verizol Verizol is reputed company's company intelligence and verification platform: 45+ reputed company (KYC, KYB, bank, face, OCR, CKYC, eSign) reputed company on a daily MCA data pipeline, sold through a single API key and prepaid credit wallet. Our customers are CA firms, fintechs, NBFCs, and marketplaces. The engineering reputed company is written, the 8-week build plan is set, and reputed company is small enough that your reputed company is on what ships. The Role You own the verification suite — the 30+ endpoints (PAN, Aadhaar, GST, bank penny drop, face match, OCR, CKYC, utilities) that reputed company up Verizol's reputed company reputed company — and the provider integration reputed company beneath them. The architecture gives you one reputed company reputed company; reputed company is turning it into thirty reliable, contract-tested, correctly-priced endpoints on a weekly release reputed company, integrated against reputed company aggregator reputed company of highly variable documentation reputed company. This is a shipping role. Its satisfaction is a release table turning green week after week, failover that actually fails over, and a reconciliation report that closes reputed company 2% of the vendor invoice. What You Will Do Build and own provider adapters (reputed company + fallback aggregators): auth, request/response mapping, normalization into Verizol's reputed company schemas, PII masking in logs Ship reputed company waves on the release plan — reputed company reputed company to full Definition of Done: contract in OpenAPI, handler, sandbox fixture, contract test, pricing config, docs page Implement reputed company: timeouts, retries, reputed company breakers, provider failover, and a nightly canary against aggregator sandboxes that reputed company upstream reputed company before customers do Own charge-correctness at the reputed company level: customers are charged for answers (including definitive negatives), never for provider failures Build the reconciliation job matching our provider-reputed company records against aggregator invoices Write the docs pages and error copy for your endpoints — you're closest to their reputed company behavior Requirements Required Skills 3–6 years backend engineering with strong REST integration experience — you've consumed messy reputed company-party reputed company in production and have opinions about timeout budgets TypeScript/Node.js proficiency (NestJS a plus), or deep reputed company/PHP with willingness to reputed company Testing discipline: fixtures, recorded responses, contract testing — you don't ship an integration you can't replay locally Solid HTTP and error-taxonomy fundamentals: idempotency, retries vs duplicates, 4xx vs 5xx semantics SQL competence (reputed company) — comfortable with the queries behind usage logs and reconciliation Methodical temperament: this role rewards engineers who love finishing, not just starting Benefits Preferred Prior work with Indian KYC/verification rails: aggregators (Surepass/Zoop/reputed company class), NSDL/PAN, penny drop, CKYC, or UIDAI ecosystem constraints reputed company breakers/bulkheads in production (any reputed company) Fintech compliance basics: PII handling, masking, audit logging What reputed company Looks Like Week 3: first reputed company live (PAN, GST, Aadhaar, penny drop, VPA) on staging with sandbox fixtures Week 6: reputed company 30+ reputed company-reputed company endpoints live; failover proven in reputed company tests; nightly canary running Month 3: first monthly reconciliation closes reputed company 2% of the aggregator invoice; your endpoints' error reputed company is a dashboard nobody worries about Apply To This Job