Inbound recruiting is the part of hiring where candidates come to you: they find the job on a board, on Google, on your careers page or in a Telegram channel, and they apply. Outbound recruiting is the opposite — you find them and write first. Most teams run both, and most teams run inbound badly: the same role is posted on five boards, applications arrive in five inboxes, and a recruiter copies CVs into a spreadsheet at 6 pm. This guide defines inbound recruiting, compares it with outbound, and shows how to set it up so every application from every board lands in one pipeline, screened, deduplicated and ready to work.

What Is Inbound Recruiting?

Inbound recruiting is the set of channels and processes through which candidates apply to you rather than being approached. It covers:

  • Job boards and aggregators — Indeed, LinkedIn, national boards, Jooble, Google for Jobs
  • Your own job page or careers site — the page Google indexes and candidates share
  • Employer brand and content — the reason a candidate clicks your listing over the next one
  • Referrals — an employee sends someone your way; still inbound, because the candidate applies
  • Community channels — Telegram and Slack job channels, Hacker News threads, university boards

The term borrows from inbound marketing: build something people find, make it easy to respond, and handle the responses well. In recruiting the "handling" is where the value is won or lost.

Inbound vs Outbound Recruiting

Inbound recruiting Outbound recruiting (sourcing)
Who moves firstThe candidate appliesThe recruiter writes first
Who you reachActive job seekersPassive candidates who are not looking
Cost per candidateLow — often free boards, high volumeHigher — search tools, contact data, recruiter time
Quality per candidateVariable; many unqualified applicationsHigh; each contact is chosen
Best forMid-level, high-volume, well-known rolesSenior, niche, hard-to-fill roles
Main failure modeApplications scattered across boards and inboxesLow reply rates from generic outreach
Where it ends upThe same pipeline — one candidate, one profile, one stage per job

Referrals show why the two are not rivals. The most-cited source-of-hire study, SilkRoad's report summarised by SHRM, found referrals produced over 30 % of all hires while job boards produced the majority of external hires — and that data is from 2016, before Google for Jobs existed. Boards bring the volume; referrals and sourcing bring the conversion. A team that only runs one lane leaves half its hires on the table.

Why Inbound Goes Wrong: Five Inboxes, One Spreadsheet

The typical setup for a small team or agency in 2026:

  1. The recruiter writes the job once and pastes it into Indeed, LinkedIn, a national board, a niche board and a Telegram channel.
  2. Each board sends applications to its own inbox, in its own format — Indeed's e-mails, LinkedIn's dashboard, the national board's PDF attachments, Telegram's "hi, here is my CV" messages.
  3. The recruiter copies each applicant into a spreadsheet or an ATS by hand. Some are copied twice; some not at all.
  4. The same person applies on two boards and becomes two rows.
  5. Screening is a first read of every CV — 80 to 200 per role — by one person.
  6. Nobody knows which board the hire came from, so next quarter the same five boards get the same job.

None of these is a people problem. They are all intake problems, and intake is a systems question.

Setting Up Inbound Properly: One Pipeline for Every Board

1. Publish one canonical job page

Every role gets one public page with the full description, salary, location and a canonical URL. That page is what Google for Jobs indexes (via JobPosting structured data), what you link from every board that allows an external apply link, and what candidates forward to each other. An ATS that hosts the page and writes the schema for you removes the developer from the loop — the Google for Jobs how-to covers what the schema must contain.

2. Distribute from the page, not by copy-paste

Four mechanisms cover nearly every board:

  • Structured data for Google for Jobs — free, unlimited, no submission.
  • An XML feed for aggregators such as Jooble (66 country sites) and Adzuna — submitted once, crawled daily.
  • A partner API where a board offers one — Djinni in Ukraine pushes each application to the ATS.
  • An apply e-mail address for everything else — a unique address per job, pasted into the board's "send applications to" field, so the board's e-mails become applications without anyone reading the inbox.

The free job posting sites guide lists which boards are free and which mechanism each one supports.

3. Parse and deduplicate on the way in

Whatever the channel, the application should arrive as a structured record: name, e-mail, phone, LinkedIn, the CV as a file and as searchable text. When the board hides the applicant's e-mail (several do), the details are extracted from the CV and the application is flagged for review rather than dropped. And before a record is created, it is matched against the candidates you already have — the same person applying to two jobs, or through two boards, is one profile with two applications, not two profiles.

4. Screen every application the same way

The first read of 200 CVs is the bottleneck. AI screening does that read against the specific job: a fit score, a verdict (strong fit, possible fit, weak fit, not a fit), the reasons, and any red flags, per applicant, the moment the application lands. The recruiter starts with the strong fits instead of the alphabet. Keep the human in the decision — the score orders the queue, it does not reject anyone.

5. Put inbound and outbound on the same board

The candidate who applied on Indeed and the candidate you sourced on LinkedIn belong in the same Kanban column for the same job, with the same stages, the same interview feedback and the same client report. Two pipelines means two truths about the search.

6. Measure source of hire

Every application carries its origin — form, e-mail from which board, Djinni, manual upload. Three roles later you know that one board sends 40 % of applications and 5 % of interviews, and another sends a tenth of the volume and half the hires. Post accordingly.

What This Looks Like in MindHunt AI

MindHunt AI was built around both lanes — search and outreach for outbound, and a job board with intake for inbound — so the setup above is the default rather than an integration project:

  • Public job page on a dedicated host with JobPosting schema, a sitemap, 30-day expiry with explicit renewal and a 410 on unpublish; a Google for Jobs toggle and a Jooble feed toggle per position, with eligibility checks before either sees the job.
  • Djinni integration — link a position to a Djinni vacancy; applications arrive by webhook and a three-hourly poll, with CV, cover letter and answers.
  • Apply e-mail address per position — apply-…@apply.mindhuntai.com, rotatable, parsing PDF, DOC and DOCX up to 5 MB, extracting identity from the CV, flagging applications that need review.
  • Deduplication against existing candidates on every intake, with the application attached to the existing profile.
  • AI screening on arrival — score, verdict, reasons, red flags — metered as one AI credit per evaluation on every plan.
  • One Kanban pipeline for inbound and sourced candidates, with source recorded per application and a shareable analytics link for clients or hiring managers.

The job board, distribution, apply e-mail and screening are included on every plan, including Free.

Inbound Recruiting Strategy: What to Do This Quarter

  1. Audit where applications arrive today. List every board and channel and where its applicants end up. Anything that ends in an inbox is a leak.
  2. Publish one canonical page per role with a full description and salary; turn on Google for Jobs and the Jooble feed.
  3. Give every board an apply address. Post on the boards you already use, route the applications to the pipeline, and stop copying.
  4. Turn on screening and review the strong fits first. Time the first read before and after.
  5. Read source of hire after three roles and drop the boards that only send noise.
  6. Keep sourcing. Inbound fills the mid-level roles; the senior ones still need outbound.

Conclusion

Inbound recruiting is not a channel choice; it is an intake design. Get every application from every board into one pipeline, screened and deduplicated on arrival, and the boards stop being a chore and start being a source you can measure. Then run outbound on top for the roles that never get applied to. Both lanes, one board.

Every Application, One Pipeline

MindHunt AI takes applications from your job page, Google, Jooble, Djinni and any board by e-mail — screened, deduplicated and on the same Kanban board as the candidates you source. Included on every plan.

Start Free →