DemandFlow Support Centre

INTERVIEW: Interview

A structured interview record against a vacancy, with scheduling, interviewers, type and outcome.

Default definition. This article describes the default INTERVIEW definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches INTERVIEW.

Entity properties

Property	Value
Entity code	`INTERVIEW`
Display name	Interview
Plural	Interviews
Level	11010

Use cases

INTERVIEW is a child of VAC (comboKey SUB|VAC). It replaces free-text interview tracking in VAC notes with a structured record so that interview activity, outcomes and candidate feedback can be reported on across vacancies and candidates. Linked to PPL via the 'candidate' objectLookup; shown on PPL as a stockRecord relatedlist.

Fields

Details

Field	Type	Required	Notes
`name`	text	Yes	Interview title.
`candidate`	reference → `CANDIDATE`	Yes	Candidate.
`vacancy`	reference → `VAC`		Vacancy.
`interviewType`	enum	Yes	Valid ids: `phoneScreen` (Phone Screen), `videoCall` (Video Call), `inPerson` (In-Person), `panel` (Panel), `technicalTest` (Technical Test), `assessmentCentre` (Assessment Centre).
`interviewStage`	enum		Valid ids: `first` (First Round), `second` (Second Round), `third` (Third Round), `final` (Final).
`status`	enum	Yes	Valid ids: `scheduled` (Scheduled), `confirmed` (Confirmed), `completed` (Completed), `cancelled` (Cancelled), `noShow` (No Show).

Scheduling

Field	Type	Required	Notes
`interviewDate`	datetime	Yes	Interview date/time.
`duration`	number		Duration (minutes).
`location`	text		Physical address or video call URL
`interviewers`	array of references → user		Interviewers.

Decision

Field	Type	Notes
`outcome`	enum	Valid ids: `proceed` (Proceed), `reject` (Reject), `hold` (Hold), `offer` (Offer).
`overallRating`	enum	Valid ids: `strongHire` (Strong Hire), `hire` (Hire), `borderline` (Borderline), `noHire` (No Hire).
`nextSteps`	text (multi-line)	Next steps.

Feedback

Field	Type	Required	Notes
`candidateFeedback`	text (multi-line)		Interviewer notes on candidate.
`candidateResponse`	text (multi-line)		Optional. feedback from the candidate about the interview

Attachments

interviewDocuments: interviewDocuments.

Additional panels

Activity timeline panel attached.

Relationships

Lookups: candidate points at a CANDIDATE record; vacancy points at a VAC record; interviewers points at multiple users.

Creating a Interview via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "INTERVIEW",
  "level":    11010,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example",
  "candidate": "",
  "interviewType": "phoneScreen",
  "status": "scheduled"
}

Listing Interviews

# All records in your tenant
GET /v1/entities/INTERVIEW/SUB:<your-sub-id>

DemandFlow Support Centre

INTERVIEW: Interview

INTERVIEW: Interview

Entity properties

Use cases

Fields

Attachments

Additional panels

Relationships

Creating a Interview via the API

Listing Interviews

See also

Was this article helpful?