Forty Applications, Five Interviews: What the Screening Pile Tells You About a Job Board

If you use this site, you already have a habit most hiring managers do not: you test something with a throwaway before you hand it anything real. You would not sign up for a strange service with your main inbox, and you would not trust a download page you had not read. Hiring deserves the same treatment, except the test runs in the other direction. The applicants are testing you, and the pile they send back is the test result. This post is about the pile.

Take one imaginary vacancy, because the shape matters more than any particular business. A small hardware shop in a mid-size town posts one job: shop assistant, full-time, $38,000 to $44,000 a year, on-site, must be able to lift stock and work Saturdays. Three days after the posting goes live, forty applications have arrived. The owner has a shop to run, one pair of hands to hire, and about three hours a week to spend choosing. The question is not whether a job board can collect forty applications. Any board can do that. The question is whether the board helps the owner turn forty into five interviews without losing the best candidate somewhere in the middle. That is what applicant tracking is actually for, and it is what this post tests, one filter at a time.

The product behind the discussion is JobDesk Pro, a job board script listed on codester.shop as a complete job board script with salary-first listings, built on Laravel 13, at $29 for a Regular License as an instant ZIP. That is the shop's own description, quoted as the product's own claim. Everything that follows is about how to screen a pile well on a board built that way, not a tour of an admin panel this run did not inspect. The numbers in the pile are illustrative. The lessons are the ones that survive contact with real applicants.

The pile arrives faster than you expect

Forty applications in three days feels like good news, and it is, but only in the way a full inbox feels like good news. Most of the pile is not a decision. It is noise wearing the shape of a decision, and the first job of screening is to admit how much of it is noise without feeling guilty about it. Out of the illustrative forty, a realistic split looks like this: about eight applications are from people who never did anything like this job and never will, six are from people in the wrong city who did not read the location line, four are duplicates or near-duplicates from people who applied twice, and three are missing the one thing you asked for — a phone number, a CV, a yes-or-no answer to the Saturday question. That leaves nineteen applications worth a proper read, and that is before a single filter has run. Half the pile is gone, and nothing has been judged yet.

Here is the first opinion, plainly stated: the speed of the pile is the problem, not the size of it. Forty applications is not a lot. What makes the pile hard is that it all arrives at once, while the shop is open and customers are at the counter. Screening fails when it is treated as a weekend task, because by the weekend the best applicants have heard from someone faster. The board's job is to make the first pass take twenty minutes, not two hours, and to make it possible on a Tuesday between customers. If a board cannot do that — if the first pass needs a quiet afternoon and a spreadsheet — then the pile will sit, and sitting is how good applicants get lost.

My earlier post in this series ran the whole first posting as a five-day diary, from writing the vacancy to closing it or rewriting it. This post picks up where that diary's Day 2 left off, and stays there: the pile is in, and now what.

First pass: completeness, duplicates, and the two-minute cull

Before any filter, run the cull, and run it by hand. It takes two minutes per ten applications once you know what you are looking for, and it is the only part of screening that should never be automated away, because it is where you learn what your posting actually attracted.

Completeness first. An application missing its phone number is not a bad application. It is an unfinished one, and unfinished applications have a specific smell: the applicant applied in a hurry, to a dozen jobs at once, and yours was one of the dozen. That is not a moral judgement. It is a practical one. A person who applies to twelve jobs in an evening is a person who will take the first offer that calls back, and that might be yours, but it might also be the shop down the road that called first. Put the incomplete applications in their own pile. Do not delete them. Read them last, if you have time, because one of them might be the best candidate having a bad evening. But do not start with them.

Duplicates second. Four of the illustrative forty applied twice, usually because the board did not show them a confirmation, or because they were not sure the first one went through. This is a board problem as much as an applicant problem: if your board makes people apply twice, it is also making some people give up after the first try. Keep the newest application, drop the older one, and note the count. If more than one in ten applications is a duplicate, the apply button is lying to people about whether it worked, and that is a fix worth making before the next posting.

The two-minute cull is the only stage where speed is a virtue. Everything after it should slow down, because everything after it is a judgement about a person, not a check on a form.

Filter one: the hard facts

Now the filters start, and the first filter is the only one that should be strict. Filter on the hard facts: location, employment type, and the salary band the applicant will accept. These are facts, not opinions. Either the applicant lives near enough to work Saturdays, or they do not. Either they want full-time, or they do not. Either the salary band works for them, or it does not. A filter on a hard fact is a kindness to both sides, because it ends a process that was never going to close.

In the illustrative pile, the location filter removes six, the employment-type filter removes three more, and the salary filter removes two who wanted substantially more than the top of the band. Nineteen becomes eight. That feels brutal, and it should, because eleven people just left the process. But read it the other way: eleven people were saved from a three-stage interview process for a job in a town they do not live in, at hours they do not want, for less than they need. A salary-first board makes this filter possible at all, which is the point of putting the number on the listing in the first place — my earlier post in this series read one salary-first listing line by line from the seeker's side, and the salary line is what lets a seeker filter themselves out before they ever reach your pile. When they do not filter themselves out, your hard-facts filter does it for them, and the earlier it happens, the cheaper it is for everyone.

One warning about the salary filter, and it matters. Do not filter on the top of your band. Filter on the bottom. An applicant who says they need $46,000 for a role banded $38,000 to $44,000 is not necessarily out — they might take $44,000 for the right hours. An applicant who says they need $60,000 is out, and no cover letter changes the arithmetic. Set the salary filter at a number that means "this person will walk away when they hear the offer," not at a number that means "this person asked for more than I hoped." The first is a fact. The second is a negotiation you have not had yet.

Filter two: the must-haves — and the good candidate they hide

Eight applications remain, and this is where screening usually goes wrong, because the next filter is not a fact. It is a judgement dressed as a fact. The posting said three must-haves: can lift stock, can work Saturdays, has done retail or warehouse work before. Filter on those, and the pile goes from eight to five. Neat. Tidy. And wrong, in exactly the way a tidy filter is usually wrong.

Because one of the three people filtered out here is the best candidate in the pile. In the illustrative version, she has never worked retail. She spent four years running the stockroom of a school kitchen — lifting, counting, ordering, working Saturdays during term, dealing with suppliers who delivered late and fridges that broke on Friday. She has done every part of this job under a different job title, and the must-have filter threw her out because the filter was looking for the words "retail" and "warehouse" and her CV says "catering." The filter did its job. The job was badly specified.

This is the honest catch about applicant tracking, and it is the reason this post is a test rather than a manual. Every filter hides someone good. A location filter hides the applicant who would have moved. An experience filter hides the applicant whose experience is real but titled differently. A salary filter hides the applicant who would have taken less for the right hours. The filter is not the mistake. The mistake is running it once and trusting the result. The fix is small and it is the whole discipline of this stage: after every filter, skim the rejected pile's headlines. Not the full CVs, just the headlines — the last job title, the town, one line of the cover letter. If you find one name that does not belong in the reject pile, your filter was too tight, and you have just learned something about your own must-haves before it cost you a hire.

So the eight becomes six, not five. The catering candidate comes back in, with a note on her file that says why: "stockroom, lifting, Saturdays, suppliers — different title, same Tuesday." A shortlist with one line per name — why this person is still here — is a decision you can re-make, and a decision you can explain to a business partner who asks why you picked these six.

The shortlist call: five names, one honest question

Six names, five interview slots, one shop, one pair of hands. This is the shortlist call, and it is the only stage where gut feeling is allowed a vote, because the filters have done everything they can do and the remaining differences are human.

Read each of the six against the Tuesday, not against each other. That is the discipline from the first-posting diary, and it is worth repeating here because it is the easiest one to break under pressure. The question is never "who is the best applicant?" It is "who can do this Tuesday, in this place, at this pay, starting soon?" The Tuesday for this vacancy is specific: open the shop, lift the morning delivery onto the shelves, serve customers who want advice rather than a transaction, cover the counter while the owner is on a supplier call, and do it again on Saturday. A beautiful CV from someone who has never done that Tuesday is worth less than a plain CV from someone who has done it for two years.

So one of the six goes, and the reason should be written down in one sentence, the same way the reason for keeping the catering candidate was written down. Not "not a fit" — that phrase is a shrug wearing a suit. Something specific: "three jobs in eighteen months, no Saturday work in any of them, and the cover letter is addressed to a different shop." If you cannot write the sentence, you do not have a reason yet, and the person should stay in.

Five interviews. That is the pile's answer, and it is a good one: five people who can do the Tuesday, in the right town, at a pay that works, who applied properly and got read properly. The board's contribution to this outcome is not glamorous. It collected the pile, it held the filters, it kept the notes, it let the owner re-run a filter in minutes when the first run was too tight. That is what applicant tracking means when it is working: not a dashboard, not a pipeline graphic, but a pile that can be sorted, re-sorted, and explained, by one person, between customers.

The replies nobody sends

Five interviews are booked. Thirty-five people are not getting one, and most of them will hear nothing. That is the normal outcome, and it is a mistake, because the rejected thirty-five are the ones who will talk about the shop in town.

The arithmetic is simple and it favours replying. A short, honest rejection — "we went with someone whose recent experience matches this role more closely, thank you for applying, we kept your details for the next opening" — costs two minutes and buys a reputation. Silence costs nothing today and costs you applicants for the next vacancy, because the people you ghosted are the people who tell their friends not to bother. A small business that replies to every applicant has a hiring advantage that no board feature can replicate, because most employers do not do it. Applicants remember the employer who replied. They apply again. They tell a friend.

The board can help here, and this is the part of applicant tracking that buyers should test hardest: can you send a kind rejection to the whole rejected pile in one action, with each person's name on it, and can you tell afterwards who got one? If the answer is yes, the two minutes is real. If the answer is no — if each rejection has to be written by hand, one at a time — then the rejections will not get sent, and the silence will cost you the next posting's applicants. Test this before you buy, not after your first pile.

What the pile says about the board

A pile is a test of a board in a way a demo never is, because a demo shows you the happy path and a pile shows you the Tuesday. Here is what to judge a job board script on, after running a pile through it, and the order matters.

First, can the first pass be done in twenty minutes, on a phone, between customers? If the applications list needs a desktop and a quiet afternoon, the pile will sit, and sitting is how good applicants get lost.

Second, can a filter be loosened and re-run in minutes, with the rejected pile still there to skim? If a filter is a one-way door — once rejected, gone — then the catering candidate stays gone, and you will never know she existed. The re-run is the feature. The first run is just a guess.

Third, can you keep one line of notes per applicant, in the applicant's own words where it matters, and can you still read those notes on Friday? A shortlist decided from memory is a shortlist decided by charm, and charm is a bad hiring manager.

Fourth, can you reply to everyone, including the rejections, without leaving the board? If the reply step lives in a separate email client, it will not happen, and the silence will cost you the next posting.

Fifth, does the salary stay visible through the whole process — on the listing, in the filter, in the shortlist? A salary-first board that hides the number once the applications arrive has given up its one advantage at the exact moment it matters most, which is when you are deciding whether a candidate will accept the offer.

Judge JobDesk Pro, or any board in this class, against those five, in that order. The shop listing for JobDesk Pro describes a complete job board script with salary-first listings on Laravel 13 at $29 for a Regular License as an instant ZIP, and that is the shape to test against the five questions: does the shape hold when the pile arrives, or does it only hold in the sales copy? I have not inspected the script's code or a live demo in this run, and this post does not pretend otherwise. What it does is hand you the test, so you can run it yourself before you buy and know what you are looking at when the pile lands.

The same test-first method runs through this whole series — most recently in the AI tools comparison test, where a directory's comparison page was run against a real $20-a-month decision instead of being trusted on its numbers. Test the tool against a real decision, report where it holds and where it does not. That is the habit this site's readers already have: they test a service with a throwaway before trusting it with something real, and a job board is no exception.

Who should skip the screening test

Skip this test if you are hiring at volume, with a recruiter and a pipeline, because your problem is throughput, not one pile, and a careful six-person shortlist will feel slow. Skip it if the vacancy is genuinely urgent and you already know the person you want — call them. And skip the salary-first format itself if you cannot publish a real range: a board that puts salary first only helps when the salary is honest, and a vague range on a salary-first board reads worse than no range at all, because the format promises candour the number does not deliver.

For everyone else — a shop, a clinic, a small agency hiring its next pair of hands — the screening test is the cheapest hiring education available, because the tuition is one pile and the lessons are yours to keep. Forty applications, five interviews, one hire, and a rejected pile that still likes you enough to apply again. That is what a good board does. The rest is just a list.

FAQ

How many applications should one vacancy get?

There is no right number, and anyone who quotes one is selling you something. The illustrative pile in this post is forty in three days for one shop vacancy, which is a healthy response for a small business posting with the salary on it. Fewer than ten usually means the posting is not reaching people. More than a hundred usually means the posting is too broad, and the screening time will eat the saving. Judge the pile by the qualified rate, not the size: how many of them can do the Tuesday, in the right town, at the pay you can offer.

What is the first filter I should apply?

The hard facts, in this order: location, employment type, salary band. These are facts, not opinions, and filtering on them first is a kindness to both sides. Do not start with experience or CV polish, because those are judgements, and a judgement made before the facts are settled will throw out good candidates for bad reasons.

How do I catch the good candidates my filters reject?

Skim the rejected pile's headlines after every filter — the last job title, the town, one line of the cover letter. If a name does not belong in the reject pile, the filter was too tight. The catering candidate in this post was caught exactly that way: her experience was real but titled differently, and the filter was looking for the wrong words. A filter you never re-check is a prejudice with a settings page.

Should I really reply to rejected applicants?

Yes. It is the highest-return two minutes in the whole process. Rejected applicants who got a kind reply apply again, recommend you, and cost you nothing. Rejected applicants who got silence remember the silence longer than they remember the job, and they are the ones your next posting needs. Keep a template, keep it human — one sentence about why, one sentence of thanks — and send it on the day you promised a reply.

Is JobDesk Pro a job board, or software for running one?

Software for running one. JobDesk Pro is listed on codester.shop as a complete job board script with salary-first listings, on Laravel 13, at $29 for a Regular License as an instant ZIP. You buy the script, you run the board, and the listings and applications on it belong to the employers and seekers who use it.

Can I test a job board with a temporary email?

You can test the board as a seeker with one, and you should — sign up, save a job, see what the board sends you, all from an address you can throw away. But do not submit a real job application from an address you cannot open in six weeks. The interview invitation and the offer go to the address you applied from. Test the board with a throwaway if you like; apply with an address you control for the long term. The tool for the test is the one on the homepage, and more tests like this one run every day on the blog.

The one-line check before you interview

Read the shortlist once more, top to bottom, and ask a single question: if I had to hire one of these five tomorrow, with no more information than I have right now, would I be comfortable explaining the choice to the person I did not hire? If the answer is yes, book the interviews. If the answer is no, and one name on the list is there because the CV was pretty rather than because the Tuesday fits, take that name off before the interviews start. A shortlist you can defend is a shortlist you can hire from, and a pile you can explain is a board worth keeping.

*JobDesk Pro is listed on codester.shop as a complete job board script with salary-first listings (Laravel 13), Regular License $29, instant ZIP. The vacancy, the forty applications, and every number in the pile are illustrative examples of how screening runs, not figures from any real business or demo. For the tool this site is built around, start at tempomailusa.com, browse the blog, or see pricing. Related script posts: how to read a salary-first listing before you apply and your first job posting, run as a five-day test.*