Hamara Jobs × ONDC

Anchor partner · India's first federated jobs network

Led Hamara into ONDC's Jobs domain as anchor partner of India's first federated, interoperable jobs network.

01 — Project context

What exists today, and how this does it better.

FIG. 04

Overview

ONDC set out to do for commerce what UPI did for payments — an open, interoperable network. I led the team that took Hamara Jobs into its Work Opportunities domain, and helped shape the domain itself.

The aim was never a bigger slice of the pie. It was a bigger pie.

01 — On the network

Re-platform, then go live

We collaborated with ONDC and ONEST on upgrading the protocol, then migrated Hamara Jobs off its PHP monolith to JavaScript and microservices — and went live on the network as a job provider. The seeker app was later rebuilt as a PWA and made ONDC-compliant.

02 — Anchor partner

An SDK so anyone could join

To help the ecosystem grow, I proposed an integration SDK so any participant could join the network without re-implementing the protocol from scratch. On the strength of the work, Quess was listed as the Anchor partner for the Work Opportunities domain.

03 — Into government

e-Nijukti, with Odisha

I took the network's relevance to the Odisha state government and led the engagement for the e-Nijukti portal — a successful ONDC SDK pilot that put an open jobs network in front of a state's job seekers.

04 — The vision

UPI, but for jobs

The bigger idea I've been drafting: a unified jobs interface, analogous to UPI — one rail every seeker and provider can plug into, instead of a hundred walled portals. More to come.

What UPI did for payments, an open network can do for jobs.

My role

Led the team that took Hamara Jobs onto ONDC, the protocol work, the re-platforming, and the SDK proposal, and the engagements that followed, from Quess's anchor-partner role to Odisha's e-Nijukti pilot.

Outcome

Content coming soon.

Stack

ONDC / Beckn
Microservices
PWA
SDK
Interoperable APIs