A careers page is a list of roles and a form, and the part that usually breaks is after the form: on 54 each application is a private record with the CV attached, visible only to whoever logs in, and you answer from a mailbox on your own domain.
Hiring starts with a page and dies in a shared inbox. Forty applications arrive as forty emails with attachments, **two people answer the same candidate and nobody answers the other thirty-eight** — which is a data problem wearing a process costume.
Swipe to compare all columns →
| The shared inbox | 54 | |
|---|---|---|
| Where an application lands | An inbox everyone reads | A private record, with the CV attached |
| Who already replied | Ask in a chat | Written on the record |
| The CV | An attachment to find again | Attached to the candidate |
| Who can see it | Everyone with the inbox | Only a logged-in owner |
| Answering | From a personal address | From a mailbox on your domain, shared with the people who hire |
Written from each product's public documentation. Products change: check theirs before you decide. No prices here for the same reason.
Yes, a file attached to their record.
Only people who log in; the records are private.
Yes, and only that mailbox: not the rest of the site.
Yes, from the panel.
Yes, each with its own page and its own form.
Yes, and the page stops being served and leaves the sitemap.
Yes, from the admin.
It is the two parts most teams actually use: the page and the applications in one place with who answered.
Yes, and require them before the record is written.
You delete the record, and deleted means deleted.