Job description to boolean string1/16/2024 Recruiters, while sourcing, need to run a variety of searches to get the best matches and not miss any top candidates.Ĭan a computer system efficiently do the job of searching and matching? I’ll write a review of matching systems in an upcoming post.There was a time when job seekers would scour through the classifieds and recruitment section in search of a job worthy of their talents and send in traditional job applications. Even in systems providing faceted resume search, allowing (for example) to search for job titles and years of experience, in addition to keywords and phrases, and offering advanced Boolean syntax, choosing search terms requires the recruiter to understand the industry terminology, as well as apply company- and job-specific knowledge. – This is additional helpful intelligence.Ĭonstructing productive searches that would find results matching the requirements, as you see, is not straightforward – it is an art. There can also be “preferences” input from Hiring Managers that is not present the job post. (except for new and unique job openings) “Similarity” to people who have been hired for this type of jobs at this company in the past, or perhaps got an offer but didn’t accept – for example, graduates from given schools, employees from a company’s competitor, or a company using the required technology, etc.Location, job title (with variations), skills (including synonyms, popular technologies, etc.), years of experience, education requirements, (possibly) certifications or licenses, etc.Recruiters who use databases with resumes or professional profiles may construct searches based on: Clearly, searching and matching in recruiting is more complicated than automatic keyword searching, even with the addition of synonyms. You see? The keyword sets in both cases are dramatically different between jobs and resumes. Resume, match #1 (the person works there):Ī filled out LinkedIn profile, match #2 (the person works there): Job 1 (Clinical Nurse) Resume, match #1 (the person works there): Resume, match #2 (the person works there): Let’s take a look and appreciate the how far apart these word clouds are: The reality is that keywords on job posts and resumes of those who get the jobs differ quite a bit!īelow, you will find the word clouds for two job ads, along with two resumes of people hired for each of the jobs. A junior recruiter (or poorly constructed system) can pull out only keyword-matching resumes as “the” ones worth reviewing – but this rarely works to solve the matching challenge. (As just one example: the job and resume “context” matters for matching in one case, a person with either Linux or Solaris, both being Unix variations, would be okay in another instance, it has to be Linux.)Ī naive assumption of some job hunters – and even systems that assist them (such as Resunate and Jobscan) – is that “resumes must contain the most prominent keywords from a job post” for a candidate to have a chance to be hired for the job. I think you would agree that finding a matching resume would rarely be productive if it is only done by crafting a Boolean string with long lists of keywords and synonyms separated by ORs, based on the job post. Let’s take a closer look at what “matching” means for a job description and a candidate’s resume. I’d like to share some observations on intelligent searching and matching and will go over some tools in a future post. At the end of last year, I became interested whether recently released tools in the “match” category can help to speed up searching, by offering “short-listed” candidates for review and contact. Intelligent searching and matching resumes against job descriptions is not an easy task, not for a recruiter and not for software.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |