Recruitment
Jobs, applications and candidates. The hiring side of an internal tool, from the posting to the person.
⚠️ Pro edition
These screens are in the Pro download. The free edition ships the design system and the demo, not the application screens.
The screens
5 screens, at these routes in your download. Open them beside this page.
| Route | Screen | What it is for |
|---|---|---|
| /jobs | Jobs | Open roles as a table: department, location, status and applicant count. |
| /job-detail | Job detail | One role's description, requirements and its pipeline of applicants. |
| /job-apply | Apply | The application form a candidate fills in, with file upload and validation. |
| /candidates | Candidates | Everyone who applied, filterable by stage and role. |
| /candidate-profile | Candidate profile | One person: their details, documents, notes and stage. |
What you get
- A stage model visible on both the candidate table and the profile, so a pipeline reads the same in either place.
- An application form with the file field, required marks and error states already wired to the theme.
- Notes and activity as a timeline beside the record rather than a second screen.
What you connect
These are interfaces, not an application.They render, they hold their own state, and they talk to nothing. Everything below is your application's, and none of it is supplied.
- Your ATS or database. Candidates, jobs and stages are demo records.
- File storage. CVs are selected and previewed; nothing is stored.
- Email. No message is sent at any stage. Rejections, invitations and reminders are yours.
- Permissions. Every screen assumes the viewer may see every candidate.
Built from
Nothing here is a one-off. Each screen composes the same families documented in the reference, so changing a token moves them with the rest of the product.
data-table, record-view, form, steps, avatar.
Next
A customer screen, end to end builds one of these from an empty route, and Theming is how you make them look like yours.