The pitch is seductive: a hiring process that runs like a symphony, where sourcing, interviewing, selecting and hiring hand off to each other without a human touching anything. Roles open, candidates appear, the machine sorts them, offers go out, and you watch.

Nobody runs that. Not because the tools are missing, but because the one step you most want to automate, the decision to reject someone, is the step that carries the legal liability, and the tooling does not absorb liability. So here is the honest version of this article: you can automate almost the entire process and none of the judgment. This is which parts, in what order, with what it actually costs, and where the line sits.

The honest answer: automate the motion, not the decision

Sort every task in your hiring process into two buckets. In the first: things where the output is deterministic and a mistake is cheap to reverse. Posting a job to twelve boards, parsing a CV into fields, chasing a hiring manager for feedback, booking a slot, sending an offer PDF, kicking off onboarding. Automate all of it, today, without hesitation.

In the second bucket: things where the output is a judgment about a person and a mistake is expensive, invisible and sometimes illegal. Deciding who is worth a call. Deciding who gets rejected at the sift. Deciding what someone is worth. These can be assisted by software (ranked, shortlisted, summarised) but the moment software makes the call unsupervised, you have not removed the work, you have moved the risk.

The useful mental model: automation buys back the hours between decisions, not the decisions. In a typical requisition the decisions take a few hours in total. The chasing, coordinating and data entry around them take dozens. That is your prize, and it is a big one. It just is not "completely".

Start with the system of record, not the shiny tools

Most people build this backwards. They buy an AI sourcing tool, an AI screener and a scheduling bot, then discover they have four candidate databases that disagree with each other and no way to trigger anything from anything else. Automation is plumbing, and plumbing needs a tank.

The tank is your applicant tracking system. It should hold every candidate record, every stage, every note, and it should be the thing that fires the triggers: candidate moves to "Offered", offer document generates. Candidate marked "Hired", record syncs to your HRIS and onboarding starts. Applicant tracking platforms like Manatal, Recruitee and Breezy HR all do this shape of thing at the small-team end of the market. Pick one, then build everything else around it.

The detail that decides whether your pipeline can be automated at all is not the feature list. It is whether your tier includes API access. This is where ATS vendors quietly separate the advertised price from the automatable price.

Stage 1: sourcing, the most automatable step there is

Sourcing automates well because the output is a list, and a bad list costs you nothing but attention. Job distribution to multiple boards from one post, resume parsing into structured fields, enrichment of a name into a profile, and continuous re-surfacing of candidates already in your database are all safe, mature and worth turning on immediately.

The genuinely underrated one is the last: most teams have thousands of past applicants sitting in the tank and re-run the same expensive top-of-funnel every time a role opens. An automation that matches new requisitions against existing records costs nothing per candidate and is the highest-margin sourcing you will ever do.

Contact data is where sourcing meets a metered wall. Tools like Apollo.io are the standard way to turn a profile into an email address, and the free tier is worth knowing precisely: $0 gets you 900 credits per seat per year, released monthly, which is roughly 75 lookups a month. That is a trial, not a pipeline. Real volume starts at Basic, $49/seat/month billed annually or $65 month-to-month, which grants 30,000 credits per seat per year upfront. Budget for the paid tier or do not build the workflow.

The alternative to assembling this yourself is a tool that does the search, the enrichment and the first message as one step. That is the category HeroHunt.ai sits in, and since we build it, treat the following as what it is: our own product, with the limits stated.

Stage 2: outreach and scheduling, where the hours actually are

Sequenced outreach with automatic follow-ups is table stakes, and follow-ups are where the replies live, so this is genuine value. Two rules keep it from backfiring. Personalisation tokens are not personalisation: a candidate can tell the difference between a merge field and a sentence about their work, and the merge field costs you the reply. And every sequence needs a hard stop on reply, or your automation will follow up on someone who already said yes.

Scheduling is the purest win in the whole stack. Calendar-linked self-booking removes an email thread that averages five or six messages per interview, needs zero judgment, and fails safely. If you automate exactly one thing this quarter, automate this one.

Stage 3: screening, where automation stops paying and starts costing

Here is the wall. Automated screening is the feature every vendor sells hardest and the one with a body of enforcement behind it.

In 2023 the EEOC settled its first AI hiring discrimination case. iTutorGroup had programmed its application software to automatically reject female applicants aged 55 or older and male applicants aged 60 or older. More than 200 qualified applicants were screened out. The company paid $365,000 and accepted EEOC monitoring for at least five years. Note how it was caught: an applicant submitted two identical applications differing only in date of birth, and got an interview only with the younger one. No sophisticated audit. One person noticing.

The bigger signal is Mobley v. Workday (No. 3:23-cv-00770-RFL, N.D. Cal.), which argues that the vendor itself can be on the hook. The court allowed the claims to proceed on the theory that Workday acts as an agent of its client-employers and therefore falls within the definition of "employer" under Title VII, the ADEA and the ADA. It preliminarily certified an age collective in May 2025 covering anyone who applied through the platform since 24 September 2020 aged 40 or over; the opt-in window closed on 7 March 2026 and the case is in discovery, with no merits ruling and no trial date. Nothing has been decided. That is exactly why it matters: the theory that "the software rejected them, not us" survived a motion to dismiss.

The practical takeaway is not "never use AI screening". It is: let it rank and summarise, never let it reject. Keep a human as the only actor who can end a candidacy, log who that was, and you keep the speed while keeping the defence.

Stage 4: offer and onboarding, safely boring

The back end is deterministic and automates cleanly. Offer documents generated from fields already in the ATS (name, title, salary, start date), e-signature, then a "Hired" trigger that syncs the record to your HRIS and opens accounts, orders hardware and books the first-week calendar. This is the least glamorous automation in this article and probably the one with the best return, because the data already exists and re-typing it is pure waste with an error rate attached.

The rules that decide how far you are allowed to go

Three regimes now bound this, and they are the reason "completely" is not on the table.

New York City Local Law 144. If you use an automated employment decision tool on candidates in NYC, you need an independent bias audit every year, a public summary of it, and at least 10 business days of notice to the candidate before the tool is used. Penalties run $500 for a first violation and up to $1,500 per day while a non-compliant tool stays in use, enforced since 5 July 2023. Compliance is, in practice, dismal: a Cornell, Data & Society and Consumer Reports study of 391 employers found only 18 had posted an audit report and 13 a transparency notice, largely because employers decide for themselves whether their tool is in scope.

Illinois HB 3773. From 1 January 2026 the Illinois Human Rights Act covers AI used in recruitment, hiring, promotion, discipline and discharge. It bans discriminatory effect, bans using zip code as a proxy for a protected class, and requires notice whenever AI is used to influence a covered decision, whether or not it discriminates.

The EU AI Act. Recruitment and candidate selection sit in Annex III, the high-risk category. The high-risk obligations were due to bite on 2 August 2026, but the Digital Omnibus deal reached provisionally on 6 May 2026 and confirmed by member states on 13 May pushes standalone Annex III systems to 2 December 2027. Read the caveat carefully: those dates only take legal effect once the Omnibus is formally adopted and published, expected before 2 August 2026. If that slips, the original date applies as written. You have been handed time, probably, not a reprieve.

Every one of these assumes a human is accountable for the outcome. A fully automated pipeline has nobody to point at, which is precisely the state each of these laws was written to prevent.

What a realistic automated pipeline actually looks like

Strip the symphony metaphor and here is the build, in order:

• ATS as the single system of record, on a tier that includes API access.
• One-click distribution to boards, plus parsing and enrichment on intake.
• An automatic rematch of every new role against your existing database before you spend a cent on new sourcing.
• Sequenced outreach with a hard stop on reply.
• Self-service scheduling linked to real calendars.
• AI ranking and summarising at the sift, with a named human making every reject call.
• Stage-triggered offer generation, e-signature, and a "Hired" trigger into HRIS and onboarding.

That is perhaps 80% of the clock and 0% of the judgment, and it is achievable this quarter with tools that already exist. Build it in that order, because each step feeds the next, and a scheduling bot bolted to nothing is just another tab.

The parts that stay human

Persuading a great engineer who is happy where they are. Reading the thing the CV does not say. Telling a hiring manager their bar is wrong. Closing someone who has three offers. Deciding that a candidate who fits nothing on paper is the one.

None of those are bottlenecks you can automate away, and they are also the entire job. The machine should be doing everything around them so a human has the time to do them well. That is not a compromised version of full automation. It is what full automation was always going to mean once you looked closely at it.