Why your job posts get no applicants (and what to run instead)

You posted the role, waited two weeks, and got a handful of applicants who were not right. So you posted it again.

The problem is usually not the role and not the pay. It is that a job post is a passive document sitting where only active jobseekers look, competing with hundreds of identical documents.

The people worth hiring are not on job boards

The strongest candidate for most roles is currently employed, reasonably content, and not browsing listings. They are not going to find your post, because they are not looking.

They are, however, on Facebook and Instagram.

This is the entire case for treating recruitment as advertising. Paid social reaches people based on who they are, not on whether they happen to be job-hunting this week. That pool is much larger, and generally stronger, than the pool of people actively applying.

Write it as an offer, not a requirements list

Most job posts are a list of demands. Five years of experience. Must be willing to work onsite. Must be a team player. Must have own laptop.

Nothing in that tells a good candidate why they would leave a job they already have.

Flip the structure. Lead with what the role offers: the pay band, the growth, the team, the specific thing that makes it better than where they are now. Put the requirements after, and keep them to what actually matters.

Put the pay in the ad

This is the single highest-impact change most Philippine employers can make, and the most resisted.

Omitting the salary does not protect you. It guarantees applications from people whose expectations do not match, and it filters out strong candidates who will not spend an evening applying to find out. You then discover the mismatch in the interview, having wasted everyone’s time.

Publishing a band costs you some negotiating flexibility. It buys you a shortlist that is already aligned on the most common dealbreaker.

The same applies to shift, location and onsite requirements. Everything you conceal, you will discover later at greater cost.

Screen before the interview, not during

Volume is only useful if it is filtered. A few qualifying questions in the application flow — experience, availability, location, salary expectation — mean your hiring manager opens a shortlist rather than a mailing list.

The goal is not the most applications. It is the fewest interviews needed per hire.

Speed decides more hires than you think

Candidate interest decays in hours, not days. Someone who applies on Tuesday night and hears nothing until the following Monday has usually moved on — often to an employer who was simply faster, not better.

At minimum: acknowledge every application immediately, tell them what happens next and when, and make scheduling easy. Automating that first response is straightforward, and it changes outcomes more than another round of sourcing.

Measure cost per hire, not applications

Applications are a vanity metric in recruitment exactly as reach is in advertising.

Track:

• Cost per qualified applicant
• Interview attendance rate
• Offer acceptance rate
• Total cost per hire

Compare that last number against what an agency placement fee would have cost you. For volume and mid-level roles — sales, agents, service staff, clinic and support teams — running your own campaigns is frequently cheaper per hire and gives you a candidate pool you keep rather than rent.

Where this does not apply

Very senior or highly specialised searches are usually still better served by direct headhunting. The pool is small enough that reaching it individually beats broadcasting to it.

For everything below that, the job post is not failing because it was worded badly. It is failing because it was published and abandoned in the one place where only people already looking will ever see it.