Recruiting Operations Manager
- Salary
- ₹8–15 LPA
- Location
- New York, US
- Experience
- Senior
About company
About the role: As Recruiting Operations Manager , you'll own the systems, processes, data, and programs that power hiring at Hex. This is a builder role. You'll take a recruiting function that's growing fast and give it infrastructure that scales: clean data, sharp reporting, efficient workflows, and a hiring experience we're proud of. The goal isn't a process that merely holds up under load. It's a hiring system that gets measurably better every quarter, where automation handles the mechanical work so recruiters and hiring managers spend their time on judgment, relationships, and closing. You'll be the person who turns "we should really fix this" into a durable, adopted process. You'll report to the Head of Talent and work cross-functionally with Finance, People Operations, and Data. What you'll do: Architect the system Own the recruiting tech stack end to end: ATS, sourcing, scheduling, and assessment tools, including configuration, integrations, and vendor management. Design and continuously improve the hiring workflow from req approval and intake through sourcing, coordination, offer, and close, removing or automating manual steps wherever possible. Make the build-versus-buy calls, and the consolidate-versus-keep calls. Decide what earns a place in the stack. Own the data Build recruiting analytics leadership actually uses to make decisions: pipeline health, funnel conversion, time-to-fill, source effectiveness, and hiring forecasts. Establish and enforce data hygiene and reporting standards so the numbers can be trusted, including the unglamorous work of making sure signal gets captured on candidates we pass on, not just the ones we hire. Partner with Finance and People on headcount planning, req management, and the operational link between the hiring plan and what's actually in the pipeline. Ship AI and automation with architecture behind it Identify where AI genuinely improves the funnel, build it into the workflow deliberately, and define how we'll know whe