Searching TotalJobs Strategically: When to Broaden Your Filters

You've set the filters perfectly. Location, salary, sector, keywords. The search returns twenty candidates. You read all twenty — properly, in three layers. The right person isn't among them.

Most recruiters respond by refreshing the same search and waiting for new profiles to appear. The smarter move is to question the filters. Because on TotalJobs, the candidate you need is usually in the database already — sitting just outside your search.

Why strict filters fail

TotalJobs matches against what candidates typed into their profiles. Your filters search their words, not their reality. That gap creates three traps:

Title drift. The same job exists under ten names. You're searching "Cloud Security Engineer". The right person calls themselves "DevSecOps Engineer", "Security Architect", or "Infrastructure Security Lead". Same work. Different label. The filter never connects them.

Stale profiles. Good candidates stop updating their profile the moment they're happily employed. Their title still says "Network Engineer" — but their last three years were cloud security. The skills are there, buried in a role description written in 2021. Search by title and you never see them.

Phrasing. Two people do the same job and describe it differently. One writes "Azure security". Another writes "hardened Azure workloads". One matches your keywords. The other doesn't. The database can't tell you they're the same person.

The trap is comfortable because it's invisible. The search worked — it returned results. What it didn't return doesn't show up anywhere.

What a bad search actually costs

Every CV you download on TotalJobs costs money. That's the visible cost — and it makes people cautious about broadening, understandably.

But count the other side. One missed candidate can mean a role unfilled for another three weeks — or filled by a competitor. If broadening costs you forty extra downloads and finds you one candidate who gets placed, the maths isn't close.

The discipline isn't don't spend on downloads. It's spend on the right downloads: candidates you haven't seen before, searched for deliberately.

When to broaden — the four signals

Broadening isn't the default. It's a response to signals:

No signal, no broadening. If the strict search gives you thirty relevant CVs, stop searching and start reading. Broadening without a reason just buys you a bigger pile of the same problem.

The widening ladder

When you do broaden, do it one step at a time — a ladder, not a flood. Relax everything at once and you get 900 results and learn nothing about which filter was hiding your candidates.

Step 1 — Broaden the title. The single biggest win. For "Cloud Security Engineer", search adjacent titles one at a time: DevSecOps Engineer, Security Architect, Infrastructure Security Lead, Platform Engineer (security). Each title is its own search, its own result list.

Step 2 — Swap keywords for skills. If titles aren't finding them, search the work itself: "Azure security", "SIEM", "infrastructure hardening", "ISO 27001".

Step 3 — Search the outcome. The strongest candidates describe what they achieved: "migrated to Azure", "built a SOC", "led a zero-trust rollout". Outcome searches surface people who do the work but never list the buzzword.

Step 4 — Loosen location before salary. A 45-minute commute difference is a conversation, not a dealbreaker. Candidates answer ads outside their stated radius all the time. Widen by ten miles and see what appears.

Step 5 — Loosen salary last. ±10% catches candidates who've grown past their listed figure. Do this only when the other steps have run dry — it adds the most noise.

At every step, note what the change produced. That's the next habit.

Deduplicate before you download

Broadened searches overlap. The wider the net, the more CVs you've already seen resurface — and on TotalJobs, paying twice for the same CV is the one cost that's never justified.

Before each download batch:

1. Keep a master list. A simple spreadsheet of every candidate you've downloaded this year — name, title, date, which role.
2. Check the batch against the list. Ten minutes per search. Names and current employers are usually enough.
3. Only download what's new. If a familiar name appears with an updated profile, download it once — not every search that surfaces it.

Over a month of broadened searching, dedupe is the difference between paying for 200 CVs and paying for 140 — with the same shortlist quality at the end.

The search log — your compounding asset

The real skill isn't any single search. It's remembering what worked last time, so each role starts from a better place than the last.

Keep one line per search:

After five roles, your log is your search strategy for your market. You'll know which titles your candidates use, which radius actually works, and which searches only produce duplicates. You won't be guessing — you'll be compounding.

Monday morning

• Take one live role. Run your current search. Note results, then broaden the title only. Compare
• Search the role's core skill instead of its title. Read the five best CVs the keyword search would have missed
• Start the search log — one line per search, from today
• Set up the master candidate list and check your next download batch against it

---

Searching strategically isn't about searching more. It's about knowing when your filters are lying to you, broadening deliberately, and never paying twice for the same CV. The candidates are already in the database — the ones you haven't seen are the ones your filters never met.