Job Search basics

Cloud Talent Solution (CTS) - Job Search is designed to transform the recruiting and talent acquisition industry by powering your job search and candidate matching solutions with built-in Machine Learning (ML) algorithms. CTS - Job Search is designed to be integrated with your existing job search site. Your site may belong to any of four basic use cases:

  1. Job boards (returns a list of jobs to job seekers)
  2. Career site providers (provides career site services to client companies)
  3. Staffing agencies (provides short- or long-term employees to clients)
  4. Applicant tracking systems (tracks applicants throughout the hiring process)

Business goals and metrics vary significantly between companies. Job Search is designed to be customizable, so you can modify API performance based on your needs. The best practices, implementation guide, and launch checklist documentation is intended to guide you through factors that you need to consider when setting up the Job Search to meet your specific goals.

How the Job Search works

CTS - Job Search enables you to leverage Google's Machine Learning (ML) technology within your own website. You send a list of jobs and companies to CTS, which stores them and indexes them into a searchable form. It uses a pre-trained ML model with your provided data to return relevant search results. You can then render the API output to your company site as viewable results. As soon as Job Search is integrated with your system your users will begin seeing high quality search results immediately.

Multi-tenancy

Cloud Talent Solution supports three organizational tiers. All data uploaded to CTS is owned by a project that you create in Google Cloud Platform. Optionally, data can be assigned to one or more tenants, a middle organizational layer between the project and data levels. A tenant enforces data isolation for the client (for example, data can't be queried across more than one tenant in a single API call) as well as machine learning training models. Setting up multiple tenants in a single project is useful for situations where you are supporting more than one customer and don't want to share data between them, but would like to use the same project for billing and reporting internally. For example:

  • Job site providers building job sites for organizations with multiple subsidiary companies.
  • Hiring agencies building applicant tracking systems for multiple businesses.

To learn more about multi-tenancy, see the Best Practices documentation.

For more information on implementing Job Search in your UI, see our implementation guide.

Var denne siden nyttig? Si fra hva du synes:

Send tilbakemelding om ...

Job Search documentation