π Welcome to the simplified guide to using operators in GigRadar's search field!
By understanding and correctly using our search operators, you can streamline your lead generation process on Upwork, pinpointing the most relevant jobs quickly and efficiently.
1. Asterisk as a Wildcard:
*οΈβ£ When you use an asterisk (*) with a keyword, it looks for all its variations.
π‘ Example:
(desig*)
This will find: desigN, desigNER, desigNING, and so on.
β οΈ Any keyword that includes an asterisk (*) in the main field (as on the screenshot), should be enclosed in brackets. This is crucial for our search system to correctly identify and process your wildcard entries.
β
β οΈ The asterisk wildcard (*) only works to find suffixes in our search system. So, please place it at the end of your keywords, not at the beginning.
2. The 'OR' Function:
βοΈ Using "|" between two keywords means either keyword can be present in the search result.
π‘ Example:
design | figma
This will fetch jobs that mention either "design" OR "figma."
3. The 'AND' Function:
A space between two keywords ensures both are present in the search result, but not necessarily in the order mentioned.
ππ» These keywords can be found anywhere in the job post, title, or skill list, not necessarily adjacent to each other.
π‘ Example:
design brochure
This looks for jobs where both "design" AND "brochure" are mentioned, regardless of their position or order.
πββοΈ For instance, a job posting saying "Help me design a unique layout. There's a brochure for reference." would still be a match.
4. Using Brackets for Priority:
π« Brackets are used to create groups of keywords and prioritize the search. This enables our search to focus on finding specific combinations.
π‘ Example:
design (brochure | "business card")
This query seeks jobs that contain the word "design" in combination with either "brochure" or "business card".
πββοΈ For instance, a job posting saying "We need a design for our new product brochure" OR "We are looking for a creative design for our business card" would match this query.
5. Exact Phrasing:
ποΈ Quotes ("") are used to search for an exact phrase. The search will look for the precise sequence of words within the quotes.
Keywords or phrases containing more than one word should be surrounded by quotation marks. This rule applies to phrases like "web development", "React Native", or even terms like "node.js" where a punctuation is involved.
Important: Use regular double quotation marks (").
β
If you copy and paste from a document, ensure the quotation marks haven't changed to a different style, as this can disrupt the search function.
β
βNOT:
'
Β«
`
β
π‘ Example:
"React Native Expert"
β This query will only fetch jobs that contain the exact phrase "React Native Expert".
π¬ For example, a job posting that says "We are hiring a React Native Expert to join our team" would be a match.
β
However, a posting stating "We are seeking an Expert in React Native development" would not be a match because the words are not in the exact order as specified in the quotes.
6. Complex Queries:
π By combining multiple techniques, you can create comprehensive queries that encompass various criteria.
π‘ Example:
((design*) | (redesign*)) ((web*) | (app*) | platform | saas | MVP)
This query forms many search queries simultaneously, for example:
(design*) = design | (design*) = designing | (design*) = designed |
|
|
|
(redesign*) = redesign | (redesign*) = redesigning | (redesign*) = redesigned |
|
|
|
π‘To ensure our database accurately processes complex search queries, they must be properly written.
For example, when using a search query like "Ruby-on-Rails)"
, special characters should be escaped with a backslash to maintain query integrity. This means the query should be written as "Ruby\-on\-Rails)"
. A complete query might include variations such as "ruby)" | "rubyonrails)" | "Ruby on Rails)" | "Ruby\-on\-Rails)"
.
Similarly, for search queries like "(laravel"
or "(laravel)"
, our system may not handle them correctly, leading to inconsistent results. To correct this, escape the terms with a backslash, like this: "\(laravel"
and "\(laravel\)"
.
ππ» Mastering these search operators and techniques is a crucial part of leveraging GigRadar platform to its fullest potential and be able to find the most relevant job postings, enhancing your lead generation on Upwork.
Remember, practice makes perfect; as you experiment with different queries for your scanners, you'll find your targeted jobs becoming more relevantΒ β
Now, it's time to put this knowledge into action and create the most effective scanners possible. Happy hunting!