Thursday, January 3, 2013

Story of Naukri Job Alerts


Naukri.com is the market leader among with career sites in India, with market share currently at 63%. Naukri.com has 30 million+ registered profiles and a large part of these registered members receive a job alert every alternate day or on a weekly basis. Job alerts only contain freshly posted jobs on Naukri.com in last two/three days. It is probably the main reason why Naukri Job Alerts have one of the highest open and click through rates. Yet, jobseekers complained of relevance of jobs sent. That was identified as one of the important problems to address in early 2010.

The process of improving the job alerts was an incremental one. We built the logic step-by-step and with every incremental step, our understanding of the relevance problem improved.

1. Discovery of “Role” – I tend to believe one major variable than we discovered was “Role”. A deep dive in the behavioral data showed several interesting patterns. Jobseekers were not sticking to their Functional Areas (departments) and were applying across Functional Areas.

a. Pattern of apply clearly indicated that Role was more important than functional area.

b. We had roles which were very similar present in multiple Functional Areas, for example, sales role existed in Industry specific functional areas. GM Accounts existed in Accounts Functional Areas as well as the Top Management Functional Area. Also, several functional areas were close to each other, for example, Accounts and Banking.

2. Limitation of Keyword search – Key skills entered by jobseekers represents what they consider as important. Logically, a search on jobs should use the key skills entered by the jobseeker. However, some of the jobseekers had not entered their key skills. A large gap existed in the key skills entered and their skills as apparent from the CV. We needed a robust mechanism which did not fail because of the data inadequacy.

3. Handling of Categorical Variables – When we compare two jobs and their relevance to the jobseeker, attributes like “role” were important. The key challenge was to translate this into a distance function that can be used in predicting relevance for the jobseeker. Similarly, attributes like Industry, Location required identification of a good distance function.

4. Jobseeker Resume – A match between a jobseeker’s expertise and the requirements from the recruiter is essentially a match between the CV/resume and the Job Description. Of course, there are challenges – if a CV is old or a job description is incomplete, this may not work very well. Yet, we needed a mechanism for matching the candidate CV and the job description.

5. Apply Behavior - It is very much possible that apply behavior of a jobseeker will deviate from the CV/resume.  Apply behavior can provide insight into asiprations of the jobseekers as well as help identify classification errors. Incorporating apply behavior in identifying matching jobs for jobseekers is another significant challenge.

Naukri Analytics team identified the above challenges and incrementally solved them in association with the product team and the technology team. And of course, we noticed a major improvement in relevance feedback from jobseekers.

We are not done on solving this technical challenge. Analytics team is looking to hire smart Data Scientists to join its rank and work on solving these – if you are interested, please click to here to apply.

No comments:

Post a Comment