How to recruit through your careers page and keep it tidy
For a small company, your own site is often where the best candidates apply: they already know who you are. To recruit through your careers page you need four things in place: each role written as its own page, an application route that lands somewhere your hiring team works, a reply to every applicant, and a habit of taking roles down the day they close.
Set up roles as a collection
In Anticode, make a CMS collection called jobs with typed fields for the role: title, team, location and working pattern, salary range, a summary, responsibilities, what you're looking for, how to apply, and a closing date. Each entry is served as its own page at /jobs/<slug>, and the collection's list sits at /jobs/. Whoever's hiring edits entries in the dashboard; nobody has to touch the layout.
A role that's its own page can be linked from a job board post, a social update or an email to a recruiter, and the address stays the same until you remove it.
Write a listing people finish reading
- A plain job title candidates would search for. "Bookkeeper", not "Numbers Ninja".
- The salary range. Listings without one get fewer and less suitable applications, and in some places publishing it is required.
- Where and when: office, hybrid or remote, hours, and start date.
- Five to eight real responsibilities and a short list of what's essential versus nice to have. Long wish-lists put good people off.
- What happens after applying: the stages, who they'll meet, and when you'll reply.
Choose the application route
Anticode's forms don't accept file uploads, so a CV can't be attached on the site. That leaves three honest options:
| Route | How it works | Best when |
|---|---|---|
| A clear address on each role page, such as jobs@ your domain, with "send your CV and two lines on why" | A handful of roles and applicants | |
| Application form | A custom form with your questions and a field for a link to a CV or portfolio, sent to Airtable or Notion | You want every applicant's answers in one table |
| Applicant tracking system | Link from each role to the role's page in your ATS | Steady hiring with several interviewers |
For the form route: the built-in contact form only takes a name, email and message, so an application with its own questions is a custom form tied to a site function, which accepts up to 30 plain-text fields. Connect Airtable or Notion, and each application arrives as a record naming the site and form, with the answers in a details field. Ask only what helps you shortlist.
Run each hiring round in order
- Publish the role as a new entry and link it from the careers page and wherever you're advertising.
- Acknowledge every application within two working days, from your own inbox. Anticode doesn't email applicants.
- Shortlist in your table, adding columns for stage, reviewer and outcome. Keep notes factual.
- Reply to everyone, including people you don't interview. A short, kind no is remembered.
- Close the role the day it's filled or the closing date passes. Delete its entry: collection pages are served from the collection, so the role page and its line in the list go with it. If another page mentions the role, edit that and republish. A role left up for months tells candidates you're disorganised or always losing staff.
- Delete applications you no longer need from Anticode's submissions and from your table, in line with your privacy policy.
Candidate data and privacy
Applications are personal data, sometimes sensitive. Submissions are sealed at rest in Anticode, and a site that collects data can't be published until the account owner and the person publishing have two-factor sign-in turned on. An access log keeps the last 200 reads, exports and deletes of form data. Anticode writes a starting Privacy Policy from what the site collects; add how long you keep applications and who sees them, and check it fits the rules where you hire. It isn't legal advice.
What goes wrong
- Applications vanish
- Each submission goes to Airtable or Notion once, with no retries. If a token expires, they stop arriving there but stay in Anticode's submissions. Test after any change.
- Candidates can't send a CV
- Say clearly on the role page how to share it: a link field on the form, or email.
- Old roles still attract applications
- Make closing the entry part of the offer-accepted checklist.
Limits
Anticode hosts the careers page and role pages, collects applications through a form and passes them to your tools. It doesn't accept file uploads, email candidates, schedule interviews, score applicants or post to job boards. Build the page with the careers page builder; for forms that send to a table, see Airtable and storing form data safely.
Questions people ask
Can candidates upload a CV through my Anticode site?
No, forms don't take file uploads. Ask for a link to a CV or portfolio in the form, or for the CV by email.
Where do applications go?
They're saved in Anticode's submissions and can be emailed to you or sent to Airtable, Notion, Google Sheets or another connector.
How do I take a job down?
Delete the role's entry from the jobs collection. Collection pages are served straight from the collection, so the role page goes with it; republish only if another page mentions the role.