{"id":1505,"date":"2026-07-15T10:17:29","date_gmt":"2026-07-15T10:17:29","guid":{"rendered":"https:\/\/hirium.com\/blog\/?p=1505"},"modified":"2026-07-16T06:09:59","modified_gmt":"2026-07-16T06:09:59","slug":"recruitment-email-templates-by-pipeline-stage","status":"publish","type":"post","link":"https:\/\/hirium.com\/blog\/recruitment-email-templates-by-pipeline-stage\/","title":{"rendered":"From Application to Offer: Mapping Recruitment Email Templates to Every Pipeline Stage"},"content":{"rendered":"

Candidates who apply to a startup or SMB hear back, on average, once\u00a0 the auto-acknowledgement\u00a0 and then nothing for 14 to 21 days. During that same window, the strongest 10\u201315% of those candidates receive interview invitations from two or three other companies. The math is unforgiving: a recruiter managing 8\u201312 open roles with 150\u2013300 applicants per role cannot manually email everyone at every stage, so the emails that don’t get sent become the silent leak in the funnel.<\/span><\/p>\n

The fix is not “send more emails.” It is mapping Recruitment Email Templates by Pipeline Stage so that a specific, pre-approved message fires automatically the moment a candidate’s status changes\u00a0 applied, screened, interviewed, offered, rejected, or hired. Teams that build this map once stop rewriting the same five emails 40 times a week and stop losing candidates in the gaps between stages.<\/span><\/p>\n

The difference shows up in hard numbers. Companies that respond to applicants within 48 hours convert candidates to interviews at roughly 2x the rate of companies that take a week. Offer acceptance climbs when candidates receive a structured sequence between verbal offer and signed letter. And rejected candidates who get a timely, respectful close-out email reapply and refer others at measurably higher rates than those who are ghosted.<\/span><\/p>\n

This guide lays out the complete stage-by-stage map: which template fires at each transition, what triggers it, the tone each stage demands, and how to A\/B test subject lines so the emails actually get opened. Everything here assumes a lean team of one to three recruiters, high application volume, and real time-to-hire pressure\u00a0 because that is where automated email mapping pays back fastest.<\/span><\/p>\n

According to recent recruiting data, 62% of candidates say they lose interest in a job if they don\u2019t hear back within two weeks, highlighting how gaps in communication directly impact hiring outcomes. To explore more data behind modern hiring trends, refer to <\/span>latest recruiting statistics and benchmarks<\/b><\/a>.\u00a0<\/span><\/p>\n

What Are Recruitment Email Templates by Pipeline Stage?<\/b><\/h2>\n

Recruitment email templates<\/b><\/a> by pipeline stage are pre-written, trigger-based messages mapped to each phase of the hiring funnel\u00a0 application received, screening, interview, offer, rejection, and hire\u00a0 so that every candidate status change automatically sends the right email, with the right tone, at the right time, without manual effort from recruiters.<\/span><\/p>\n

That 55-word definition is the whole concept. The execution of what fires when, how it sounds, and how you measure it\u00a0 is where most teams get it wrong, so the rest of this guide covers exactly that.<\/span><\/p>\n

\"Recruitment<\/p>\n

The Core Problem: Communication Gaps Compound at Volume<\/b><\/h2>\n

Every recruiter intends to keep candidates informed. Intent is not the bottleneck; arithmetic is. A single mid-sized role at a growing SMB draws 200\u2013250 applications. A properly communicative process requires at minimum six touchpoints per candidate\u00a0 acknowledgment, screening update, interview invitation, interview reminder, decision email, and either an offer sequence or a <\/span>rejection email<\/b>. That is 1,200\u20131,500 emails for one role.<\/span><\/p>\n

Multiply by eight open roles and a two-person talent team is theoretically responsible for 10,000+ emails per hiring cycle. Nobody sends those manually. What actually happens is triage: the 15\u201320 candidates actively interviewing get personal emails, and the other 95% of the <\/span>talent pipeline<\/b> gets silence.<\/span><\/p>\n

The cost of that silence is specific and measurable. Candidates who hear nothing for 10+ days after applying disengage\u00a0 may accept interviews elsewhere before your screening email ever arrives. Interview no-show rates run 15\u201325% higher when no reminder is sent 24 hours before the slot. And in the offer stage, every day of silence between verbal offer and written letter gives competing offers room to land; teams routinely underestimate offer-stage drop-off by 3\u20134x because they only count formal declines, not the candidates who went quiet.<\/span><\/p>\n

There is also a compounding brand cost. Ghosted candidates talk\u00a0 on Glassdoor, on LinkedIn, and to the exact peers you will want to recruit next quarter. For startups hiring repeatedly in the same niche talent market, poor <\/span>candidate engagement<\/b><\/a> in one cycle directly raises sourcing costs in the next.<\/span><\/p>\n

The structural answer is not more recruiter hours, it is recruitment email templates by pipeline stage, wired to fire on status changes. That map is what the next section builds.<\/span><\/p>\n

The Stage-by-Stage Map: Which Template Fires, When, and in What Tone<\/b><\/h2>\n

Before writing a single template, the pipeline itself needs clean stage definitions inside your <\/span>applicant tracking system<\/b>, because recruitment email templates by pipeline stage are only as reliable as the status changes that fire them. Modern <\/span>workflow automation software<\/b><\/a> builds <\/span>automated email triggers<\/b> on a simple rule: when a candidate’s status changes to X, send template Y after delay Z. If recruiters use stages inconsistently, some marking “screened” after a resume review, others after a phone call\u00a0 the automation misfires.<\/span><\/p>\n

Here is the full visual-style map for a standard six-stage funnel:<\/span><\/p>\n

\n
\n

<\/p>\n

\n
Applied<\/div>\n<\/div>\n
\u2192<\/div>\n
\n
Screened<\/div>\n<\/div>\n
\u2192<\/div>\n
\n
Interview<\/div>\n<\/div>\n
\u2192<\/div>\n
\n
Offer<\/div>\n<\/div>\n
\u2192<\/div>\n
\n
Hired<\/div>\n<\/div>\n

<\/p>\n

\u2502<\/div>\n
\u2502<\/div>\n
\u2502<\/div>\n
\u2502<\/div>\n

<\/p>\n

<\/div>\n

<\/p>\n

\u2193<\/div>\n

<\/p>\n

\n
Rejected<\/p>\n
Can exit from Applied, Screened, Interview, or Offer<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n\n\n\n\n\n\n
Stage<\/b><\/td>\nTrigger<\/b><\/td>\nTemplate That Fires<\/b><\/td>\nSend Timing<\/b><\/td>\nTone<\/b><\/td>\n<\/tr>\n
Applied<\/span><\/td>\nApplication submitted<\/span><\/td>\nAcknowledgment + timeline expectation<\/span><\/td>\nInstant<\/span><\/td>\nWarm, informative<\/span><\/td>\n<\/tr>\n
Screened<\/span><\/td>\nStatus \u2192 “Screened \/ Shortlisted”<\/span><\/td>\nStatus update + next-step preview<\/span><\/td>\nWithin 24 hrs<\/span><\/td>\nEncouraging, specific<\/span><\/td>\n<\/tr>\n
Interview<\/span><\/td>\nInterview scheduled<\/span><\/td>\nConfirmation + logistics; reminder<\/span><\/td>\nInstant + 24 hrs before<\/span><\/td>\nClear, practical<\/span><\/td>\n<\/tr>\n
Offer<\/span><\/td>\nStatus \u2192 “Offer”<\/span><\/td>\nVerbal recap \u2192 formal letter \u2192 nudge<\/span><\/td>\nSame day, day 2, day 5<\/span><\/td>\nEnthusiastic, personal<\/span><\/td>\n<\/tr>\n
Rejected<\/span><\/td>\nStatus \u2192 “Rejected”<\/span><\/td>\nStage-appropriate decline<\/span><\/td>\nWithin 48 hrs of decision<\/span><\/td>\nRespectful, human<\/span><\/td>\n<\/tr>\n
Hired<\/span><\/td>\nOffer accepted<\/span><\/td>\nWelcome + pre-boarding sequence<\/span><\/td>\nInstant + weekly<\/span><\/td>\nCelebratory, structured<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The table is the skeleton. The judgment calls live inside each stage.<\/span><\/p>\n

Stage 1\u00a0 Applied: Set Expectations in the First Five Minutes<\/b><\/h3>\n

The acknowledgment email is the most-opened message you will ever send a candidate, which makes it the most wasted real estate in recruiting. The generic version\u00a0 “We received your application”\u00a0 confirms delivery and nothing else. The high-performing version does three things in under 120 words: confirms receipt, states a concrete timeline (“you’ll hear from us within 5 business days either way”), and sets the channel (“all updates will come from this address”).<\/span><\/p>\n

The phrase “either way” is doing heavy lifting. It commits you to closing the loop with rejected candidates, and it signals to strong candidates that your process is organized\u00a0 a real differentiator when they are comparing you against companies that go dark. This template should fire instantly on submission; any delay reads as disorganization.<\/span><\/p>\n

Stage 2\u00a0 Screened: The Update Most Teams Skip Entirely<\/b><\/h3>\n

Somewhere between application and interview sits the stage where the most candidates are lost\u00a0 and where deciding <\/span>which <\/b>email template<\/b><\/a> to send at each hiring stage<\/b> matters most, because most teams send nothing here at all. When a candidate passes resume screening, an automatic status email should tell them so and preview what’s next: “Your background is a strong match. Our team is finalizing the interview shortlist this week; expect scheduling details by Friday.”<\/span><\/p>\n

The tone here is encouraging but not committal; you are keeping candidates warm without promising an interview. For teams running AI resume screening, this email can fire the moment the shortlisting algorithm moves a candidate forward, which means top applicants get positive signals within hours of applying rather than weeks. That speed alone is a competitive weapon: the best candidates are off the market in about 10 days.<\/span><\/p>\n

Candidates screened out at this stage get the rejection template (covered below)\u00a0 not silence.<\/span><\/p>\n

Stage 3\u00a0 Interview: Where AI Interview Scheduling Removes the Ping-Pong<\/b><\/h3>\n

Coordinating a single interview by email averages 5\u20138 back-and-forth messages and 1\u20133 days of elapsed time. <\/span>AI interview scheduling<\/b><\/a> collapses that to one email containing a live booking link synced to interviewer calendars; the candidate picks a slot and confirmation fires instantly. For teams also running an AI interviewer for first-round screens, the invitation can include an on-demand link the candidate completes on their own schedule\u00a0 removing coordination entirely from round one.<\/span><\/p>\n

Two templates matter here, and both should be automated:<\/span><\/p>\n

The confirmation email fires the moment a slot is booked. It must contain everything a candidate needs in one place: date and time with timezone, format and link (or address and parking), interviewer names and roles, expected duration, and any prep materials. Practical completeness is the tone\u00a0 candidates rate “I knew exactly what to expect” among the strongest drivers of positive candidate experience scores.<\/span><\/p>\n

The reminder email is one of the highest-ROI interview reminders you can automate\u00a0 fires 24 hours before the slot with a shortened restatement of logistics and a one-click reschedule link. The reschedule link is counterintuitive but critical: making it easy to move an interview converts would-be no-shows into rescheduled conversations. Teams that add the 24-hour reminder typically cut no-shows by half.<\/span><\/p>\n

On timing more broadly, the data on the best time to send interview confirmation emails is consistent: send the confirmation instantly on booking (delays create doubt the booking worked), and send reminders mid-morning local time, when open rates peak.<\/span><\/p>\n

\"Automated<\/p>\n

Stage 4\u00a0 Offer: A Three-Email Sequence, Not a Single Letter<\/b><\/h3>\n

The offer stage is the only place in the funnel where under-automation and over-automation both fail. A fully robotic offer reads as cheap exactly when the candidate is deciding whether you value them; a purely manual process introduces the fatal delays described earlier.<\/span><\/p>\n

The working pattern is a three-part sequence with human checkpoints:<\/span><\/p>\n

    \n
  1. Same-day verbal recap<\/b> (semi-automated draft, personalized by the recruiter): congratulations, headline terms, and the promise of the formal letter within 48 hours.<\/span><\/li>\n
  2. Formal offer letter<\/b> (template-generated, human-reviewed): full compensation, benefits, start date, and a clear acceptance deadline\u00a0 5 business days is standard and keeps momentum without pressure.<\/span><\/li>\n
  3. Day-5 nudge<\/b> (automated, warm): a short check-in offering a call to discuss questions, triggered only if the offer remains unsigned.<\/span><\/li>\n<\/ol>\n

    Tone across all three: enthusiastic and personal. This is the one stage where templates should feel least like templates\u00a0 merge fields for role, manager name, and a specific line about why the team was impressed. Measured well, this sequence is where your <\/span>offer acceptance rate<\/b> is won or lost; teams that compress verbal-to-letter time from a week to 48 hours routinely see acceptance climb 10\u201315 percentage points.<\/span><\/p>\n

    Stage 5\u00a0 Rejected: The Template That Determines Your Reputation<\/b><\/h3>\n

    Rejection emails carry open rates of 70%+\u00a0 candidates want closure\u00a0 which means this is the template your employer brand is most often judged by. The rules: send within 48 hours of the decision, never on Friday evening, and calibrate depth to the stage reached. An applicant screened out on resume review gets a brief, kind, no-feedback note. A candidate who completed two interview rounds gets a longer message, ideally with one concrete piece of feedback and an explicit invitation to apply for future roles.<\/span><\/p>\n

    That invitation is not a platitude if your system backs it. Rejected-but-strong candidates flagged into a silver-medalist pool become your cheapest future hires; teams that re-engage this pool fill 10\u201320% of subsequent roles from it at near-zero sourcing cost.<\/span><\/p>\n

    Stage 6\u00a0 Hired: The Sequence That Prevents First-Day Ghosting<\/b><\/h3>\n

    Signed offers still fall through\u00a0 renege rates in competitive markets run 5\u201310%, concentrated in the gap between signing and day one. A pre-boarding email sequence closes that gap: an immediate welcome email, a week-out logistics email (start time, equipment, first-day agenda), and a two-days-out note from the hiring manager. All three can fire automatically off the start date field, with only the manager note requiring a personal touch.<\/span><\/p>\n

    How to A\/B Test Recruiting Email Subject Lines<\/b><\/h3>\n

    Templates decay. A subject line that opened at 68% in January drifts down as candidates see the same pattern from every company, which is why learning <\/span>how to A\/B test recruiting email subject lines<\/b> belongs in the map itself, not as an afterthought. The process:<\/span><\/p>\n

      \n
    1. Pick one stage and one variable.<\/b> Test subject lines only with the same body, same send time. Testing two variables at once tells you nothing.<\/span><\/li>\n
    2. Write two variants with a real hypothesis.<\/b> For example, interview confirmation: “Interview confirmed: [Role] at [Company], Tuesday 2pm” vs. “[FirstName], you’re booked\u00a0 here’s everything for Tuesday.” Hypothesis: logistics-forward vs. name-personalized.<\/span><\/li>\n
    3. Split 50\/50 at meaningful volume.<\/b> You need roughly 100+ sends per variant for directional confidence; below that, run the test across multiple roles.<\/span><\/li>\n
    4. Measure the metric that matters for that stage.<\/b> Opens for acknowledgments and updates; reply\/booking rate for interview invitations; signed-offer rate for offer nudges. Note that Apple Mail privacy inflates raw open rates, so compare variants against each other, not against absolute benchmarks.<\/span><\/li>\n
    5. Promote the winner, archive the loser, log the result.<\/b> Then test the next stage. One test per stage per quarter is a sustainable cadence for a small team.<\/span><\/li>\n<\/ol>\n

      Patterns that consistently win in recruiting specifically: 5\u20137 word subject lines, the candidate’s first name as a merge token, and the role title stated plainly. Patterns that consistently lose: “exciting opportunity,” all-caps urgency, and vague teasers that hide which company is writing.<\/span><\/p>\n

      Real-World Results: Two Teams That Mapped the Funnel<\/b><\/h2>\n

      A 40-person fintech startup hiring 12 engineering and ops roles per quarter had one recruiter and a 19-day average gap between application and first contact. After mapping recruitment email templates by pipeline stage across all six statuses inside their <\/span>ATS<\/b><\/a>, first-response time dropped to under 4 hours, interview no-shows fell from 22% to 9% after the 24-hour reminder went live, and time-to-hire shrank from 41 to 28 days across two quarters.<\/span><\/p>\n

      A 15-location staffing-heavy retail SMB faced the opposite problem: 1,800 applications a month and a rejection backlog so large that 70% of applicants never heard back. Automating stage-based status and rejection emails cleared the backlog in one cycle; within four months, their reapplication rate from previously rejected candidates rose 3x, and Glassdoor interview-experience ratings climbed from 2.9 to 4.1.<\/span><\/p>\n

      \"Recruiting<\/p>\n

      Choosing the Tooling: A Decision Framework for Recruitment Status Update Software<\/b><\/h2>\n

      The stage map is tool-agnostic, but execution is not\u00a0 and evaluating <\/span>recruitment status update software<\/b><\/a> for recruitment email templates by pipeline stage comes down to five capabilities, not feature-list length. Score any vendor, including a spreadsheet-plus-email-tool stack, against these:<\/span><\/p>\n\n\n\n\n\n\n\n\n
      Criterion<\/b><\/td>\nWhat “Good” Looks Like<\/b><\/td>\nWhy It Matters<\/b><\/td>\n<\/tr>\n
      Trigger granularity<\/span><\/td>\nEmails fire on any status change, with per-stage delay rules<\/span><\/td>\nThe whole map depends on this primitive<\/span><\/td>\n<\/tr>\n
      Template + merge fields<\/span><\/td>\nRole, name, interviewer, dates auto-populate; branded sender domain<\/span><\/td>\nPersonalization at volume without manual edits<\/span><\/td>\n<\/tr>\n
      Scheduling integration<\/span><\/td>\nCalendar-synced booking links inside emails<\/span><\/td>\nRemoves the 5\u20138 message coordination loop<\/span><\/td>\n<\/tr>\n
      Analytics per template<\/span><\/td>\nOpen, click, and reply rates by stage and variant<\/span><\/td>\nWithout this, A\/B testing is guesswork<\/span><\/td>\n<\/tr>\n
      Pipeline data hygiene<\/span><\/td>\nSingle candidate record across stages, duplicate detection<\/span><\/td>\nMisfired emails almost always trace to dirty data<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      That last row deserves emphasis, because strong <\/span>Candidate Database management<\/b><\/a> is the unglamorous foundation under everything else: if the same candidate exists as three records across three roles, your automation will send them three conflicting emails, and no template quality survives that. Centralized candidate records with <\/span>real-time candidate tracking<\/b> are prerequisites, not nice-to-haves.<\/span><\/p>\n

      On cost: standalone email automation tools run $50\u2013150 per recruiter per month and still leave you stitching together scheduling and pipeline data. An integrated <\/span>AI-powered ATS<\/b> that bundles screening, scheduling, and stage-triggered email costs less than the stitched stack in most SMB scenarios\u00a0 and several, including Hirium, offer forever-free entry plans with flat pricing, which changes the evaluation from “can we afford tooling” to “which map do we build first.”<\/span><\/p>\n

      Migration friction is the other hidden cost line. If you are moving off an incumbent system, ask vendors directly whether migration is supported and free; how to automate candidate status update emails on a new platform matters far less if six months of candidate history gets stranded in the old one.<\/span><\/p>\n

      \"Pipeline<\/p>\n

      What Most Teams Get Wrong<\/b><\/h2>\n

      The most common failure with recruitment email templates by pipeline stage is not bad templates, it is automating the wrong stages first. Teams instinctively automate outbound sourcing emails because that is where effort feels visible, while the acknowledgment, screening-update, and rejection emails with 60\u201390% open rates and direct brand impact\u00a0 stay manual and therefore unsent. Automate the funnel’s back half first. Sourcing can stay artisanal; status communication cannot.<\/span><\/p>\n

      The second failure is confusing automation with volume. A mapped funnel sends <\/span>fewer<\/span><\/i> total emails than a panicked manual process, because every message is load-bearing. If your sequence includes a “just checking in” email that carries no new information, delete it; recruiting-email data consistently shows that each follow-up must add something: a timeline, a decision, a next step\u00a0 or it trains candidates to ignore you.<\/span><\/p>\n

      Third: teams write templates in the company’s marketing voice instead of a recruiter’s voice. Candidates respond to emails that read like they came from a person with a name and a calendar, not a brand. Send from a real recruiter address, sign with a real name, and reserve polish for the offer letter.<\/span><\/p>\n

      Finally, almost no one closes the measurement loop. The template map gets built, launched, and never revisited, while recruitment analytics sit unread. The teams that outperform review stage-level email metrics monthly\u00a0 open rate by template, booking rate on invitations, acceptance rate on offers\u00a0 and treat every drop as a test hypothesis. The map is not a document; it is a system you tune.<\/span><\/p>\n

      Build the Map Before the Next Role Opens<\/b><\/h2>\n

      The full template map\u00a0 six stages, roughly ten templates, trigger rules, and one A\/B test per quarter\u00a0 takes a focused afternoon to build and configure in a modern ATS in under a week. The alternative is another hiring cycle where your best applicants hear from a competitor before they hear from you.<\/span><\/p>\n

      If you want to pressure-test your stage map against how 5,000+ startups and SMBs run theirs, start with the free funnel audit above, wire the six triggers into your system, and measure the first month of open and booking rates against your manual baseline. The gap is usually the entire business case.<\/span><\/p>\n

      \"Recruitment<\/p>\n

      Frequently Asked Questions<\/b><\/h2>\n

      What emails should be sent at each stage of recruitment?\u00a0<\/b><\/h3>\n

      Six templates cover the standard map of recruitment email templates by pipeline stage: an instant application acknowledgment, a screening status update, an interview confirmation plus 24-hour reminder, a three-part offer sequence (verbal recap, formal letter, nudge), a stage-calibrated rejection, and a pre-boarding welcome series. Each fires automatically on a candidate status change, with only offer-stage messages requiring a human personalization pass.<\/span><\/p>\n

      How do you automate recruitment emails without sounding robotic?\u00a0<\/b><\/h3>\n

      Use merge fields beyond the first name\u00a0 role title, interviewer name, specific dates\u00a0 and send from a named recruiter address rather than a no-reply alias. Keep automated messages under 150 words, write them in first person, and reserve fully manual writing for the two moments candidates scrutinize most: post-interview rejections and offers.<\/span><\/p>\n

      What is a good open rate for recruitment emails?\u00a0<\/b><\/h3>\n

      Benchmarks vary sharply by stage. Cold sourcing outreach averages 40\u201360% opens, application acknowledgments and status updates reach 60\u201380%, and offer or rejection emails often exceed 80% because candidates are awaiting a decision. Judge each template against its own stage benchmark and its own historical baseline, not against a single blended number.<\/span><\/p>\n

      How do you write a rejection email that protects your employer brand?\u00a0<\/b><\/h3>\n

      Send it within 48 hours of the decision, address the candidate by name, state the outcome plainly in the first two sentences, and scale warmth to investment\u00a0 brief and kind for resume-stage declines, feedback and a reapply invitation for finalists. Never use “unfortunately” as the opening word of the subject line, and never let rejections batch up for weeks.<\/span><\/p>\n

      Should recruitment emails be automated or personalized?\u00a0<\/b><\/h3>\n

      It is a false choice at every stage except the offer. Acknowledgments, updates, confirmations, reminders, and early-stage rejections should be fully automated with merge-field personalization, because speed beats hand-crafting there. Offers and final-round rejections warrant genuine human writing layered on a template skeleton. The practical rule: automate the trigger and timing everywhere; personalize the content where stakes peak.<\/span><\/p>\n

      How many follow-up emails should recruiters send to candidates?\u00a0<\/b><\/h3>\n

      For sourcing outreach, three to four touches spaced 3\u20136 days apart capture the large majority of eventual replies\u00a0 sequences that beat single sends by more than 2x. Inside an active pipeline, follow-ups should be event-driven rather than counted: one reminder before each interview, one nudge five days into an unsigned offer, one re-engagement when a matching role opens.<\/span><\/p>\n

      How do I know if my current process needs this, or if it’s overkill for my team size?\u00a0<\/b><\/h3>\n

      Run one diagnostic: pull ten random candidates from your last closed role and count the days between each of their status changes and the email (if any) they received about it. If more than two candidates have a gap over five days\u00a0 or received nothing at all\u00a0 the map will pay for itself on the next roll. Most platforms in this category, Hirium included, will run that funnel audit with you on a free plan before you commit to anything.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

      Candidates who apply to a startup or SMB hear back, on average, once\u00a0 the auto-acknowledgement\u00a0 and then nothing for 14 to 21 days. During that same window, the strongest 10\u201315% of those candidates receive interview invitations from two or three other companies. The math is unforgiving: a recruiter managing 8\u201312 open roles with 150\u2013300 applicants […]<\/p>\n","protected":false},"author":3,"featured_media":1506,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-1505","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ats-automation"],"_links":{"self":[{"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/posts\/1505","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/comments?post=1505"}],"version-history":[{"count":3,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/posts\/1505\/revisions"}],"predecessor-version":[{"id":1515,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/posts\/1505\/revisions\/1515"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/media\/1506"}],"wp:attachment":[{"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/media?parent=1505"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/categories?post=1505"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/tags?post=1505"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}