Audience
Internal
Displayed Description
Page Type
Article
Which field is this pulling from?
ATS | Location Stored Where? |
Greenhouse | GreenhouseCandidate.addresses |
Workday | WorkdayCandidate.address |
SuccessFactors | missing |
SmartRecruiters | SmartRecruitersCandidate.location |
Lever | LeverContact.location |
AtsLite / Gem Jobs | Person.location |
OATS | Person.location |
iCIMS | missing |
Taleo | ??? |
- Derived value from curr_work_location, typically from available fields like work experience/location.
- There are 2 GH location fields - one on the profile (typically a home address), another on the application (where are you located). We chose the former, despite known data quality issues since Prospect Search surfaces candidate level data. This helps us simplify the logic and avoid potential collisions.
Candidate location as a filter in other surfaces(TalentPipeline, App Review)
- In App Review task: https://app.asana.com/0/1205297914345529/1205534669284096/f
- In Talent Pipeline: can I learn more about this request?
- Why isn’t it available everywhere in Gem? Don’t we have it now?
- Unfortunately, a bit more complicated to expose in multiple places in our product! App Review and Prospect Search are built using different ElasticSearch indices. We’ve added it to one, but not the other. These are independent, discrete pieces of work, and each takes about 2 weeks + buffer for deployment.
- Which field is this pulling from?
- Candidate location as a filter in other surfaces(TalentPipeline, App Review)