
Scaling Job Postings via Platform Intelligence
Reducing manual operations through AI-assisted workflows
InfoEdge Hackathon (48 hours)
AI-Assisted Workflows
Context
Increasing job postings from recruiters with active subscriptions was a core business OKR for NaukriGulf, directly tied to active database growth and renewal likelihood.
Despite multiple initiatives, a significant portion of job recovery still depended on manual client servicing workflowsβcreating a bottleneck that limited progress against this goal.
My role was to identify structural inefficiencies in this process, reframe the problem beyond operational execution, and explore whether a system-level approach could unlock scale.
Constraints & Operating Reality
The problem existed under several non-negotiable constraints:
π³
Recruiters were cautious about consuming paid credits
π₯
Client servicing bandwidth was limited and already stretched
π
Hiring intent existed outside the platform, but detection was slow and manual
Any viable solution had to:
βοΈ
Reduce human dependency
βοΈ
Preserve recruiter trust and control
βοΈ
Integrate into existing workflows rather than replace them
Ground Truth
To understand the problem beyond metrics, I reviewed the client servicing workflow directly.
Observed Reality
π΅οΈ
Career sites and LinkedIn were monitored manually
π
Jobs found externally were mapped back to NaukriGulf to avoid duplication
π§
Recovery required multiple emails / scripted persuasion / free job credits
Despite this effort
β
90% recruiter declined
β
Approval authority was often unclear
β³οΈ
Time to convert stretched into weeks
Core Insights
The constraint was not demand.
Recruiter intent, candidate supply, and historical behavior already existed β but the system relied on humans to connect these signals.
This reframed the problem from sales execution to platform intelligence.
Strategic Decisions
π€
Shift ownership from humans to the platform
Rationale: Manual pattern recognition does not scale and delays response to hiring intent
Trade-off: Accept partial coverage in exchange for higher confidence and speed
βοΈ
Validate value before
prompting action
Rationale: Recruiter trust erodes when nudges are not backed by supply confidence
Trade-off: Fewer prompts, but significantly higher relevance
π₯
Treat client servicing as a primary user
Rationale: Any solution that increased their cognitive or operational load would fail
Trade-off: Reduced configurability in favor of operational simplicity
System Design Response
We designed a multi-agent AI system, where each agent addressed a specific failure point in the existing process.
π
Job Discovery Agent
Detects jobs posted on career sites and competitor platforms that are missing on NaukriGulf.
π§
Client Insight Agent
Analyzes recruiter history to infer posting preference, credit availability, and likelihood of action.
π‘οΈ
Supply Validation Agent
Confirms candidate availability to avoid low-value recommendations.
π€
Decision & Pitching Agent
Synthesizes insights to decide:
βοΈ
Whether to prompt at all
βοΈ
What action to recommend
βοΈ
Why the recommendation is relevant

Reflection
This work reinforced a consistent pattern in my approach:
Scalable impact comes from re-architecting how intent, insight, and action connect β not from adding features.
Impact
For recruiters, this meant:
βοΈ
Reduce job detection latency from weeks to hours
βοΈ
Increase utilization of existing paid credits
βοΈ
Lower dependence on manual client servicing effort
βοΈ
Improve likelihood of recruiter reactivation and renewal

Scaling Job Postings via Platform Intelligence
Reducing manual operations through AI-assisted workflows
InfoEdge Hackathon (48 hours)
AI-Assisted Workflows
Context
Increasing job postings from recruiters with active subscriptions was a core business OKR for NaukriGulf, directly tied to active database growth and renewal likelihood.
Despite multiple initiatives, a significant portion of job recovery still depended on manual client servicing workflowsβcreating a bottleneck that limited progress against this goal.
My role was to identify structural inefficiencies in this process, reframe the problem beyond operational execution, and explore whether a system-level approach could unlock scale.
Constraints & Operating Reality
The problem existed under several non-negotiable constraints:
π³
Recruiters were cautious about consuming paid credits
Client servicing bandwidth was limited and already stretched
π₯
π
Hiring intent existed outside the platform, but detection was slow and manual
Any viable solution had to:
βοΈ
Reduce human dependency
βοΈ
Preserve recruiter trust and control
βοΈ
Integrate into existing workflows rather than replace them
Ground Truth
To understand the problem beyond metrics, I reviewed the client servicing workflow directly.
Observed Reality
π΅οΈ
Career sites and LinkedIn were monitored manually
π
Jobs found externally were mapped back to NaukriGulf to avoid duplication
π§
Recovery required multiple emails / scripted persuasion / free job credits
Despite this effort
β
90% recruiter declined
β
Approval authority was often unclear
β³οΈ
Time to convert stretched into weeks
Core Insights
The constraint was not demand.
Recruiter intent, candidate supply, and historical behavior already existed β but the system relied on humans to connect these signals.
This reframed the problem from sales execution to platform intelligence.
Strategic
Decisions
π€
Shift ownership from humans to the platform
Rationale: Manual pattern recognition does not scale and delays response to hiring intent
Trade-off: Accept partial coverage in exchange for higher confidence and speed
βοΈ
Validate value before
prompting action
Rationale: Recruiter trust erodes when nudges are not backed by supply confidence
Trade-off: Fewer prompts, but significantly higher relevance
π₯
Treat client servicing as a primary user
Rationale: Any solution that increased their cognitive or operational load would fail
Trade-off: Reduced configurability in favor of operational simplicity
System Design Response
We designed a multi-agent AI system, where each agent addressed a specific failure point in the existing process.
π
Job Discovery Agent
Detects jobs posted on career sites and competitor platforms that are missing on NaukriGulf.
π§
Client Insight Agent
Analyzes recruiter history to infer posting preference, credit availability, and likelihood of action.
π‘οΈ
Supply Validation Agent
Confirms candidate availability to avoid low-value recommendations.
π€
Decision & Pitching Agent
Synthesizes insights to decide:
βοΈ
Whether to prompt at all
βοΈ
What action to recommend
βοΈ
Why the recommendation is relevant

Experience Principles
The experience was deliberately designed around four principles:
βοΈ
Explainability over automation
Recruiters understand why an action is recommended.
βοΈ
Control over enforcement
The system recommends; the recruiter decides.
βοΈ
Low friction, not zero friction
Actions are simplified but never forced.
βοΈ
In-flow delivery
Recommendations surface within existing recruiter workflows and outreach channels without altering operating models.
Impact
Although developed as a concept, the system demonstrated potential to:
βοΈ
Reduce job detection latency from weeks to hours
βοΈ
Increase utilization of existing paid credits
βοΈ
Lower dependence on manual client servicing effort
βοΈ
Improve likelihood of recruiter reactivation and renewal
Reflection
This work reinforced a consistent pattern in my approach:
Scalable impact comes from
re-architecting how intent, insight, and action connect β not from adding features.
