Skip to main content

Interview portal configuration

Generates the document imported by Portal customisation → Interview portal → Import configuration. The interview portal is the candidate-facing side: the public position pages, the apply flow, and the screens a candidate sees around an interview. It is a different product from the coaching portal and has its own languages and content. Every field is optional — omitted fields keep their current value. Languages are only ever added, never removed.

Document

Fields

The read-more block

readmore_text, readmore_link and readmore_button are one unit. Supply all three or none — a partial set renders a block with a missing label or a button that goes nowhere.

Ids

public_avatar_id and discover_id are database ids. Never invent them. If you do not have a confirmed id, emit null or omit the field. A fabricated id produces a broken page rather than a validation error, because the importer cannot check ids that live in another table.

Markdown

Rendered with a restricted renderer: headings, bold, italic, lists, links. In hero_box, wrapping a word in _underscores_ renders it as the italic accent word. Keep interview_completed_box short — it is read once, by someone who has just finished an interview and wants to know what happens next. Say what happens and when.

Rules

  • Put the primary language first in pages[] — the editor opens on it after import.
  • Write candidate-facing copy in second person (“your application”), not third (“the candidate’s application”).
  • Do not set public_interviews_disabled: true on a portal whose whole purpose is a public careers page; check before emitting it.