{"id":1565,"date":"2026-07-28T10:27:32","date_gmt":"2026-07-28T10:27:32","guid":{"rendered":"https:\/\/hirium.com\/blog\/?p=1565"},"modified":"2026-07-28T10:40:28","modified_gmt":"2026-07-28T10:40:28","slug":"job-posting-software-for-candidate-quality","status":"publish","type":"post","link":"https:\/\/hirium.com\/blog\/job-posting-software-for-candidate-quality\/","title":{"rendered":"Job Posting Software for Candidate Quality: Features That Actually Work"},"content":{"rendered":"

41 % of organizations say they’re now seeing candidates ghost them mid-interview process, <\/span>according to SHRM’s<\/b><\/a> 2025 Talent Trends Report, up from a problem that used to be rare enough to joke about.\u00a0<\/span><\/p>\n

That number alone should reframe how most hiring teams think about their tech stack. Most of them are still optimizing for applicant volume, when the real cost is sitting in the candidates who never show up, never convert, or never should have been shortlisted in the first place.<\/span><\/p>\n

More applicants were supposed to solve the hiring problem. It didn’t. A posting that pulls in 300+ resumes just moves the bottleneck downstream into screening hours, interview scheduling, and recruiter fatigue.<\/span><\/p>\n

\u00a0The teams that are actually <\/span>hiring faster in 2026 <\/b>aren’t the ones getting more applications. They’re the ones using <\/span>job posting software for candidate quality<\/b> instead of job posting software built to maximize reach.<\/span><\/p>\n

This matters most for startups and SMBs, where one recruiter or a two-person HR team is often running the entire funnel sourcing, screening, scheduling, and closing without the headcount to manually triage hundreds of resumes per role.\u00a0<\/span><\/p>\n

The gap between “software that posts jobs” and “software that improves who you interview” is where most of the wasted time in <\/span>2026 hiring<\/b> actually lives.<\/span><\/p>\n

Founders and talent leads evaluating tools right now tend to default to the same shortlist: which platform posts to the most job boards, and which one has the biggest applicant database.\u00a0<\/span><\/p>\n

Those are reasonable questions for a company that’s still building its first hiring process.\u00a0<\/span><\/p>\n

They stop being the right questions the moment a team is running multiple open roles simultaneously, and the constraint shifts from “not enough applicants” to “too many of the wrong applicants and not enough hours to sort them.”<\/span><\/p>\n

\"Applicant<\/p>\n

What Is Job Posting Software for Candidate Quality?<\/b><\/h2>\n

Job posting software<\/b><\/a> for candidate quality is recruitment technology that filters, scores, and surfaces applicants based on job-fit signals, skills, experience relevance, and screening responses rather than simply distributing a listing to maximize application count.<\/span><\/p>\n

It combines AI resume screening, structured candidate scoring, and workflow automation to reduce the volume of unqualified applicants a recruiter has to manually review before reaching a shortlist.<\/span><\/p>\n

The Core Problem: Volume Without Filtering Wastes Recruiter Hours<\/b><\/h2>\n

Most <\/span>applicant tracking systems<\/b><\/a> were built in an era when the applicant-to-interview ratio wasn’t the bottleneck. That era is over. Industry benchmarking from CareerPlug’s 2025\u00a0<\/span><\/p>\n

Recruiting Metrics Report, based on 10 million+ applications, puts the applicant-to-interview conversion rate at roughly 3%, meaning 97 out of every 100 resumes a recruiter receives never should have reached a human review queue in the first place.<\/span><\/p>\n

For a startup posting five open roles at once, with 150\u2013300 applicants per role, that’s 750\u20131,500 resumes a month competing for a recruiter’s attention.\u00a0<\/span><\/p>\n

Most teams underestimate this by 3\u20134x when they’re scoping headcount for a hiring function, because they plan around the number of roles, not the number of resumes each role generates.<\/span><\/p>\n

The downstream cost compounds. Every unqualified resume that reaches a phone screen costs roughly 20\u201330 minutes of recruiter time.\u00a0<\/span><\/p>\n

\"applicant-to-hire-conversion-funnel\"<\/p>\n

Every unqualified candidate that reaches a first-round interview costs 45\u201360 minutes of a hiring manager’s time plus scheduling coordination, calendar holds, and the opportunity cost of a slot that a stronger candidate didn’t get.<\/span><\/p>\n

Interview no-shows make the math worse. Industry KPI benchmarks put a healthy no-show rate under 5%, with anything above 10% signaling a process problem rather than bad luck.\u00a0<\/span><\/p>\n

 <\/p>\n

Three causes show up consistently across recruiting teams: too much lead time between scheduling and the interview date, no reminder touchpoints in between, and unclear logistics (wrong time zone, missing video link, unclear address for on-site rounds). None of these are candidate-quality problems; they’re <\/span>workflow automation software<\/b><\/a> gaps.<\/span><\/p>\n

The cost implications add up faster than most hiring plans account for. A recruiter earning the equivalent of \u20b98\u201312 lakhs annually costs a business roughly \u20b9400\u2013600 per working hour once loaded costs are included.<\/span><\/p>\n

If 60 of that recruiter’s hours each month go toward screening resumes that were never going to pass a first-round interview, that’s \u20b924,000\u201336,000 a month spent on volume the process should have filtered out before it reached a human reviewer.\u00a0<\/span><\/p>\n

Multiply that across a hiring season with five or six open roles, and the unfiltered-volume problem stops being an inconvenience and starts showing up as a real line item.<\/span><\/p>\n

Time-to-hire compounds the same way. Industry data across small businesses puts average time-to-hire between 40\u201345 days, and every extra week a role stays open has a measurable cost in lost productivity, team overload, and, for revenue-generating roles, delayed output.<\/span><\/p>\n

Teams that treat screening as a manual, one-resume-at-a-time task are effectively accepting a longer time-to-hire as the price of not investing in filtering technology.<\/span><\/p>\n

None of this means volume is worthless. A posting still needs enough reach to surface qualified candidates in the first place, particularly for niche or senior roles where the talent pool is naturally smaller.\u00a0<\/span><\/p>\n

The problem is treating volume as the finish line instead of the starting point, which is exactly the shift that separates reach-focused job boards from job posting software for candidate quality.<\/span><\/p>\n

Deep Dive: The Features That Actually Move Candidate Quality<\/b><\/h2>\n

Reach-focused job boards and quality-focused job posting software look similar from the outside; both let you write a listing, publish it, and collect applications. The difference is entirely in what happens between “applicant submits resume” and “recruiter sees a shortlist.” That gap is where four categories of features do the real work.<\/span><\/p>\n

1. AI Resume Screening That Scores Against the Role, Not Keywords<\/b><\/h3>\n

Early resume-parsing tools worked off keyword matching, which meant a candidate who wrote “led a team of 5” scored lower than one who copy-pasted the job description’s exact phrasing. Modern <\/span>AI resume screening<\/b><\/a> evaluates context years of relevant experience, skill adjacency, and career trajectory against the specific role’s requirements, not a static keyword list.<\/span><\/p>\n

The practical difference: keyword-based filtering rejects strong candidates who phrase things differently and passes weak candidates who know how to game the parser. Context-based scoring reduces both false negatives and false positives, which is the entire point of screening software in the first place.<\/span><\/p>\n

For a startup hiring a senior engineer, this is the difference between a shortlist of 8 genuinely qualified candidates and a shortlist of 25 where a recruiter still has to manually re-screen half of them.<\/span><\/p>\n

2. AI Candidate Insights for Ranking, Not Just Sorting<\/b><\/h3>\n

AI candidate insights<\/b><\/a> go one layer past parsing. Instead of a pass\/fail flag, the software surfaces a ranked shortlist with reasoning attached on why a candidate scored where they did, which requirements they matched, and where the gaps are. Some platforms, including Hirium, extend this with an AI interviewer that runs unbiased first-round screening conversations before a human recruiter ever gets involved, which removes a layer of scheduling friction for high-volume roles.<\/span><\/p>\n

This matters for consistency. Two recruiters screening the same 100 resumes manually will disagree on which 15 are worth interviewing; human fatigue and unconscious pattern-matching both creep in after resume 40 or so. A scoring model applies the same criteria to resume 1 and resume 300.<\/span><\/p>\n

3. Candidate Database Management That Doesn’t Lose Warm Leads<\/b><\/h3>\n

Candidate database management<\/b><\/a> is the most underrated feature category in recruitment technology, because its value doesn’t show up until 3\u20136 months after a role closes. A centralized, searchable database means the strong second-place candidate from a March hire is retrievable for a similar August role without re-running a full sourcing cycle.<\/span><\/p>\n

Without this, teams re-source from zero for every open role, even when a qualified, previously-vetted candidate already exists in an old spreadsheet or a closed email thread. Real-time candidate tracking across every open requisition also prevents the common SMB failure mode of two recruiters unknowingly reaching out to the same candidate for two different roles.<\/span><\/p>\n

4. Workflow Automation That Reduces No-Shows, Not Just Admin Time<\/b><\/h3>\n

This is the category most directly tied to interview attendance, and it’s worth breaking into a concrete process:<\/span><\/p>\n

    \n
  1. Confirm within 24 hours of scheduling<\/b>: an automated confirmation email or SMS sent immediately after a candidate books a slot, restating date, time, time zone, and format (video link or address).<\/span><\/li>\n
  2. Send a reminder 48 hours out<\/b>: a second automated touchpoint with a one-click reschedule option, so candidates with a genuine conflict self-serve instead of silently no-showing.<\/span><\/li>\n
  3. Send a same-day reminder 2\u20133 hours before<\/b> the final touchpoint, timed to catch candidates before they lose the window to reschedule gracefully.<\/span><\/li>\n<\/ol>\n

    \"hree<\/p>\n

    Calendar-hold automation reinforces it: auto-blocking the interviewer’s calendar the moment a slot is confirmed, and auto-releasing it the moment a candidate reschedules, prevents the wasted hiring-manager time that no-shows create even when the candidate does eventually reconnect.<\/span><\/p>\n

    A reschedule-friendly policy removes the reason candidates ghost instead of rescheduling. A workable version reads: <\/span>“Life happens. If you need to move your interview, use the link in your confirmation email up to 4 hours before your slot, no explanation needed. If something comes up last-minute, just reply to this email and we’ll find a new time.”<\/span><\/i><\/p>\n

    Removing the friction and the awkwardness of asking for a reschedule directly reduces silent no-shows, because most candidates who ghost do so. After all, rescheduling feels like it requires an excuse.<\/span><\/p>\n

    5. Recruitment Analytics That Show Which Channels Actually Convert<\/b><\/h3>\n

    Applicant volume by source is a vanity metric on its own. What matters is source effectiveness: which job boards, referral channels, or sourcing efforts produce candidates who actually convert to interviews and offers, not just applications.<\/span><\/p>\n

    Recruitment analytics<\/b> dashboards that break down time-to-hire, offer acceptance rate, and recruiter load by channel let a hiring team redirect budget away from high-volume, low-conversion sources and toward the ones that are quietly outperforming.<\/span><\/p>\n

    This is especially relevant for startups running paid job board listings on a fixed budget. A channel generating 150 applications with a 1% shortlist rate is a worse spend than one generating 40 applications with a 12% shortlist rate, even though the first number looks more impressive in a monthly report.<\/span><\/p>\n

    Without analytics broken out by source, that distinction is invisible until a recruiter manually cross-references spreadsheets, which most SMB teams don’t have the bandwidth to do consistently.<\/span><\/p>\n

    6. Branded Career Pages and Candidate Experience<\/b><\/h3>\n

    A generic, unbranded application form is itself a quality filter, just not the kind a hiring team wants. Candidates evaluating multiple offers read a career page as a signal of how organized the company is likely to be as an employer, and a clunky or generic application flow disproportionately loses stronger candidates who have other options and less patience for friction.<\/span><\/p>\n

    Customizable, branded career pages that load quickly, work on mobile, and clearly communicate role expectations reduce application abandonment at the top of the funnel.\u00a0<\/span><\/p>\n

    This doesn’t directly filter for skill match the way AI resume screening does, but it does affect who applies in the first place, and candidate experience research consistently shows that process friction disproportionately drives away higher-caliber applicants who have competing offers.<\/span><\/p>\n

    Compliance and Integration Considerations<\/b><\/h3>\n

    For startups and SMBs evaluating <\/span>talent acquisition software<\/b>, two practical factors matter beyond feature lists: data residency for candidate PII, and how cleanly the platform migrates existing candidate records from a prior ATS.\u00a0<\/span><\/p>\n

    A forced re-upload of years of candidate history is a common reason teams delay switching tools even when the current one is clearly underperforming, which is why migration support, not just onboarding support, should be part of the evaluation.<\/span><\/p>\n

    Integration depth is the second practical filter. A platform that only handles job posting and resume intake, without connecting to the calendars, video-conferencing tools, and email systems a team already uses, just relocates the manual-coordination problem instead of solving it.\u00a0<\/span><\/p>\n

    Calendar-hold automation, for example, only works if the software can write directly to the interviewer’s calendar rather than relying on a recruiter to manually block time after every scheduled interview.\u00a0<\/span><\/p>\n

    The same applies to automated status emails: if a platform can’t trigger candidate updates directly from a stage change in the pipeline, teams end up building a manual parallel process anyway, which defeats the purpose of adopting workflow automation software in the first place.<\/span><\/p>\n

    Cost structure interacts with both of these.\u00a0<\/span><\/p>\n

    Per-recruiter-seat pricing can look inexpensive at a two-person hiring team and become disproportionately expensive the moment a startup scales its talent function to five or six recruiters during a growth phase.\u00a0<\/span><\/p>\n

    Flat pricing with no per-hire or per-recruiter fees removes that scaling penalty, which matters more for SMBs than the headline monthly price usually suggests during a first look at a vendor’s pricing page.<\/span><\/p>\n

    Case Study: Candidate Quality Over Volume in Practice<\/b><\/h2>\n

    A 40-person fintech startup running four open roles simultaneously was receiving roughly 220 applications per posting through a generic job board integration, with a recruiter manually screening each one.\u00a0<\/span><\/p>\n

    Average time-to-shortlist was 11 days per role, and interview no-show rate sat at 14%, well above the 10% threshold considered a warning sign.<\/span><\/p>\n

    After introducing AI resume screening and a 3-touchpoint reminder sequence, time-to-shortlist dropped to 4 days, and the no-show rate fell to 6% within two hiring cycles.\u00a0<\/span><\/p>\n

    The applicant volume didn’t change meaningfully; what changed was how much of that volume ever reached a recruiter’s manual queue, and how many confirmed interviews actually happened.<\/span><\/p>\n

    A separate case from a 15-person B2B SaaS company illustrates the database side: a candidate who reached final rounds for a product marketing role in Q1 but lost out narrowly was resurfaced from the centralized candidate database for a similar role in Q3, cutting a 3\u20134 week sourcing cycle down to a single follow-up call and an offer within 10 days.<\/span><\/p>\n

    \"Interview<\/p>\n

    Neither case involved reducing applicant volume. Both involved filtering that volume faster and following up on it more reliably, which is the distinction that matters when evaluating job posting software for candidate quality against software optimized purely for reach.\u00a0<\/span><\/p>\n

    The fintech team didn’t need fewer applicants; it needed fewer of those applicants reaching a human screener before being ranked. The SaaS team didn’t need a bigger candidate pool; it needed the pool it already had to remain searchable past the point a role closed.<\/span><\/p>\n

    Comparison Framework: Evaluating Job Posting Software for Candidate Quality<\/b><\/h2>\n

    Not every platform marketed as “AI-powered recruiting software” actually filters for quality. Many simply add a keyword-matching layer on top of the same reach-maximizing job distribution model, which produces a slightly cleaner-looking applicant list without changing the underlying volume-versus-quality tradeoff.<\/span><\/p>\n

    The evaluation framework below is built around the five factors that most directly separate quality-focused platforms from reach-focused ones, based on the feature categories covered above.\u00a0<\/span><\/p>\n

    Use it as a checklist during vendor demos rather than relying on a feature comparison chart pulled from a sales deck, since demo behavior on your own job requisitions is a more reliable signal than marketing copy.<\/span><\/p>\n\n\n\n\n\n\n\n\n
    Evaluation Criteria<\/b><\/td>\nWhat to Check<\/b><\/td>\nWhy It Matters<\/b><\/td>\n<\/tr>\n
    Screening logic<\/span><\/td>\nKeyword match vs. contextual scoring<\/span><\/td>\nDetermines false-positive and false-negative rates on shortlists<\/span><\/td>\n<\/tr>\n
    Reminder automation<\/span><\/td>\nManual follow-up vs. built-in multi-touch sequences<\/span><\/td>\nDirectly affects interview no-show rate<\/span><\/td>\n<\/tr>\n
    Candidate database<\/span><\/td>\nSiloed per-role vs. centralized, searchable across roles<\/span><\/td>\nDetermines whether past candidates are reusable<\/span><\/td>\n<\/tr>\n
    Migration support<\/span><\/td>\nSelf-service export vs. supported, free migration<\/span><\/td>\nDetermines real switching cost from an existing ATS<\/span><\/td>\n<\/tr>\n
    Pricing structure<\/span><\/td>\nPer-recruiter fees vs. flat pricing<\/span><\/td>\nAffects total cost as a team scales hiring volume<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

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

    The most common mistake isn’t picking the wrong software; it’s optimizing the evaluation for the wrong metric. Teams compare platforms on applicant volume generated per posting, when the metric that actually predicts hiring speed and quality is time-to-qualified-shortlist.<\/span><\/p>\n

    A second pattern: teams treat interview no-shows as a candidate-behavior problem rather than a process design problem.\u00a0<\/span><\/p>\n

    Blaming candidate flakiness ignores that most no-shows are traceable to scheduling gaps a recruiter’s own workflow created, too much lead time with zero touchpoints in between, or logistics details buried three emails deep instead of restated at every reminder.<\/span><\/p>\n

    A third, quieter mistake: abandoning a candidate database every time a role closes. Recruiters who don’t revisit near-miss candidates from prior searches are effectively re-doing sourcing work they already paid for in recruiter hours, every single time a similar role opens.<\/span><\/p>\n

    A fourth pattern shows up specifically during vendor selection: teams evaluate job posting software for candidate quality primarily on the strength of a sales demo, using a curated sample job requisition, rather than testing the screening logic against one of their own historically difficult-to-fill roles.<\/span><\/p>\n

    A demo built around a clean, well-defined role will make almost any AI resume screening tool look accurate.\u00a0<\/span><\/p>\n

    The real test is how the same tool handles a role with ambiguous requirements or a title that doesn’t map cleanly to standard taxonomy, which is exactly the kind of role most startups and SMBs are actually hiring for.<\/span><\/p>\n

    FAQ<\/b><\/h2>\n

    1. What is candidate quality in recruitment?<\/b>\u00a0<\/span><\/h3>\n

    Candidate quality refers to how closely an applicant’s skills, experience, and role-fit match a specific job’s requirements, as distinct from the total number of applications a posting receives.\u00a0<\/span><\/p>\n

    High-quality candidates require fewer screening cycles to identify, move through the interview pipeline with fewer drop-offs, and convert to hires at a meaningfully higher rate once they actually reach an interview.\u00a0<\/span><\/p>\n

    A posting can generate hundreds of applications and still produce low candidate quality if most of those applicants don’t meet the role’s core requirements.<\/span><\/p>\n

    2. How do you measure candidate quality instead of volume?\u00a0<\/b><\/h3>\n

    Track time-to-qualified-shortlist, interview-to-offer ratio, and interview no-show rate rather than total applicants per posting.<\/span><\/p>\n

    A posting generating 300 applications with a 2% shortlist rate is performing worse than one generating 80 applications with a 15% shortlist rate, even though the raw application count tells the opposite story.<\/span><\/p>\n

    Recruitment analytics that break these figures out by role and by sourcing channel make the comparison visible instead of anecdotal.<\/span><\/p>\n

    3. What features should job posting software have in 2026?\u00a0<\/b><\/h3>\n

    At minimum: contextual AI resume screening, a centralized and searchable candidate database, automated multi-touchpoint interview reminders, and recruitment analytics covering time-to-hire and source effectiveness.<\/span><\/p>\n

    Branded career pages and free, supported ATS migration are strong secondary signals of a mature platform, since they indicate the vendor has built for teams switching from an existing tool rather than only for greenfield setups.<\/span><\/p>\n

    How can automation reduce interview no-shows?<\/b>\u00a0<\/span><\/h3>\n

    A structured reminder sequence confirmation within 24 hours of booking, a reminder at 48 hours out with a one-click reschedule option, and a final reminder 2\u20133 hours before the slot addresses the three most common no-show causes: long lead times between scheduling and the interview, missing follow-up in between, and unclear logistics that only get restated once, in the original invite.<\/span><\/p>\n

    4. Is AI resume screening accurate enough to trust?\u00a0<\/b><\/h3>\n

    Contextual AI screening, which evaluates experience relevance rather than keyword matches, meaningfully reduces both false rejections of strong candidates and false shortlisting of weak ones compared to older keyword-parsing tools.\u00a0<\/span><\/p>\n

    It works best as a first-pass filter that narrows volume down to a manageable shortlist, with human recruiters making the final call on borderline or ambiguous cases rather than relying on the score alone.<\/span><\/p>\n

    5. How much does job posting software cost for a startup?<\/b><\/h3>\n

    Costs vary widely, from per-recruiter-seat pricing that scales with team size to flat-fee platforms with no per-hire or per-recruiter charges.\u00a0<\/span><\/p>\n

    Startups evaluating <\/span>job posting software for candidate quality<\/b> should weigh total cost at their expected hiring volume across a full year, not just the entry-tier monthly price, since per-recruiter and per-hire fees compound quickly during high-volume hiring quarters when several roles are open at once.<\/span><\/p>\n

    6. Which recruiting tools help track candidate quality over time?\u00a0<\/b><\/h3>\n

    Recruitment analytics dashboards that report time-to-hire, offer acceptance rate, recruiter load, and source effectiveness by channel let teams see which job boards and sourcing efforts produce candidates who actually convert to hires, not just which channels produce the most raw applications.<\/span><\/p>\n

    Reviewing these numbers quarterly, rather than only at the end of a hiring cycle, makes it easier to catch an underperforming channel before it eats further budget.<\/span><\/p>\n

    If You’re Evaluating This Now<\/b><\/h2>\n

    If you’re comparing job posting software for candidate quality against a platform built mainly for reach, the fastest way to pressure-test a vendor is to ask for their actual shortlist rate and average interview no-show rate across customers your size, not just their applicant-volume numbers.\u00a0<\/span><\/p>\n

    Run the vendor’s screening logic against one of your own historically difficult-to-fill roles before signing anything, not the clean sample requisition in their demo script.<\/span><\/p>\n

    Hirium runs AI resume screening, candidate database management, and automated reminder workflows on a forever-free plan with no per-recruiter fees, and offers free, supported migration if you’re moving off an existing ATS like Zoho Recruit. You can explore the platform at<\/span> hirium.com<\/b><\/a> and test the screening logic against a real open role before committing to anything.<\/span><\/p>\n

     <\/p>\n","protected":false},"excerpt":{"rendered":"

    41 % of organizations say they’re now seeing candidates ghost them mid-interview process, according to SHRM’s 2025 Talent Trends Report, up from a problem that used to be rare enough to joke about.\u00a0 That number alone should reframe how most hiring teams think about their tech stack. Most of them are still optimizing for applicant […]<\/p>\n","protected":false},"author":3,"featured_media":1572,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[],"class_list":["post-1565","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-talent-management"],"_links":{"self":[{"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/posts\/1565","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=1565"}],"version-history":[{"count":2,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/posts\/1565\/revisions"}],"predecessor-version":[{"id":1573,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/posts\/1565\/revisions\/1573"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/media\/1572"}],"wp:attachment":[{"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/media?parent=1565"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/categories?post=1565"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hirium.com\/blog\/wp-json\/wp\/v2\/tags?post=1565"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}