Careers sitePostings
Say enough, and only what you chose to say. The details people actually filter on, pay you can state or leave out, boilerplate written once, and a role that stops accepting on the date you set.
The details people filter on. Plus the one they always look for.
Department, location and the kind of engagement, including volunteer, which most hiring software makes you pretend is a part-time job. Compensation is yours to state, per posting.
- Department and location, because that is what people filter on
- Five kinds of work, and volunteer is one of them
- Pay as a range, one end of a range, or nothing
- By the hour, by the year, or for the project
- In your currency, per posting rather than per account
Write the boilerplate once. Then stop rewriting it.
Who you are, what you offer, how you hire: kept as reusable sections that attach themselves to new postings, so the parts that should be identical actually are.
- Write the boilerplate once, as reusable sections
- Attach them to every posting automatically, or not
- Mark the ones a posting must always carry
- Order them the way a posting should read
- Fix a typo once and every future posting is right
Draft, published, closed. Three different things, kept different.
Draft, published and closed behave differently on purpose. A closing date ends the form without anybody having to remember to.
- A draft nobody has seen is not the same as a closed role
- Published and closed are recorded with their own dates
- And a closing date stops the form on its own
- So the posting can end without anybody being at a desk
A posting is wired in. It knows three things about the rest of Cadre.
It knows its team
A posting points at the team it is hiring into, which is why the org chart can show you where the gaps are without a separate headcount spreadsheet.
It knows its pipeline
Every posting names the pipeline applicants will move through. New postings start from your default, and you change it per posting when the hiring is genuinely different.
It knows its form
The question set attached to a posting becomes its apply form, copied onto the posting so later edits to the set leave it alone.
Published, under your brand
The opening as a candidate meets it: your hero, your colours, the details they came for, and an apply button that goes to a form you built.
Then they apply. On a form you built, not a template’s.
No. Compensation is entirely optional, and it is a per-posting decision rather than an account setting. Give both ends of a range, one end, or nothing at all: the posting shows exactly what you give it and nothing more.
Yes. Volunteer is one of the five engagement types, alongside full-time, part-time, contract and internship, so a volunteer call and a staff role sit on the same careers page and run through the same pipeline machinery.
Closing is something you do; a closing date is something the posting does. Set a date and the public form stops accepting on it, without anybody being at a desk that morning. Closing it yourself is a separate, recorded act, and both are different again from a draft nobody has seen.
No. Openings publish to your own Engagement Hub under your own brand. There is no feed to Indeed or LinkedIn today. Where you want a posting on a board, you put it there yourself and point it back at your apply link, which is also how the source ends up recorded correctly.
Not as a workflow. A posting is a draft until somebody publishes it, and publishing is the review. There is no approval chain and no scheduled publish.