Skip to main content

Interviews

The interviews (seven20__Interview__c) object is used to represent an interview that has been scheduled for a job application. It contains a number of fields that are used to track the progress of the interview through the recruitment process. The object is highly customisable, fully allowing different types of interviews to be configured to specific business needs, e.g. First Stage Interview, Phone Interview, etc.

Interview creation

An interview is usually created through the use of the ATS stage transitions, when an application is moved to a stage which has been configured as an interview stage. Alternatively, there is no restriction on creating interviews manually, or via automation.

tip

Further details around the customisation of Interviews created via the ATS, including field sets, are documented here.

Regardless of how an interview is created, the following fields are automatically populated on creation, before the record is committed to the database:

Field NameValue
seven20__Application__cThe application the interview is associated with
seven20__Account__cThe account the application (seven20__Application__c.seven20__Account__c) is associated to
seven20__Candidate__cThe contact the application (seven20__Application__c.seven20__Candidate__c) belongs to
seven20__Job__cThe job the application (seven20__Application__c.seven20__Job__c) is against
seven20__Hiring_Manager__cThe hiring manager (seven20__Job__c.seven20__Hiring_Manager__c) of the job
OwnerIdThe Id of the interview owner

Interview events

Whenever an interview is created, a companion Event record is created, which appears in the Salesforce calendar. The relationship is a one-to-one relationship, and is established by the seven20__Interview__c.seven20__Event_Id__c field and a lookup field to Interview on the Event object (Event.seven20_Interview__c).

warning

Do not modify the seven20__Interview__c.seven20__Event_Id__c or the Event.seven20__Interview__c fields, as this will break the relationship between the two records, and any automations which rely upon it.

Interviews and events are synced in both directions, so that any changes made to either record will be reflected in the other, with the following fields being synced:

Interview fieldEvent field
seven20__End__cEndDateTime
seven20__Start__cStartDateTime

In addition to the above, there are a number of fields which are populated on the event creation:

Event FieldValue
SubjectThe event subject is a concatenation of the candidate's name, account name and job name. E.g. "Candidate Name: Account Name: Job Name", if these are null, it defaults to "Interview"
OwnerIdSet to the Id of the user creating the interview
WhoIdThe interview's seven20__Candidate__c value
WhatIdThe interview's Id
info

When an interview is deleted, the corresponding event is also deleted.

Interview counts

Whenever a new interview is created or deleted, the total number of interviews is rolled up against several different objects. These are:

ObjectField NameDescription
seven20__Job__cseven20__Total_Interviews__cSum of all interviews against the job
seven20__Job__cseven20__Unique_Interviewees__cNumber of unique candidates interviewing for this job
seven20__Application__cseven20__Interview_Count__cSum of all interviews for this application

Alongside the above fields, a number representing the sequence of interviews is recorded on the interview record itself on the seven20__Interview_Number__c field. This is used to determine the order of interviews for a candidate, and is used to determine the next interview in the sequence when an interview is created. For example, if a candidate has already had two interviews, the next interview will be assigned a value of 3.

warning

The value of seven20__Interview_Number__c is calculated via a SOQL aggregate function, equivalent to Count(ID). Modifying this field value will result in the sequence being broken, and may result in unexpected behaviour.