In Paradigm Shift – Adding Context to Job Search I stated, “…instead of searching all jobs in our index for the words ‘computer network support’, we can search for all jobs classified within the five occupational categories deemed most appropriate for the search text.”
Of course, this only works if all of the jobs in our index have been tagged with appropriate occupational codes. Here’s an example:
A search for ‘computer network support’ jobs in Kansas City, MO, using Indeed, returned 219 results – the top organic result was for a ‘Sales Manager, Parts, Service, and Body Shop’ (click image at right for a larger view). In the snippet of text returned with the job title you can see that all of the search words (support, network, computer) are highlighted.
As bad as this result is, remember that I’ve rated Indeed as the best job board for active job search.
If Indeed used O*NET-SOC AutoCoder technology to tag the jobs in their index, a jobseeker searching for a ‘computer network support’ position would never see this job – let alone see it as the top rated organic result.
As discussed in the previous post, instead of searching all jobs for the three keywords (computer, network, and support), the search engine would look for jobs tagged with the occupations:
- Computer Support Specialists
- Network and Computer Systems Administrators
- Network Systems and Data Communications Analysts
- Computer Security Specialists
- Computer and Information Systems Managers
And the tags assigned to the top job in Indeed’s organic results? O*NET-SOC AutoCoder processes the title and full description of the job listing and assigns the following three tags:
- First-Line Supervisors/Managers of Retail Sales Workers
- First-Line Supervisors/Managers of Non-Retail Sales Workers
It’s pretty obvious that there is no overlap between the context of the jobseeker’s search for ‘computer network support’ and this job – and no reason at all that it should be number one out of 219 ‘matching’ jobs.
Comments