A careers website should be a system, not a set of pages
Your careers site was true the day it launched. What happens next, and what we changed after fifteen years of watching it happen.
Your careers site was true the day it launched.
Then a department gets renamed. Two teams merge. The graduate scheme page still describes an intake that finished two years ago, and nobody can tell you which of the other forty pages are current either.
We built careers websites that way for fifteen years. Sector bodies, membership organisations, large employers. Good sites, and we would still show you most of them. They aged the same way every time, and it took us too long to admit the pages were the problem, not the people maintaining them.
A page is finished by definition. Your organisation isn't.
It happens to us too
Last month we changed the price of our own careers websites. One number, decided in an afternoon.
That number lived on the pricing page. It also lived on the homepage, the platform page, the software page, the charities page, the sector bodies page, the scope framework, the order form and two sales documents.
Five weeks later we found four of those figures still showing the old price, on five live pages. We only found them because somebody ran an audit.
We build these for a living, and a single number got away from us across our own website for over a month.
Now make it forty role titles after a restructure, and give the job to somebody who has a day job.
Why it goes the same way every time
Nothing goes wrong at launch. Launch is the best day: new photography, copy everyone has argued over, a kind word from the chief executive.
The trouble arrives in year two, and it arrives quietly. A change request becomes a brief, a quote, an approval and a wait. The quote is never unreasonable. But approving it means explaining to a budget holder why a website signed off eighteen months ago needs money spent on it already, and that conversation is easier to postpone than to have.
Meanwhile three more things have changed and nobody has mentioned them.
By year three nobody can say which pages are current. So nobody links to the site internally, and the recruiters go back to emailing PDFs.
The cost of a careers website was never the build. It is year three. And year three is decided by what sits underneath the site, which is the part nobody asks about during procurement, because every demo you are shown is a demo of launch day.
What we do differently now
We stopped treating your roles as page content.
Your roles, your job families and your vacancies live in one place, managed by you, and we build your careers site from that. When a role changes, you change it where it lives rather than hunting for the pages that mention it. The site is generated from your structure instead of describing it from memory.
It is not a technology answer so much as a structural one. The same forty pages, with something underneath them that knows what is true.
What we are not claiming
We are not claiming your website maintains itself. Somebody still has to know that a role has changed and go and change it.
What changes is where that work happens, and how many places it has to happen in. One edit in one place, rather than a hunt across forty pages and a quote to approve.
Two questions worth asking any supplier
Where do my roles live? If the answer is "on the page", you are buying a set of finished objects to describe a moving organisation.
What does year three cost? Not the build, and not the hosting. What it costs to still be true in thirty-six months.
Most suppliers have a good answer to the first. Far fewer have thought about the second, and the second is the one that decides whether anybody in your organisation still trusts the site by the time it matters.
Ours went stale too, for five weeks, over one number. Yours will go stale over forty role titles unless something underneath it is holding them.
Worth a conversation? A discovery call is 25 minutes, no deck. We'll ask what your current site could do better and tell you plainly whether the answer is a rebuild, a content fix, or nothing at all — we've said "nothing at all" more than once.*
Every careers website we build includes a free basic licence covering job roles and vacancies, so your role pages are structured from day one.
