freehire launches on Product Hunt on 26 August.

Follow →

Backend Engineer

Open 17d

Summary

Build and maintain a suite of 30+ verification endpoints (PAN, Aadhaar, GST, bank penny drop, etc.) for a KYC/KYB platform, integrating with external aggregators and ensuring reliability, contract testing, and charge accuracy.

This is a remote position.

About Verizol

Verizol is ZipNom's company intelligence and verification platform: 45+ APIs (KYC, KYB, bank, face, OCR, CKYC, eSign) built 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 blueprint is written, the 8-week build plan is set, and the team is small enough that your name 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 make up Verizol's rate card — and the provider integration layer beneath them. The architecture gives you one adapter pattern; your job is turning it into thirty reliable, contract-tested, correctly-priced endpoints on a weekly release cadence, integrated against external aggregator APIs of highly variable documentation quality.

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 within 2% of the vendor invoice.

What You Will Do

  • Build and own provider adapters (primary + fallback aggregators): auth, request/response mapping, normalization into Verizol's canonical schemas, PII masking in logs
  • Ship endpoint waves on the release plan — each endpoint to full Definition of Done: contract in OpenAPI, handler, sandbox fixture, contract test, pricing config, docs page
  • Implement resilience: timeouts, retries, circuit breakers, provider failover, and a nightly canary against aggregator sandboxes that catches upstream drift before customers do
  • Own charge-correctness at the endpoint level: customers are charged for answers (including definitive negatives), never for provider failures
  • Build the reconciliation job matching our provider-call records against aggregator invoices
  • Write the docs pages and error copy for your endpoints — you're closest to their real behavior


Requirements

Required Skills

  • 3–6 years backend engineering with strong REST integration experience — you've consumed messy third-party APIs in production and have opinions about timeout budgets
  • TypeScript/Node.js proficiency (NestJS a plus), or deep Laravel/PHP with willingness to switch
  • 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 (Postgres) — 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/Signzy class), NSDL/PAN, penny drop, CKYC, or UIDAI ecosystem constraints
  • Circuit breakers/bulkheads in production (any framework)
  • Fintech compliance basics: PII handling, masking, audit logging

What Success Looks Like

  • Week 3: first wave live (PAN, GST, Aadhaar, penny drop, VPA) on staging with sandbox fixtures
  • Week 6: all 30+ rate-card endpoints live; failover proven in chaos tests; nightly canary running
  • Month 3: first monthly reconciliation closes within 2% of the aggregator invoice; your endpoints' error rate is a dashboard nobody worries about


See also

Tailor your CV for this role?

We couldn't check your fit for this role — add a CV to your profile to see it next time.

A new version of freehire is available