So you would want to include those in parentheses rather than just using the word Ruby. Right? So read articles that are written by developers about the stack, like intro documents, just so that you can get an understanding of different words that might be in the same framework, right? So Ruby, ROR, and Ruby on Rails, they all indicate slightly different things, but it’s the same language. You might know a high-level version of, and just like read articles that are written by- my example’s tax because I’m an ex sourcer. So as you’re delving into a search, it’s important to just take the terms that you might not know as well. People who maybe only talk about their work in one way. So a lot of people, they’ll scan the JD and they’ll just take key terms out of the JD and throw them into a search string, which is great, but you’re going to get Can you maybe describe natural language searches for people that aren’t super familiar with that term? Sure. So we do this really to become more familiar with the language that’s used to describe particular skillsets, which is known as natural language. Moving on, as recruiters and sourcers we know it’s important to do research on roles that we might be unfamiliar with before we start our search. So what I always recommend is when you’re building out these search strings, play around with them, add different words, try out different stop words to see if it’s actually registering or not, and don’t commit to one Boolean string too quickly. And a lot of people like myself here include their pronouns in their profiles now, but you can’t actually search using them depending on what you’re doing. The closest steak and shake?” Google’s going to skip over the “where” “it” “is” and “the” and it’s just going to look for steak and shake, right? So some examples that are ignored by various search engines, are “she” “her” “they” “them” and then “go”, which I included because that’s the language for Golang.Ī lot of examples of diversity sourcing for gender have talked about including pronouns, which are important. I’d always heard of stop words, so it’s just words that when you’re typing into Google you say, “Where is it So I actually recently learned this at source con. So it’s important to note that when you’re working with Boolean strings, that a lot of Boolean strings are based off of old programming language. So by using Boolean strings, you can refine your search in order to find the candidates you’re looking for depending on your needs. Whereas if you did X-Men or Avengers, you would get everybody who’s in this current circle. So and then X men, just X men, not Avengers you would get Gambit, Professor X and Nightcrawler. Right? If you were looking for X-Men who hadn’t been Avengers, you’d be looking for professor X, Gambit, Nightcrawler. So using my X-Men and Avengers example here, if you were looking for somebody who was an X-Men and an Avenger, you would find Rogue, Beast, and Storm because they both have been on both schemes. So with Boolean strings you use “and” “or” and “not” as ways to search different candidates. For those that may be unfamiliar, what are Boolean strings? So Boolean strings are a concept we learn about in math, combining different words and phrases together in order to create more robust searches. So Robyn, let’s start things off with the basics. So today we want to dig into things a little bit more and talk a bit about the technical aspects of sourcing and focus really on Boolean strings. In our first episode, we explored how to get started when searching for diversity and we covered topics such as defining diversity, avoiding tokenism, and creating inclusive environments. Welcome to the second episode of sourcing for diversity, expanding Boolean search strings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |