role-shortlist
The rule: a role is judged from its posting, or not at all. A careers page lists forty titles. The agent's habit is to rank them from the titles, the department and what such jobs usually ask for, and a ranking built that way looks exactly like one built from the postings. "Senior Care Coordinator" may require a nursing registration; "Data Analyst" may be a night shift in another country. So each role is ranked only after its own posting text has been read. A role whose posting you couldn't open, or that is only a title in a list, goes under Not read, with no score, no guess and no reason to apply.
Two things follow from the rule:
- A screening requirement the person doesn't meet takes a role out. A licence or registration, a degree the posting says is required, a minimum number of years, the right to work in a country, a location or shift, a clearance, a language. One of those unmet outweighs everything else that fits, so the role goes under Skip with that requirement named, however good the rest looks. Only the posting decides what is required: an item it calls preferred, desirable, a plus or nice to have never takes a role out.
- One role is one role. The same job posted in three cities, or reposted with a new reference number, is one entry with its locations listed. A posting marked closed, or past its closing date, is noted and not ranked.
How to respond
Gather the postings. Use what you were given: saved pages, a pasted list, an export, a folder of files. When you were given a careers-page link and can open it, read the listing and then each posting. When you can't open something, say so once and ask for the text or saved pages; never fill it in from what you know about the employer.
Read the person's evidence. Their resume, and any other file of theirs that sits beside it or that they point to. Nothing is credited because people in that line of work usually have it. Note any constraint they stated themselves: where they can work, hours, salary, the kind of role they want.
Check each posting for what could screen them out first. For every role, find the requirements the posting makes a condition: what it calls required, essential or a must, and the facts of the job itself (where it is, the hours or shift, a licence the work needs). Mark whether the person's material meets them. Any unmet one sends the role to Skip, named in a few words: "requires HCPC registration". An item the posting calls preferred, desirable or a plus is not one of these, even a degree or a licence; it is a gap to weigh in step 4, and the role stays in.
Rank the rest from the posting's own requirements. For each remaining role, compare the required and preferred items with the person's evidence, and say in one line why it fits and what is missing. Use the posting's wording for requirements and the person's for evidence. Similar is not the same: a named system, qualification or setting the posting requires is met only if the person's material names it.
Give the shortlist, answer first. Open with the two or three roles worth applying for and why, in a sentence or two. Then the roles under these groups, using only the groups that have a role in them. A heading with nothing under it, or with "none", is not shown: when every posting was read and none is closed, there is no Not read or Closed group.
- Apply: roles where nothing screening is unmet and most of what's required is met.
- Maybe: roles worth applying for if one named question has the right answer ("if your forklift licence is current").
- Skip: each with the requirement that rules it out.
- Not read: each with why (link wouldn't open, title only, page was empty).
- Closed or duplicate: one line each.
One line per role. Every role you were given appears exactly once, so the person can see nothing was dropped.
Close with what to do next, in two or three lines: which role to check in full first, the one or two questions whose answers would move a role between groups, and which unread postings to fetch.
Fit the size and format they asked for. "Just the top two" gets two, each with its reason and anything to check first, then the rest in a line or two: which were ruled out and by what, and any that couldn't be read. No groups and no headings; the person asked for two names, not a sorted list. A list for a spreadsheet gets one row per role. The whole answer is in the reply unless they ask for a file.
Deliver from what you have. With postings and a few lines about the person, shortlist against those and say a resume would settle the rest. When each role is only a line or two, say the picks rest on those lines and the full postings come next. With a resume and no postings, ask for the postings in one line.
Quality bar
- No role is ranked without its posting text having been read. Unread roles are listed as unread, with no verdict.
- A role with an unmet screening requirement is never under Apply, and the requirement is named. An item the posting calls preferred is never treated as one.
- Every role given appears exactly once; duplicates are merged, closed ones are noted.
- Every "fits" rests on the person's own material, and a similar thing is not counted as the named one.
- The answer opens the reply, and the size is the one asked for, with no empty groups.
When to use this skill
- ✅ "Here's the careers page export for this company — which should I go for?"
- ✅ "I've saved twelve postings in this folder. Shortlist them against my CV."
- ✅ Narrowing a long list of openings to the few worth a full application
When NOT to use this skill
- ❌ A full, requirement-by-requirement check of one posting — use
job-fit-analysison the role this shortlist puts first - ❌ Rewriting the resume for a role — use
resume-tailor - ❌ Searching the internet for jobs to apply for — this reads the postings you have or point to
Anti-patterns to avoid
- ❌ Ranking from titles. "Operations Lead sounds like a good fit" with the posting unread.
- ❌ Guessing an unread posting from what the employer or the job title usually means.
- ❌ A strong fit over an unmet licence. Screening requirements decide first.
- ❌ A preferred item as a requirement. "Degree preferred" is a gap to weigh, not a reason to skip.
- ❌ Empty groups. A "Not read: none" heading, or the full five groups for a top-two answer.
- ❌ Counting a duplicate twice, or ranking a closed posting.
- ❌ Dropping roles silently. A list that covers 9 of 12 postings without saying so.
- ❌ Crediting the usual. "As a nurse you'll have used Epic" is an invention.
- ❌ Percentages and scores. "82% match" hides which requirement is the problem.
- ❌ Judging the person. No remarks on age, gaps, family, health or anything an employer may not lawfully weigh.