Careers page and publishing a job
Your open roles can live on a public careers page under your own name - and nothing is public until you say so twice. The workspace has one switch (HR > Careers page) and every job has its own. Both start off.
- Switch the page on: HR > Careers page > The page. Your address is workbos.com/careers/<your-name>, or your own domain once it is verified in Appearance. Choose the address before you share it - every job link and everything Google indexes hangs off it.
- Write what it says: a headline, an introduction, an equal-opportunity statement (required by law in some places), a link to a culture page and a careers contact address. All optional; the page reads fine with just a headline.
- Publish a role: open the job in HR > Jobs, go to the Publishing tab and press Publish. The web address is made from the title, so a non-technical person never sees the word "slug". Unpublish takes it straight back down.
- The advert: the Advert tab holds the summary, the role, responsibilities, requirements and benefits. Lines starting with "- " become bullets on the public page.
- Location and pay: city, region and country are what a job board reads; the free-text location line is what a person reads. Salary is stored as a range and hidden until you tick "Show the salary on the public page" - pay transparency is required in some places and optional in others, so it is your decision per role.
- Where people apply: on your page into this workspace, on another website (your existing ATS), or by email. WorkBOS is the default, not the only option.
- Applications close: set a date and the role stops being served and drops out of Google for Jobs. That is what stops people applying for a filled role.
Every published job carries schema.org JobPosting data, which is what Google for Jobs reads. You do not have to do anything for it - publish the role, and it is in the page Google receives.
Applications from the careers page land in HR > Applications at the Applied stage, tagged as coming from Careers. A second application from the same email for the same role is recognised as the same person, so a double-clicked button is one candidate.
ATTACHING A CV. Turn this on in HR > Careers page and a candidate can attach their CV when they apply - a PDF, a Word document, an RTF or a plain text file, up to 5 MB. You can leave it optional or make it required. Every file is checked by looking at what it actually is, not just its name, so a file dressed up to look like something it is not is refused before it ever reaches your workspace.
A CV is kept privately. Nobody can open it by guessing or sharing a link - only someone with access to your Applications can open it, and each time they do, a fresh, time-limited link is created just for that moment.
THE THANK-YOU EMAIL. When someone applies, they can automatically get a short email confirming you have received it, sent from your own workspace address. It is on by default and you can switch it off, and you can add your own line to the message - for example, how long hiring usually takes.
HOW LONG A CV IS KEPT. A CV is personal information someone sent you for one reason, so it does not stay forever by default. Choose how long to keep it, from 30 days up to 10 years - a nightly check quietly removes the file itself once it passes that age. The application record stays in your history either way; only the attached file is removed, and the candidate’s name and the file name they used are kept for your records.
In HR > Applications, filter the list to "Careers page" to see only candidates who applied through your public page, versus everyone added another way.
Who can do what: an owner or admin switches the careers page on and edits its text. An owner, admin or member publishes and unpublishes a role, provided their role still has write access to Jobs. A viewer can do neither - and that is enforced by the server, not by hiding the button.
GETTING ONTO THE JOB BOARDS. Job boards do not read your careers page. They read a feed - a plain web address listing your open roles in the shape their system expects, which they re-check on a schedule. HR > Careers page > Job boards has the address for each board, with a copy button.
- Give a board the address once. From then on, publishing a role here puts it on that board and unpublishing takes it down - there is nothing to re-enter and nothing to keep in sync.
- Indeed, Jooble and Jobrapido take the address directly and need no contract. Glassdoor is part of Indeed and reads the same index, so setting up Indeed covers it - there is no separate address for it.
- LinkedIn, Monster and ZipRecruiter will not read a feed without a signed partner agreement, so their addresses are shown but marked as needing that first. Post to those by hand until the agreement is in place.
- Jooble only lists roles published in the last 45 days, so a long-running vacancy is worth republishing.
- Google needs no setup at all: it reads the careers page itself, and every published role already carries what it needs.
- A board always sends candidates to your careers page, even for a role whose apply button points at your own recruiting system. That way the link keeps working if you change where applications go.
A feed contains exactly what your careers page already shows in public: published, unexpired roles, and a salary only where you chose to show one. It carries no applicant information, and it stops working the moment you switch the careers page off.