Job search launch checklist (v3)

The first 3 sections apply to all Job search use cases. Specific instructions tailored to different applications of Job search are available in section 4.

1. Prepare

  • Identify your business goals and the key metric(s) to track during setup and testing.
  • Download the client libraries in the language of your choice.
  • Create an architecture summary. Include:
    • An overall architecture diagram.
    • A summary of process flows outlining:
      • Creating jobs and companies.
      • Updating jobs.
      • Latency.
      • Maintenance efforts.
  • Estimate your quota:
    • Estimate how frequently jobs are CUD (Created, Updated and Deleted) and how often job seekers are receiving job email alerts. There are 2 main use cases:
      • Capacity for the initial load or reload.
      • Capacity for normal operations.
    • Estimate how frequently job seekers are searching for jobs:
      • Capacity at peak.
      • Capacity for normal operations.

2. Index companies and jobs

  • Create Company objects:
    • Create at least one Company. We recommend creating Company objects for all companies in your database with open jobs.
  • Create Job objects:
    • Create Jobs for your Companies. We recommend creating Job objects for all open jobs in your database.
  • Test retrieval of Companies and Jobs:
    • Use the GET method to ensure that created Companies and Jobs are indexed by CTS correctly.

3. Implement search and client events

  • Implement basic search:
    • Implement search in your existing UI.
      • Use our how-to guides for implementation tips for basic search.
    • Implement search filters.
    • Implement location search.
      • Allow job seekers to find jobs in their preferred location by enabling location search.
    • Implement autocomplete.
    • Implement pagination.
      • As a best practice, we recommend returning 20 or fewer jobs per page to reduce latency in our API return.
    • Enable spell checking.
      • Return relevant results even if a job seeker mistypes a keyword.
    • Implement histograms.
      • Return the number of jobs associated with a given query.
    • Implement client events.
      • Add client event data to your domain to improve the relevance of your search results over time. Use our how-to guide for implementation tips.

4. Recommendations according to use cases

Job boards

We recommend that job boards implement the following features to get the most out of Cloud Talent Solution:

  • Incorporate business logic into your search results. Cloud Talent Solution allows you to return high-value job postings at the top of your search results. Consult our best practices and determine which of the following options makes the most sense for your business needs:
    • Featured Jobs: Highlight important jobs at the top of your search results based on your assigned promotional value.
    • Custom ranking: Highlight jobs based on multiple variables rather than a single variable. This option is most useful for applications with multi-tiered Cost-per-Click subscriber systems.
  • Commute Search: Allow your customers to search for jobs based on their commute preferences.

Staffing agencies

We recommend that staffing agencies implement the following features to get the most out of Cloud Talent Solution:

  • Search by requisition ID:
    • For recruiters who need to search by requisition ID, we recommend setting the search request flag disable_keyword_match to its default of false to ensure that only the specific job required is returned.
    • Alternatively, you can allow recruiters to search by requisition ID by querying reqid:(requisition id). If this is a common use-case for your users we recommend highlighting this ability in your UI.

Career site providers

We recommend that career site providers implement the following features to get the most out of Cloud Talent Solution:

  • Incorporate business logic into your search results. Cloud Talent Solution allows you to return high-value job postings at the top of your search results. Consult our best practices guide for details.
    • Featured Jobs: Highlight important jobs at the top of your search results based on your assigned promotional value.
  • Commute Search: Allow your customers to search for jobs based on their commute preferences.
  • Search by requisition ID:
    • For recruiters who need to search by requisition ID, we recommend setting the search request flag disable_keyword_match to its default of false to ensure that only the specific job required is returned.
    • Alternatively, you can allow recruiters to search by requisition ID by querying reqid:(requisition id). If this is a common use-case for your users we recommend highlighting this ability in your UI.
  • Query broadening: Relax restrictions on location and job categories in order to increase the number of results returned. While the relevance of overall search results may decrease, engagement metrics such as click through rate may increase.

Job aggregators

We that job aggregators implement the following features to get the most out of Cloud Talent Solution:

  • Incorporate business logic into your search results. Cloud Talent Solution allows you to return high-value job postings at the top of your search results. Consult our best practices and determine which of the following options makes the most sense for your business needs:
    • Featured Jobs: Highlight important jobs at the top of your search results based on your assigned promotional value.
    • Custom ranking: Highlight jobs based on multiple variables rather than a single variable. This option is most useful for applications with multi-tiered Cost-per-Click subscriber systems.

Best practices

For a more details on the features and parameters listed here, see our best practices documentation.