Broken LinkedIn Boolean Explained and Webinar

booleanstrings Boolean 2 Comments

 

I have figured out how it works and will briefly explain below.

We have announced a new delivery of the LinkedHacks webinar, live on May 1st, to fully update you. (Don’t miss it; seating is limited). Come to learn how to not only work with Premium and Basic accounts but take advantage of a new hidden feature!

Of course, nobody would search like this in practice; the search should produce zero results if we had working Boolean search. However, these results shed some light on what is going on. Let me explain.

If you search for senior software engineer (without the NOT additions; try it), LI would include:
a) synonyms and variations for “senior” such as “sr” and “snr”, “software” such as “sw”, “engineer” such as “engineering”
b) translations into other languages, such as “Ingeniero” etc.
It would look in all titles present – and past as well.

You need not write (senior OR sr OR snr) (etc.) – synonyms are included automatically.

With the awareness that the search is not Boolean, you can take advantage of the current implementation: keyword search for a job title returns all the members for whom this is a present or a past title. This search is otherwise unavailable in LinkedIn.com.

Meanwhile, LinkedIn Recruiter has its own, different ways to include job title synonyms.

We have observed lots of changes in LinkedIn search in the last few weeks. Come to LinkedHacks webinar (May 1st, optional hands-on practice May 2nd) to get full explanations, new and updated hacks (some, unavailable anywhere online), and get support on everything LinkedIn Sourcing for thirty days.

Update on LinkedIn People Search

booleanstrings Boolean 1 Comment

What happened?

As of two days ago, search operators (that I have covered in previous posts) have stopped working on LinkedIn. This includes not only undocumented operators like headline: but also the officially documented operators firstname:, lastname:, title:, company:, and school:. (They were introduced in 2017). It’s quite unfortunate! [Edited April 22, 2019: LinkedIn has taken down that help page.]

As always, we will be looking into alternative ways for Recruiters and Sourcers to overcome LinkedIn limitations.

We may get the operators back; we’ll see.

In the meantime, if you are searching with a basic or premium account, keep in mind that:

  1. LinkedIn Keywords Boolean Search Is Compromised. For better results, use the advanced search dialog.
  2. You can X-Ray LinkedIn for current company and job title. The advantage is, you would be looking for the “true” current job and avoiding finding jobs that members have not “closed”.
  3. If you are up for writing complex Custom Search Engine (little-known) special operators, you can use the technique described in Fascinating: Custom Headline Search. While LinkedIn search operators are not working, this is the only way to search by headlines (unavailable in any LinkedIn accounts, including Recruiter.)
  4. If you are not up for writing complex CSE search operators, use our Sourcing Tool Social List, which used the CSE technology via APIs and hides all the complexity for end-users. (We have also added a “Contact Finder” to the tool. Check out Dean Da Costa’s blog and video).

Thanks for reading! I’ll keep you updated.

Google Introduces before: and after:

booleanstrings Boolean Leave a Comment

 

Google has just introduced two new search operators – before: and after:

Here is what @searchliaison tells us:

The before: & after: commands return documents before & after a date. You must provide year-month-day dates or only a year. You can combine both. For example: [avengers endgame before:2019] [avengers endgame after:2019-04-01] [avengers endgame after:2019-03-01 before:2019-03-05].

If you provide only a year, before: & after: translates those into full dates that work, such as follows: [before:2018] = [before:2018-01-01] [after:2018] = [after:2018-12-31].

You can use either dashes or slashes in dates. Both of these are valid: 2018-12-31 2018/12/31.

(At the same time, Google took away sorting by date, except in the News, claiming that few users have taken advantage of it over the years.)

Example search: after:2019-1-1 site:linkedin.com/in OR site:linkedin.com/pub -pub.dir javascript engineer seattle

It’s a matter of taste, but I like the new operators better than the date range selection that has been available under “Tools” since 2009.

The new operators are described as working in the general and news search; however, it looks like we can use them in Image and other special searches too.

Keep in mind that Google makes its best guess on a page’s date based on several considerations. For many pages “out there”, it is not able to identify the dates, and those pages won’t show up in the date range-restricted results.

For a large-volume collection of Google search tips and support from our training staff, check out the Advanced Workshop recording.

Three Diversity Custom Searches

booleanstrings Boolean 2 Comments

It is possible, for some membership sites, to create Custom Search Engines that would search for female members only – and do so precisely.

Let me share some Diversity Custom Search Engines with you. (I’ll add some nerdy explanations of how it works, for those interested, at the end of the post).

Here you go.

CSE #1. Searching in Healthcare? Try Doximity Female Search. Add terms for locations and job titles. The search results are guaranteed to include female doctors only. Example search: child neurology houston texas.

CSE #2. Looking for Researchers? Try ResearchGate Female Search. Add your keywords. Example: “machine learning” “artificial intelligence”. The results are guaranteed to be females only.

CSE #3. Interested in female Speakers? Try SpeakerHub Female Search. Example search: recruiting OR sourcing. You will be finding females only.

Of course, this search is free, and we are not even likely to see “the captchas”.

Coming up – don’t miss the webinar! – “Sourcing for Diversity” – April 10 at 9 am PDT (recording and follow-up support are provided) where we’ll be sharing lots of creative and doable approaches in addition to these.
Read the details and register at https://sourcingcertification.com/diversitysourcing/. Seating is limited.

Now, the nerdy part, if you are into that kind of thing. (You don’t need this to use the CSEs). The above Custom Search Engines each X-Ray their appropriate site, plus, automatically add this substring to the search:  more:p:metatags-profile_gender:female. I wrote more about this technique in a past post.

LinkedIn Keywords Boolean Search Is Compromised

booleanstrings Boolean 10 Comments

Some of us, when starting a new search, go to LinkedIn, type a few terms – including, perhaps, a title and some skills – into the Keywords field in people search and try to assess the volume of potential candidates. However, if you do so, your answers may be flawed.

The LinkedIn Boolean Search Help article tells us, “If your search has two or more terms, you’ll automatically see results that include all of them.” However, this is not true in an exceeding number of keyword searches. You need to be aware of that, not to miss matching search results.

Here is what happens. If your keywords contain terms sounding like:

  • First and Last Names
  • Company Names
  • Job Titles (especially, titles with two or more words, following each other in the Keywords field, e.g. Java Developer)

Then – you will not “automatically see results that include all of the terms”. Instead, one or both of these things happen:

#1. Your search is automatically restricted to the respective profile fields – Name, Company, or Title.

For example, a search for James Smith misses some profiles that have both words, James AND Smith. (I have narrowed down the example search by a few parameters, to make the differences obvious).

#2. Your search is expanded to “synonyms”. For example, a search for “James” may find people called “Jim” or “Jamie”.

This sort of interpretation of first and last names has been there for a long time (and perhaps makes sense). What we are increasingly seeing at this time is Job Title-sounding words interpretation, that affects search results.

Here is what, for example, a (narrowed-down) search for Java Developer looks like*

– that does not include many profiles that have both keywords Java AND Developer:

* Note that your account may get different results from these searches.

When we search for the keywords Java Developer:

#1 – LinkedIn looks for people with the current or past (!) job titles including the words Java and Developer

#2 – LinkedIn includes some people with similar past or present job titles – for example, Java Engineer.

That’s it – LinkedIn will not include, for example, someone who is a Developer and has a skill Java unless they match #1 or #2 above.

The automatic interpretation of the search terms is not expected and not helpful. It’s best to avoid it.

You do not have to necessarily use “ANDs” to “break your way” to true Boolean search. Simply changing the keyword order in such a way that the terms don’t convey a job title – Developer Java – would “fix” the search:

 

This sort of job title-sounding search terms interpretation is inconsistent across accounts (no matter, basic or business). Different accounts get different numbers of results on the same job-title-like-sounding searches that vary quite significantly.

To avoid being misled:

  1. Watch for Job Title-sounding word combinations in your Keywords and avoid them.
  2. Use common sense – does the number of results make sense to you or is it too small or too large?
  3. Change the keyword order, rerun the search and compare.
  4. Use the advanced people search dialog and search operators.
  5. Come to our brand-new webinar LinkedHacks for Sourcing on Wednesday, March 27th.
    We will explain how to avoid search pitfalls – and how to make your Basic or Business account quite comparable in power with LinkedIn Recruiter by using workarounds, undocumented operators, URL modifications, and messaging alternatives.
    If you work with a Basic or Business account, I strongly recommend attending!

Four Major LinkedIn Sourcing Hacks

booleanstrings Boolean 7 Comments

Here are some LinkedIn Sourcing News.

  1. In case you haven’t noticed: LinkedIn has quietly introduced a “People” tab to its Company pages, like this one: https://www.linkedin.com/company/hewlett-packard-enterprise/people. (It is similar to the Alumni pages). We can search by location, school, the field of study, job function, skills, and connection level. It’s quite useful, especially if you are looking at some stats.
  2. The linkedin.com/company/*/people pages do accept LinkedIn search operators! Example.
  3. So do the Alumni search pages. Example.
  4. I have discovered another undocumented LinkedIn search operator, in addition to thesefieldsofstudy:The operator takes one or more Field of Study codes as an argument, for example, fieldsofstudy:100892;“100189” is the code for the Computer Science major. You can find other codes to use in a search by playing with a company “people” dialog like https://www.linkedin.com/company/hewlett-packard-enterprise/people/?facetFieldOfStudy=100189.

Happy Sourcing!

 

 

 

 

 

 

Ten Custom Search Engines for Recruiters

booleanstrings Boolean 2 Comments

Google Custom Search Engines (CSEs) is a powerful Sourcing tool, that can improve your Sourcing process with new results, often faster than “regular” Google.

CSE users fall roughly into three categories:

  1. End-user. If writing out search operators is not your cup of tea, you can use CSEs built by your more technical peers, without even learning advanced operators.
  2. Creator. Creating CSEs is not rocket science! Creating CSEs for your own and your peers’ use has numerous advantages. You can create CSEs that would “hide” Boolean operators, such as site:, from the end user (saving time on retyping), search within a list of sites, and, importantly, use CSE search options unavailable in “regular” Google. For example, you can set a CSE to “search the entire web but emphasize included sites” – it is like “Soft” X-Ray.
  3. Master. Unknowingly to many, CSEs have additional search operators compared to “regular” Google. These operators allow finding not just web pages with the keyword occurrences but pages where a particular term is in a person’s company or job title, for example. Learning how to identify and use the special operators takes a bit of a learning curve, but it is well worth it.

Let me share with you some Custom Search Engines for Sourcing that I have created.

  1. Diversity Associations
  2. Hidden Resumes
  3. LinkedIn X-Ray
  4. LinkedIn – Countries
  5. LinkedIn – Contact Info
  6. XING X-Ray
  7. Github Profiles
  8. Search for Teachers
  9. Documents – Formats
  10. Google Storage

Enjoy!

We will be delivering a Custom Search Engines Webinar >>> Become A Custom Search Engines Expert. Don’t miss it!

LinkedIn Recruiter Doesn’t Do What You Think It Does

booleanstrings Boolean Leave a Comment

LinkedIn has not failed to create UI/UX that doesn’t do what we expect it to do. It’s been a Sourcer’s delight to figure out the “ins” of LinkedIn and, in particular, LinkedIn Recruiter (which I extensively use for sourcing) over the years. To add to the confusion, LinkedIn often makes “helpful” adjustments to its software, and what it exactly does keeps shifting. LinkedIn Recruiter (LIR) is especially misleading in its hidden “helpful” semantic interpretations of our searches (none of that stuff is documented). There have always been bugs, too – worse than we can expect from a corporation that has the resources they do.

So many Recruiters rely on the expensive product for Sourcing, while missing matching results and getting non-matching results due to the way it works.

While LinkedIn seems to care about the UX, they seem to do the wrong thing a lot of the time. Here are just some unhelpful things LIR users experience:

Free and Business LinkedIn users have features that LIR doesn’t – LinkedIn Operators: One More and a Tip Sheet.

Are you a LinkedIn Recruiter user? Check out the online class “Mastering LinkedIn Recruiter” coming up on Wednesday, February 13th. (If you miss it, we will have a recording available at the same link).

If you are confused with your search results in Recruiter, it’s not you, it’s them! Let us show you ‘what’ it does while searching (not what you think it does!) and how to search “right”. LinkedIn’s documentation doesn’t talk about this, and customer support, unfortunately, is unaware of these search behaviors. (Sometimes we wonder if anyone at LinkedIn is aware of what we are discovering!) Seating is limited.

Our webinars include the materials and video-recording for you to keep and one month of support on the topic (an excellent value by itself; I don’t think anyone else provides that).

Four “Lazy Operators” for Lazy Sourcers

booleanstrings Boolean Leave a Comment

If you source well, that implies that you are also a Lazy Sourcer. What I mean by a Sourcer’s “Laziness” is trying to get results with fewer keystrokes and mouse movements. (Those of us who type slowly – I do! – need to find ways to reduce typing even more desperately). I am a Lazy Sourcer – and am always on the lookout to do things faster.

I won’t be covering various info-fetching Chrome extensions in this post. Good people like Dean DaCosta and Jan Tegze have posted plenty of information about them. Rather, I will talk about ways to type less when searching – specifically when considering using most common advanced Google search operators.

(To mention, I am not a fan of “Boolean Builders.” I always type searches “by hand”; I recommend you do, too! Humans do better than machines in generating searches as of February 2019.)

Here are some tips I want to share. (They are simple.) I will call them Lazy Search Operators.

  1. Lazy site: (X-Ray)

Google has become very intelligent. We can often search for a site (or company) name without writing out a site: operator (X-Raying) and still find the information we are looking for on that site.

For example, searching for <first> <last> linkedin (example search) or, for more common names, <first> <last> <company> linkedin, will find LinkedIn profile(s) in question. We can write other types of searches (if the search terms are “reasonably unique”) along with the word linkedin and quickly land on the right results.

Similarly, we can search for <any site’s name> <keywords> instead of X-Raying that site. Example.

(Makes sense, Sourcers?)

  1. Lazy filetype:

You guessed it. We can often search just for the file type and drop the operator filetype:. We do need to put the file type in the quotation marks, e.g., “XLSX” (though there are two extra characters to be entered!). Example.

  1. Lazy intitle: and inurl:

Remember that Google will rank results higher if it finds our keywords in titles and URLs, even if we don’t use these operators. For example, searching for resume along with some keywords will often work just as well as the popular template intitle:resume OR inurl:resume.

  1. Lazy define

In many cases, just naming the entity and dropping the operator define will produce a definition in a “Featured Snippet,” which we see above the search results. Example. (You can also search for what is <term>).

Additional Tip:

Try using fewer, if any, quotation marks in these searches: you may get better results – and you will type less as well!

Note that these “relaxed” searches have started working much better in our experience in recent years, as Google has been enhancing its search algorithms.

(As a reminder, use these best practices while you are searching).

So, you would ask, do we no longer even need to teach new Sourcers Google’s advanced operators? We absolutely do! There are numerous cases where advanced operators give us searching superpowers. (I might just need to take a touch-typing class to speed up those. 😉)