Inbound Application

Hiring ran on acquaintance for a very long time. A seat opened, you asked the team whether anyone knew someone, and if that came up empty you widened the circle to suppliers, classmates, former colleagues. What this method sorted on was position rather than ability. Anyone not connected to somebody at that company never learned the seat existed, and the company could not see who was out there beyond its own network.

Job boards and public listings lowered that wall. Outside observers could finally see what roles a company was filling and on what terms, and someone with no connection at all could submit an application. The change ran the other way too. Finding one person went from asking ten people a question to posting once and having strangers arrive continuously.

Within hiring, the ways of meeting candidates split into waiting and going out to find them, and inbound application is the standard form of waiting. How much of the other routes you need is decided by watching how well this one turns. If a posting has been live for three weeks, five people applied, and none of them cleared the resume round, that's the signal to shift weight toward going out and finding people.

Publish the posting, collect the applications in one place, and judge each one against the requirements you wrote down.

1. Write the posting. A job description (JD) laying out the work and the experience required is the starting point. It's an advertisement and an agreement at once. The three lines under required qualifications become the three things checked at interview, so a vague document brings vague applicants.
2. Put it in several places. A company careers page alone is rare; postings usually go up on hiring platforms and role-specific communities as well. Tagging where each application came from tells you at the next opening which channel actually worked, and which one you can stop paying for.
3. Gather applications in one place. Taking them by email means some get missed and interviewers end up reading different files. An applicant tracking system stacks them into one list and shows which stage every candidate is at.
4. Filter with resume screening. The question here is not how impressive someone is but whether anything overlaps with what the posting asked for. Shift the bar as you go and the same resume gets judged differently depending on who reads it, which shows up later as interviewers disagreeing about what the role even is.
5. Pass people to interviews, and keep the rest. Candidates who came close go into the talent pool, so that when the same seat reopens in six months nobody starts from scratch.

All of that elapsed time lands in time to hire, the span from posting to a signed start date. For a role run on inbound applications alone, that number is bound to how fast applicants accumulate.

It works best at companies people have heard of. If you build a product that's already familiar, a single posting draws hundreds of applications. Post the identical role at a company nobody knows and you get five in three weeks. The difference isn't the quality of the writing — it's how visible the company is, which is the argument for building employer branding well before you need it.

It also fits roles where several people are hired at once. Filling three or four seats in support or sales goes much faster by opening a posting and filtering than by chasing candidates one at a time. Entry-level roles and positions asking for under three years of experience usually draw enough volume to be solved this way too, which is why most teams reserve their scarce outreach time for the seats above that line.

The roles it fails on are just as clear: fields where few people exist at all, and senior people who aren't looking. A data platform engineer with ten years behind them does not browse job sites. Postings for seats like that can sit for six months without a single application, and they get filled by reaching out first. Companies that haven't launched publicly also struggle here, because there's so little they can put in the posting — no product to name, no customers to point at, and often no salary band they're willing to publish.

"Let's run this one on inbound only. This role gets plenty of applications."

No need to go out and find anyone; the posting alone should fill it.

"Three weeks up and five applicants. We need to add sourcing."

Waiting isn't collecting candidates, so the route has to change.

"Two hundred applications and three cleared screening. Time to revisit the posting."

The problem isn't volume but fit, and the cause sits in the job description.

When Pagedeck opened two sales seats, Grace started with inbound. The posting went on the careers page and two platforms, and ninety applications arrived in two weeks. Four of them cleared the resume round. The posting hadn't asked for any industry background, so people came in from everywhere.

Sofia rewrote it and cut the required qualifications down to two lines: experience selling a tool bought by teams, and experience carrying a contract-size conversation directly. Over the next two weeks applications dropped by half, to forty — and eleven cleared screening. Mia's summary was that the dial you actually control in inbound hiring isn't the number of applications, it's the sentences in the posting.

The most common mistake is reading a high application count as progress. The number is visible, it feels like an outcome, and it gives whoever posted the role something to report. But the count that matters is how many reached an interview. A posting with three passes out of two hundred is worse than one with ten out of forty. Treat the first as success and the team starts widening requirements to pull the number up, which multiplies the reading time and changes nothing else. Worse, the candidates who did fit wait longer for an answer while someone works through the pile, and a few of them accept something else before the reply arrives.

The second is assuming a posting fills itself once it's up. The continuous-arrival part is real, but only for a company that's already visible. An unknown company can leave the same posting live while two months pass and nothing happens at all. Left uncorrected, the team sits watching an empty inbox on a seat it could have filled, and loses the candidates another route would have reached in the meantime.