The Careers module runs the hiring side of the site: the careers page itself, the open positions on it, and the applications people send in. Three pieces, one flow: you publish a position, a candidate applies on the site, the application lands in the admin with the CV attached.
Careers → Careers page is the landing page, built from its own blocks: a hero, an overview, the hiring process steps, the open positions list and an open application section for candidates who don't fit a listed role. The positions list fills itself, every published position appears there automatically, so day to day you rarely touch this page.
Its second tab, Application Form, holds the copy around the form: the title and description shown above it on every position page, and the success screen a candidate sees after submitting. Written once here, reused by all positions.
A position is one job ad, created under Careers → Positions. The General tab asks for the title, the location, the work mode (on-site, hybrid, remote), the employment type (full time, part time, contract, internship) and Open Until, the last day applications are accepted. The Content tab is the ad itself, free text for the role, responsibilities, expectations and benefits.
Open Until does real work: at the end of that day the site stops accepting applications for the position, server-side, even if someone still has the form open. The position page stays up, only the form closes. To extend a deadline, move the date and publish.
Positions are draft-enabled like pages, so you can prepare an ad, schedule it to go live on the announcement day, and unpublish it when the role is filled.
Two more tabs matter less often. Structured Data feeds the Google Jobs listing: optional street address details and an optional salary range, leave salary empty to keep it private. Applications lists every application received for this position, newest first.
Applications arrive on their own, the site's form creates them, nobody in the admin can. Each one is read-only: which position it was for (empty means an open application), the candidate's contact details, the LinkedIn profile if given, the CV and the privacy consent checkbox. The form validates hard before anything lands here: required contact fields, a captcha, consent, and a CV up to 10 MB.
Read-only is deliberate. An application is a record of what the candidate submitted, not a document to edit. The only thing you can do with one is delete it, which is how GDPR removal requests get honored, deleting the application removes the stored CV with it.
CVs themselves sit in a hidden storage collection you never browse directly, open them from the application they belong to.