What was one interesting search string or web sourcing trick you have learned in the past week?

[Irina Shamaeva]

In the spirit of sharing, I'd like to invite all new members to post a suggestion here.

Here is mine: I have discovered that the filetype: operator on Google not only looks for files of certain types such as DOC, PDF etc. but would simply look for any given "ending" of a URL. As an example you can search for filetype:uk to look for pages ending in .uk.

[Amit Kumar]

Sounds great Irina.

I've another good & effective search shortcut for Google which yields good results in the form of resume's.

For ex; (intitle:resume | inurl:resume) -Guide -Post -Writing -Create -Distribution Java developer

This search will result in all Java developer resume's. If we put;

(intitle:resume | inurl:resume) -Guide -Post -Writing -Create -Distribution Java developer, DC

This search will result in all Java developer resume's for the DC region.....

[Wayne Howell]

I have been trying to get my arms around this concept however when ever I go and take another stab at it it seems I get alot of garbage. What do I mean as garbage I just ran as suggested this string

(intitle:resume | inurl:resume) -Guide -Post -Writing -Create -Distribution Java developer

And it give me 35,000 pages and most are over 2 years old... What am I missing. Would it be easier to use job boards and even if I select the all date range and start from the end moving forward.

Just a guy from the old school

[Moises Lopez]

Hi Wayne,

The query that you tried is ((intitle:resume | inurl:resume) -Guide -Post -Writing -Create -Distribution Java developer) was written specifically for google. It would not work well in other search engines. So I will assume you tried it in google. The keywords terms "guide, create, writing, post, distribution" are terms that are selected to screen out resume sites and at that is effective but it is my thought that you can zero in better by a better use of keywords. Also by using the intitle or the inurl commands you are unnecessarily narrowing your results without first knowing what the keywords will bring.

From the inital search string I deduce that we are searching for java developer. I would write my query differently, perhaps even simpler. I would focus on keywords that maybe indicate skills that only a java developer would use such as "soap or beans". Also the term "DC" I am assuming is to indicate a preference for the Washington, DC area, you might be better served by using zip codes like 20001, 20002, 20003.

By now the search string would look like - resume java beans (20001 OR 20002 OR 20003) and in google that would return in the neighborhood of 3,120 results. if you wanted to narrow further by date you can go to the advance search and select the different date narrowing options.

I hope this helps