Careers pages that filter people in, not out

I produce Brassfern's projects, which means I sit in every debrief when a hire works out and every retrospective when one doesn't. The pattern that took me embarrassingly long to see: bad hires rarely start with a bad interview. They start with a careers page that attracted the wrong hundred people and repelled the right twenty. Your careers page is not a bucket for collecting résumés. It's a filter — and right now it's probably filtering out the candidates you'd most want, while waving through the ones who apply to everything with the word "fast-paced" in it.

This piece is about rebuilding the careers page as a self-selection device: one that makes the right person think finally, someone being straight with me and the wrong person quietly close the tab. Both outcomes are wins.

The filter works before the application

Every element of a careers page pushes someone toward or away from applying. That's the whole mechanism. The mistake is optimising the page for volume of applications — big enthusiastic copy, vague perks, minimum requirements inflated to "10x ninja" — when volume is the thing you're drowning in. What you want is precision: fewer, better-matched applicants who already made an informed choice.

This reframes everything downstream. Requirements lists stop being a wish list and become a boundary. Salary transparency stops being a risk and becomes the sharpest filter you own. The application flow itself becomes a preview of working with you. When we rebuilt our own careers page on these principles, application volume dropped by roughly a third and offer-acceptance rate nearly doubled (illustrative numbers, but the direction is what matters). Less noise in, better signal out. The whole employer brand argument rests on this: a careers page is a brand page with consequences.

Show the work, not the wallpaper

Candidates who are good at their craft want one thing above all: evidence they'll get to practice it. The standard careers page gives them a photo of the snack wall and a paragraph about "our amazing culture." That's wallpaper. The candidates you want scroll straight past it looking for the work.

So give them the work. On our page, every open role links to real case studies the team shipped — the engineer reading about a design-engineer role can look at the sites and products we've actually delivered and judge the bar for themselves. Include the messy truth where you can: a short note about a project that went sideways and what changed afterwards is worth more than any "we value learning" bullet. Candidates with real scar tissue recognise real scar tissue.

Specific beats generic at sentence level too. Compare "You'll work on exciting challenges for global brands" with "You'll own the design system for a telehealth platform used by regional clinics." The second sentence filters. It's checkable. It lets someone imagine a Tuesday. Write every line of the careers page so a candidate can picture a specific Tuesday.

Salary bands: the honesty that filters hardest

Posting salary bands is still treated as radical, which tells you how low the bar is. Here's what actually happens when you publish them: a third of your screen-time disappears. Candidates who would have applied at the wrong expectation self-select out before costing you a recruiter screen, a hiring-manager hour and their own afternoon. Candidates who were underpaid elsewhere and assumed you'd be the same — often exactly the senior people you're chasing — apply where they wouldn't have bothered.

The objections are mostly about negotiating leverage, and they're mostly wrong. You lose a little room at the margin; you gain a shorter process, a fairer one, and a public signal that the company's internal talk about transparency isn't decorative. Our senior product engineer listing carries the band right in the header block, and the single most common line in accepting candidates' feedback is some version of "you were the only ones who didn't make me guess."

If you genuinely can't publish a number, publish a range and explain the band logic — level, location adjustment, review cadence. Even the explanation filters, because it shows the candidate how decisions get made before they've joined.

The application flow is a product demo — of you

Candidates experience your application form as a working prototype of your company's regard for people's time. A studio that claims to obsess over UX and then asks applicants to upload a résumé and retype it into eleven fields has just demoed its real product: bureaucracy.

Design the flow like you'd design a checkout, because it is one — the candidate is paying with their career. The rules are the ones we apply in designing forms people actually finish:

• Ask for the minimum viable application. Résumé or profile link, one or two genuinely discriminating questions, done. Cover letters are a tradition that selects for stamina, not talent. If you want to know how someone thinks, ask one specific question — "Tell us about a thing you shipped that you're still proud of, and what you'd do differently" — and cap it at 300 words.
• State the process. How many stages, who they'll meet, whether there's a take-home, and how long it all takes. Ambiguity about process reads as either disorganisation or disrespect, and senior candidates correctly treat both as a preview of employment.
• Confirm instantly, follow up on a date. An auto-acknowledgement that commits to a response by a named weekday. "We reply to every application by Friday fortnight" is a promise you must keep, which is exactly why it works as a filter — it proves the operational machinery exists.

One more craft note: every open role deserves its own page with its own URL, real typography and the same design care as your services pages. A job ad rendered as a grey ATS iframe inside your beautiful site tells candidates the role is a ticket in someone else's queue. We wrote about treating the job ad itself as a shareable artifact — if your own team wouldn't share it, neither will anyone else's.

Kill the clichés, keep the truth

A brief audit list. If your careers page contains any of these, edit:

• Ping-pong tables and beer fridges. Perks-as-personality reads as compensation for something. Also, the people you want have outgrown free snacks as a decision input.
• "Fast-paced environment." Means unclear priorities. Say what the pace is: "We ship weekly and demo every Friday, which means feedback is frequent and scope is honest."
• "We're a family." You're not, and candidates know it; a family doesn't do performance reviews. Say what you actually offer: decent work, decent people, decent boundaries.
• Vague values walls. Integrity, excellence, innovation — the acronym-generics. Replace each value with a behaviour: not "we value craft" but "a designer can stop a release if the work isn't right, and has."

Every cliché you cut makes the surviving sentences work harder. The page should sound like the person who'd be the candidate's manager, on a candid day. If your hiring managers wouldn't sign the copy, it isn't copy — it's set dressing.

What the page tells people who never apply

There's a second, quieter audience: every prospective client who checks your careers page before signing. They do it more than you think — a healthy pipeline of thoughtfully advertised roles is quiet proof of a stable business, and the way you treat candidates strongly implies how you'll treat clients. Our approach to client work — small senior squads, weekly demos, shipping in public — only sounds credible because the careers page shows a company run the same way from the inside. Consistency between how you hire and how you sell is itself a trust signal, and inconsistency is a leak.

Key takeaways

• A careers page is a self-selection device. Optimise for precision of applicants, not volume; both the "yes, finally" and the "not for me" are wins.
• Show real shipped work and specific Tuesdays. "Exciting challenges for global brands" filters nobody.
• Publish salary bands or band logic. It's the sharpest, fairest filter you own.
• The application flow is a product demo of your company's respect for time: minimal fields, one discriminating question, a stated process, a dated reply promise.
• Every open role deserves a real page on your own domain, not an ATS iframe.
• Cut the clichés — ping-pong, "fast-paced", "we're a family", generic values — and replace each with a verifiable behaviour.

Frequently asked questions

We're small and hire rarely. Do we still need a careers page? Yes — arguably more than a company with a standing pipeline. An always-on page that says "we're not hiring right now, but here's how we work and what we look for" keeps your next hire warm and tells clients you're stable and intentional. It costs an afternoon.

Won't publishing salary bands hand competitors our compensation data? They already know it, roughly — candidates talk, recruiters share, and band data leaks within weeks. What publishing actually changes is your inbound quality and your internal pay discipline, both in your favour. The secrecy mainly protects unclear pay logic.

How do we handle confidential roles we can't advertise? Post the rest properly and keep the confidential one off the page entirely. A careers page with one role and nineteen stubs looks like a company in distress. The unadvertised hire goes through networks and recruiters anyway; the page doesn't have to carry it.

Should we list "nice-to-haves" on job ads? No. Research on application behaviour has shown for years that long requirements lists disproportionately deter strong candidates who take requirements literally — an effect well-documented across gender lines. If it isn't genuinely required to do the job in month one, it doesn't go on the page. Ambition is not a requirement.