Struct google_jobs3::api::Job
source · pub struct Job {Show 30 fields
pub addresses: Option<Vec<String>>,
pub application_info: Option<ApplicationInfo>,
pub company_display_name: Option<String>,
pub company_name: Option<String>,
pub compensation_info: Option<CompensationInfo>,
pub custom_attributes: Option<HashMap<String, CustomAttribute>>,
pub degree_types: Option<Vec<String>>,
pub department: Option<String>,
pub derived_info: Option<JobDerivedInfo>,
pub description: Option<String>,
pub employment_types: Option<Vec<String>>,
pub incentives: Option<String>,
pub job_benefits: Option<Vec<String>>,
pub job_end_time: Option<DateTime<Utc>>,
pub job_level: Option<String>,
pub job_start_time: Option<DateTime<Utc>>,
pub language_code: Option<String>,
pub name: Option<String>,
pub posting_create_time: Option<DateTime<Utc>>,
pub posting_expire_time: Option<DateTime<Utc>>,
pub posting_publish_time: Option<DateTime<Utc>>,
pub posting_region: Option<String>,
pub posting_update_time: Option<DateTime<Utc>>,
pub processing_options: Option<ProcessingOptions>,
pub promotion_value: Option<i32>,
pub qualifications: Option<String>,
pub requisition_id: Option<String>,
pub responsibilities: Option<String>,
pub title: Option<String>,
pub visibility: Option<String>,
}Expand description
A Job resource represents a job posting (also referred to as a “job listing” or “job requisition”). A job belongs to a Company, which is the hiring entity responsible for the job.
§Activities
This type is used in activities, which are methods you may call on this type or where this type is involved in. The list links the activity name, along with information about where it is used (one of request and response).
- jobs create projects (response)
- jobs get projects (response)
- jobs patch projects (response)
Fields§
§addresses: Option<Vec<String>>Optional but strongly recommended for the best service experience. Location(s) where the employer is looking to hire for this job posting. Specifying the full street address(es) of the hiring location enables better API results, especially job searches by commute time. At most 50 locations are allowed for best search performance. If a job has more locations, it is suggested to split it into multiple jobs with unique requisition_ids (e.g. ‘ReqA’ becomes ‘ReqA-1’, ‘ReqA-2’, etc.) as multiple jobs with the same company_name, language_code and requisition_id are not allowed. If the original requisition_id must be preserved, a custom field should be used for storage. It is also suggested to group the locations that close to each other in the same job for better search experience. Jobs with multiple addresses must have their addresses with the same LocationType to allow location filtering to work properly. (For example, a Job with addresses “1600 Amphitheatre Parkway, Mountain View, CA, USA” and “London, UK” may not have location filters applied correctly at search time since the first is a LocationType.STREET_ADDRESS and the second is a LocationType.LOCALITY.) If a job needs to have multiple addresses, it is suggested to split it into multiple jobs with same LocationTypes. The maximum number of allowed characters is 500.
application_info: Option<ApplicationInfo>Required. At least one field within ApplicationInfo must be specified. Job application information.
company_display_name: Option<String>Output only. Display name of the company listing the job.
company_name: Option<String>Required. The resource name of the company listing the job, such as “projects/api-test-project/companies/foo”.
compensation_info: Option<CompensationInfo>Optional. Job compensation information.
custom_attributes: Option<HashMap<String, CustomAttribute>>Optional. A map of fields to hold both filterable and non-filterable custom job attributes that are not covered by the provided structured fields. The keys of the map are strings up to 64 bytes and must match the pattern: a-zA-Z*. For example, key0LikeThis or KEY_1_LIKE_THIS. At most 100 filterable and at most 100 unfilterable keys are supported. For filterable string_values, across all keys at most 200 values are allowed, with each string no more than 255 characters. For unfilterable string_values, the maximum total size of string_values across all keys is 50KB.
degree_types: Option<Vec<String>>Optional. The desired education degrees for the job, such as Bachelors, Masters.
department: Option<String>Optional. The department or functional area within the company with the open position. The maximum number of allowed characters is 255.
derived_info: Option<JobDerivedInfo>Output only. Derived details about the job posting.
description: Option<String>Required. The description of the job, which typically includes a multi-paragraph description of the company and related information. Separate fields are provided on the job object for responsibilities, qualifications, and other job characteristics. Use of these separate job fields is recommended. This field accepts and sanitizes HTML input, and also accepts bold, italic, ordered list, and unordered list markup tags. The maximum number of allowed characters is 100,000.
employment_types: Option<Vec<String>>Optional. The employment type(s) of a job, for example, full time or part time.
incentives: Option<String>Optional. A description of bonus, commission, and other compensation incentives associated with the job not including salary or pay. The maximum number of allowed characters is 10,000.
job_benefits: Option<Vec<String>>Optional. The benefits included with the job.
job_end_time: Option<DateTime<Utc>>Optional. The end timestamp of the job. Typically this field is used for contracting engagements. Invalid timestamps are ignored.
job_level: Option<String>Optional. The experience level associated with the job, such as “Entry Level”.
job_start_time: Option<DateTime<Utc>>Optional. The start timestamp of the job in UTC time zone. Typically this field is used for contracting engagements. Invalid timestamps are ignored.
language_code: Option<String>Optional. The language of the posting. This field is distinct from any requirements for fluency that are associated with the job. Language codes must be in BCP-47 format, such as “en-US” or “sr-Latn”. For more information, see Tags for Identifying Languages{: class=“external” target=“_blank” }. If this field is unspecified and Job.description is present, detected language code based on Job.description is assigned, otherwise defaults to ‘en_US’.
name: Option<String>Required during job update. The resource name for the job. This is generated by the service when a job is created. The format is “projects/{project_id}/jobs/{job_id}”, for example, “projects/api-test-project/jobs/1234”. Use of this field in job queries and API calls is preferred over the use of requisition_id since this value is unique.
posting_create_time: Option<DateTime<Utc>>Output only. The timestamp when this job posting was created.
posting_expire_time: Option<DateTime<Utc>>Optional but strongly recommended for the best service experience. The expiration timestamp of the job. After this timestamp, the job is marked as expired, and it no longer appears in search results. The expired job can’t be deleted or listed by the DeleteJob and ListJobs APIs, but it can be retrieved with the GetJob API or updated with the UpdateJob API. An expired job can be updated and opened again by using a future expiration timestamp. Updating an expired job fails if there is another existing open job with same company_name, language_code and requisition_id. The expired jobs are retained in our system for 90 days. However, the overall expired job count cannot exceed 3 times the maximum of open jobs count over the past week, otherwise jobs with earlier expire time are cleaned first. Expired jobs are no longer accessible after they are cleaned out. Invalid timestamps are ignored, and treated as expire time not provided. Timestamp before the instant request is made is considered valid, the job will be treated as expired immediately. If this value is not provided at the time of job creation or is invalid, the job posting expires after 30 days from the job’s creation time. For example, if the job was created on 2017/01/01 13:00AM UTC with an unspecified expiration date, the job expires after 2017/01/31 13:00AM UTC. If this value is not provided on job update, it depends on the field masks set by UpdateJobRequest.update_mask. If the field masks include expiry_time, or the masks are empty meaning that every field is updated, the job posting expires after 30 days from the job’s last update time. Otherwise the expiration date isn’t updated.
posting_publish_time: Option<DateTime<Utc>>Optional. The timestamp this job posting was most recently published. The default value is the time the request arrives at the server. Invalid timestamps are ignored.
posting_region: Option<String>Optional. The job PostingRegion (for example, state, country) throughout which the job is available. If this field is set, a LocationFilter in a search query within the job region finds this job posting if an exact location match isn’t specified. If this field is set to PostingRegion.NATION or PostingRegion.ADMINISTRATIVE_AREA, setting job Job.addresses to the same location level as this field is strongly recommended.
posting_update_time: Option<DateTime<Utc>>Output only. The timestamp when this job posting was last updated.
processing_options: Option<ProcessingOptions>Optional. Options for job processing.
promotion_value: Option<i32>Optional. A promotion value of the job, as determined by the client. The value determines the sort order of the jobs returned when searching for jobs using the featured jobs search call, with higher promotional values being returned first and ties being resolved by relevance sort. Only the jobs with a promotionValue >0 are returned in a FEATURED_JOB_SEARCH. Default value is 0, and negative values are treated as 0.
qualifications: Option<String>Optional. A description of the qualifications required to perform the job. The use of this field is recommended as an alternative to using the more general description field. This field accepts and sanitizes HTML input, and also accepts bold, italic, ordered list, and unordered list markup tags. The maximum number of allowed characters is 10,000.
requisition_id: Option<String>Required. The requisition ID, also referred to as the posting ID, assigned by the client to identify a job. This field is intended to be used by clients for client identification and tracking of postings. A job is not allowed to be created if there is another job with the same [company_name], language_code and requisition_id. The maximum number of allowed characters is 255.
responsibilities: Option<String>Optional. A description of job responsibilities. The use of this field is recommended as an alternative to using the more general description field. This field accepts and sanitizes HTML input, and also accepts bold, italic, ordered list, and unordered list markup tags. The maximum number of allowed characters is 10,000.
title: Option<String>Required. The title of the job, such as “Software Engineer” The maximum number of allowed characters is 500.
visibility: Option<String>Deprecated. The job is only visible to the owner. The visibility of the job. Defaults to Visibility.ACCOUNT_ONLY if not specified.