Get In Touch

How to use this template: Use this interview process audit checklist to diagnose bottlenecks in your own hiring engine. Identify why pipelines are stalling and build a data-backed case for change to present to your leadership team.

The Non-Negotiable Toolkit

A high-performing hiring engine requires the right infrastructure. Before auditing the behaviour, ensure the following tools and documents are built, approved, and actively utilised:

Phase 1: Intake & Alignment (The Foundation)

A broken process always starts with a bad kickoff. If the Hiring Manager and TA are misaligned, the entire search will fail.

The TA.guru Stance (No Intake, No Search): Do not open a requisition based on a quick Slack message or a forwarded JD. If the Hiring Manager does not have 30 minutes to align on the intake, they do not have the time to hire. Own the process and push back.

Phase 2: The Interview Loop & Assessment (The Funnel)

Top talent will not tolerate a chaotic, seven-round interview process. The loop must be rigorous but fast.

The TA.guru Stance (Kill “Culture Fit”): “Culture fit” is a breeding ground for unconscious bias. If an interviewer rejects a candidate, they must cite specific, competency-based evidence from the scorecard. If it isn’t on the scorecard, it cannot be used as a reason to reject.

Phase 3: Operations & Candidate Experience (The Machine)

A leaky funnel destroys employer brand. Speed and communication are your biggest competitive advantages.

The TA.guru Stance (Time Kills All Deals): A 24-hour feedback SLA is a mandatory behavioural standard, not a loose guideline. If a Hiring Manager habitually fails to submit feedback on time, pause their active searches until they clear their backlog.

Phase 4: Closing & The Offer (The Finish Line)

If you are losing candidates at the offer stage, the pre-closing strategy is failing.

The TA.guru Stance (Eliminate the Surprise): Surprises at the offer stage are a failure of the recruiter, not the candidate. You should know exactly what the candidate will accept before you ever generate the official paperwork.

The Output: The Audit Review Readout

Once you complete this checklist, treat it as a consulting deliverable. Schedule a 30-minute “Process Audit Readout” with the VP of People or the Hiring Manager and present your findings using the following structure:

How to use this template: Do not just send this to your Hiring Manager to fill out. Use this as your active agenda to guide the hiring manager role kickoff conversation. The goal is to uncover the business problem this role solves, align on the exact profile, and establish a partnership.

The Business Need & Impact

Stop asking for “years of experience” and start uncovering the reality of the role.

The Profile & Calibration

Define the non-negotiables versus the “nice-to-haves.”

The Pitch (Employee Value Proposition)

Top talent isn’t looking for a job; they are looking for an opportunity. How do we sell this?

The Interview Process & Assessment

Map the candidate journey to prevent bottlenecks.

Partnership & Commitments (Ways of Working)

Set the ground rules for accountability.

TA.guru Pro-Tip: Never leave a hiring manager role kickoff meeting without scheduling your first pipeline review. Lock in a 15-minute calendar invite for 5 days post-kickoff to review the first batch of sourced profiles together.

Please download our input template here to leverage in your hiring manager call

Hiring Manager Kickoff Agenda – Input FieldDownload

Recruiters have made up their minds about AI. So have candidates. The problem is they’ve reached opposite conclusions.

We surveyed Talent Acquisition professionals on how they’re actually using AI day to day, then put the same question to candidates: how does it feel to be on the other side of it? The gap between the two answers is the most important thing happening in hiring right now.

On the recruiter side, AI is everywhere. 85% use it daily, most treat it as a co-pilot, and almost none think it has improved the quality of who they hire. On the candidate side, trust has collapsed. Just 26% believe AI can evaluate them fairly, and 88% walk away with a worse view of an employer after an AI-only rejection.

Then there’s the part nobody is talking about: candidates are using AI too. Two thirds of them are now using it to write the very applications recruiters are screening. The tools are competing with each other, and the human signal is getting harder to find.

This report maps where AI belongs in hiring, where it’s quietly doing damage, and what the data says TA leaders should do about it before the trust gap widens any further.

Download the full report below.

What’s inside

The full report runs 13 pages across both surveys. You’ll get:

The recruiter benchmark: real adoption data on how TA teams are using AI day to day, which tools actually dominate (it’s not the agents), and why 58% say it’s created a “manual tax” rather than frictionless time savings.

The candidate trust data: where job seekers accept AI, where they reject it outright, and the assessment line they will not let a machine cross.

The AI arms race: how candidates are using the same tools to beat your screening, and what that does to the signal in your pipeline.

The Automate / Blend / Protect framework: a one-page reference mapping every hiring stage to the level of AI candidates will actually tolerate.

Five strategic takeaways for TA leaders, plus the full methodology and demographic breakdown.

    How to use this candidate screening template: Standardise your screening process to ensure every recruiter captures the exact same data points, eliminating “gut feel” progression.

    Phase 1: The Hook & Pitch (0–5 Mins)

    Control the call from the start. Build rapport, but quickly pivot to selling the opportunity before you start interrogating their resume.

    Phase 2: The Core Profile & Competency (5–20 Mins)

    This is where you hunt for your “Green Flags” and “Watch-Outs”. Do not ask them to walk you through their entire resume chronologically; you will run out of time.

    Phase 3: The Pre-Close & Logistics (20–25 Mins)

    If you do not capture this data with absolute clarity, you cannot submit the candidate. Ambiguity here kills offers later.

    Phase 4: Candidate Q&A & Wrap-Up (25–30 Mins)

    Leave time for them to interview you. A strong candidate will always have questions.

    The TA.guru Stance: Screening Non-Negotiables

    How to use these templates: Copy and paste directly into Slack, your ATS, or email. Hiring managers often read submissions on the go; this candidate submittal template cuts through the noise to speed up feedback.

    TA.guru Pro-Tip: Always include a clear “Green Flag” and at least one “Watch-Out.” This anchors your calibration, builds trust, and shows you are acting as a talent advisor rather than simply passing along a CV.

    Slack Template – (Copy & Paste)

    Candidate: [Name] – [Current Job Title] @ [Current Company] 

    Profile: [LinkedIn Link] | Resume: [ATS Link / Attached]

    The TL;DR:

    [1-2 sentences on why this person is worth the Hiring Manager’s time. What is their hook?]

    Alignment to Core Requirements:

    Green Flags:

    Watch-Outs / Areas to Probe:

    Logistics & Comp:

    Next Steps: Are you a YES or NO for a 30-minute intro call? (If yes, they are available [Insert 2 timeslots]).

    Example (Slack Version)

    Candidate: Sarah Jenkins – Senior Backend Engineer @ FinTechCorp

    Profile: linkedin.com/in/example | Resume: Attached in Greenhouse

    The TL;DR: 

    Sarah is a strong backend specialist who just led the migration from a monolith to microservices at her current company. She hits all 3 of our core technical requirements and is looking for a step up in scale.

    Alignment to Core Requirements:

    Green Flags:

    Watch-Outs / Areas to Probe:

    Logistics & Comp:

    Next Steps: Are you a YES or NO for a 30-minute intro call? (If yes, she is wide open this Thursday between 2 PM and 5 PM).

    ATS / Email Template (Copy & Paste)

    Use this for deep-dive roles, executive search, or complex technical hires where the Hiring Manager needs a comprehensive narrative.

    Candidate: [Name] – [Current Job Title] @ [Current Company] 

    Profile: [LinkedIn Link] | Resume: [ATS Link / Attached]

    Key Takeaways: 

    Strengths:

    Concerns / Gaps:

    Overall Assessment

    [A 2-3 sentence synthesis. Acknowledge the gaps, but explain why their strengths and overall trajectory make them a viable, strong submission for the role.]

    Logistics & Comp:

    Decision: [YES / NO]

    Example – Detailed ATS / Email Version

    Candidate: Sarah Jenkins – Senior Backend Engineer @ FinTechCorp

    Profile: linkedin.com/in/example | Resume: Attached in Greenhouse

    Key Takeaways: 

    Strengths:

    Concerns / Gaps:

    Overall Assessment

    Sarah is a highly technical and articulate engineer who meets our core requirements for Golang and AWS scale. While she will need to ramp up on GraphQL, her proven ability to execute complex architectural migrations in a regulated environment makes her an exceptionally strong submission for this level.

    Logistics & Comp:

    Decision: YES

    For a US technology company, the decision to open a Dublin operation is the easy part. The harder question is what happens next. How fast can you actually grow a team, will the people you hire stay, and can you build the kind of balanced, committed group your parent company expects.

    To answer that, we analysed the hiring data of emerging FDI technology companies that set up new Dublin operations with an engineering or sales focus, then layered on our own experience helping companies land and scale here. The findings are encouraging. Teams move through three clear stages from Seed to Core to Grow, companies that transfer a little culture early grow noticeably faster, the local multinational ecosystem hands you a ready-made talent pool, and the people who join tend to stay longer than industry norms would predict.

    Growing a Great Team in Dublin lays out what that journey looks like in practice, so you can plan your first three years with realistic expectations rather than guesswork.

    FDI in Ireland – TA.guruDownload

    Planning your Dublin operation?

    Knowing the pattern is useful. Building the team is where it gets real, and the first hires set the tone for everything that follows.

    If you are standing up a new Dublin site, working out your Seed and Core hires, or trying to scale toward that first 30 without the cost and lock-in of traditional agencies, the TA.guru team can help. We work as an embedded extension of your business, bringing local market knowledge, access to the FDI talent ecosystem, and the execution to turn a hiring plan into a team on the ground.

    Tell us what you are building in Dublin, and we will help you get there faster.

    Get in touch or email info@ta.guru

    There is a question every founder eventually faces and very few answer well. Not who do I hire next, but how should my whole organisation take shape as we grow.

    To find out what the answer looks like in practice, we profiled 1,385 employees across ten of Dublin’s most successful software start-ups and traced how their teams evolved from the early product-only days to a fully built-out organisation. The patterns were remarkably consistent. Engineering leads, sales arrives on a predictable clock, customer teams follow sales, and talent itself shifts from an afterthought to a strategic advantage.

    Charting Your Course turns those patterns into a practical hiring blueprint you can hold against your own company, so you can see where you are, what comes next, and where the common scaling mistakes tend to hit.

    TA.guru – Charting Your CourseDownload

    Reading about hiring patterns is one thing. Building the right team for where your company is heading is another, and that is the harder part.

    If you are weighing up your next hires, working out when to bring a function in-house, or trying to scale without the cost and lock-in of either agencies or fixed headcount, the TA.guru team can help. We work as an embedded extension of your business, bringing the strategy, structure and execution to match your plans to your stage of growth.

    Tell us where you are and where you want to be, and we will help you chart the path between the two.

    Get in touch here or email info@ta.guru to set up a conversation

    Hiring is starting to be a conversation between different robots.

    Most candidates now use AI somewhere in their application. Most employers of any scale now use AI somewhere in their screening. The middle of a recruitment process, the part where a candidate’s signal is supposed to meet a human evaluator’s judgement, has quietly become a conversation between two language models. The candidate’s career and the company’s hire both hang on what comes out the other side of that exchange.

    That framing sounds dramatic. The research suggests it is not.

    The candidate side

    Our recent candidate survey, which formed the basis of the Talent Trust Gap report, found that two out of three candidates are now using AI somewhere across their application process. Cover letters, CVs, screening question answers, interview prep. Often all of the above.

    This is not emerging behaviour anymore, it is the default. The “candidates are using AI” conversation has been running for two years, and most TA leaders accept the basic shape of it. What is worth saying again is that the function has largely not redesigned its assessment process around the new default. The forms, the screens, the take-homes, and the structured interviews most companies are running today were designed for a world that no longer exists.

    The formats that have quietly lost the most signal are the ones TA functions still lean on hardest. The written cover letter is now almost entirely AI-mediated for many candidates. The free-text screening question (“why do you want to work here”, “tell us about a time when”) is barely more informative. The standard take-home task, the kind that takes a candidate two or three hours to complete, can often be finished in fifteen minutes with the right prompt. None of these have been formally retired by most companies. They are simply being run as if they still work.

    That, on its own, would be enough to justify a serious rethink. But it is only half of what is going on.

    The screening side

    The newer and far less discussed half of the story sits on the employer’s side, and it is more uncomfortable than the candidate side.

    In late 2025, a research team led by Jiannan Xu at the University of Maryland, with Gujie Li at the National University of Singapore and Jane Yi Jiang at Ohio State, published a paper titled “AI Self-preferencing in Algorithmic Hiring.” Using a large-scale controlled experiment with 2,245 human-written CVs and seven major language models, including GPT-4o, GPT-4-turbo, LLaMA 3.3, Mistral, Qwen and DeepSeek, they tested whether an LLM used as a screening tool would prefer CVs that the same model had also rewritten.

    It did. Consistently. Across every model tested, with self-preference bias against human-written CVs ranging from 68 percent to 88 percent.

    This is not a rounding error or a fragile finding. It is a structural bias that holds across the entire current landscape of commercial and open-source models. The mechanism the researchers identify is self-recognition. The model is implicitly detecting linguistic and stylistic patterns that match its own output, and weighting them positively. It is not that the AI-written CVs are better written, because the researchers controlled for content quality. The screener simply prefers content that looks like its own work.

    The implication for hiring is direct. If a candidate uses ChatGPT to rewrite their CV, and your ATS or screening tool runs on an OpenAI model underneath, that candidate is significantly more likely to advance than a candidate of equivalent quality who wrote their own CV, or who used a different model. Which AI tools each side happens to use is now part of what shapes who gets hired.

    To put the academic finding into a labour market context, the same research team simulated realistic hiring pipelines across 24 occupations and found measurable downstream effects on which candidates progressed and which did not. This is a new kind of bias, where the unfairness comes from which AI tool each side happens to use rather than from the candidate’s demographic profile. Current fairness frameworks were not built to detect it, and most of the AI hiring fairness conversation to date has been looking the other way.

    There is a second-order effect worth flagging. As more candidates use AI to write their CVs, and as screening models reward AI-written content, the “winning” CV style increasingly converges on whatever the dominant model produces. Phrasing, structure, the rhythm of bullet points, the kinds of verbs used, all start to drift toward a single house style. Candidates who do not conform begin to look anomalous to the screener, regardless of their actual quality. The likely outcome over the next twelve to eighteen months is a rush to conformity, with CVs across the market converging on a narrow stylistic band optimised for whichever model is doing most of the screening. The candidates who can least afford that conformity, junior, non-native English, career-changers, are also the ones most likely to be punished for non-conformity.

    Robots talking to robots

    Put the two halves together and the shape of the system becomes clear.

    Candidates increasingly write their applications with AI. Employers increasingly screen those applications with AI. The screening AI preferences inputs that look like its own outputs, which means it preferences AI-written inputs over human-written ones, and within AI-written inputs it preferences ones that match its own model family.

    The candidate has no visibility into which model the employer is using. The employer has no reliable visibility into which model the candidate is using. The two systems negotiate the candidate’s onward progress between themselves, on the basis of stylistic resonance, before a human recruiter has read a word.

    Consider how this plays out in a typical week. A scaling tech company is hiring a Senior Product Manager. The role attracts 400 applications in ten days. The first screen is run by an ATS-integrated LLM that scores CVs against the job description. Around 270 of those applicants used ChatGPT to refine their CV. About 60 used Claude. Maybe 70 wrote their own. The screening model, an OpenAI derivative, scores the 270 ChatGPT-refined CVs systematically higher than the equivalent-quality Claude-refined ones, and both groups higher again than the 70 human-written CVs. A shortlist of 40 goes to the in-house recruiter. The recruiter spends an hour reviewing those 40 with no idea that the funnel they are looking at has been shaped less by candidate quality than by candidate tooling.

    This is what we mean by robots talking to robots. The top of the funnel for most high-volume hiring in 2026 is increasingly running on this loop, and the signal human evaluators are working from downstream has been pre-filtered by a system that is, demonstrably, biased toward AI-written content of a specific kind.

    The implications go beyond fairness. They go to whether the hiring process is doing the job it is supposed to do. If the top of the funnel is no longer a reliable signal about the candidate, every downstream decision, the interview list, the panel debrief, the hire or no-hire call, is being made on a thinner evidence base than the people making those calls realise.

    Most TA functions are not designed for this. Most ATS configurations are not designed for this. Most assessment workflows still treat the cover letter and the written screening response as if they carry signal about the candidate, when increasingly they carry signal about the candidate’s tooling.

    What TA leaders should do about it

    There are five positions worth taking. None of them are particularly comfortable.

    1. Stop pretending you can detect AI use, and design as if you cannot.

    AI detection tools are losing the arms race. False positives disproportionately punish non-native English speakers, and the tools that work today will not work in six months. Build the process on the assumption that AI was used somewhere in the application, and design assessment so that it is informative whether AI was used or not. Catching candidates out is a losing game. Designing assessment that survives AI use is a winnable one.

    2. Find out what model your screening stack runs on, and decouple it from what candidates are using.

    This is the most underrated position in the piece. If two out of three candidates are using ChatGPT, and your ATS or screening tool runs on an OpenAI model underneath, you have a self-preferencing loop sitting inside your hiring process. The mechanical advantage to candidates who happen to pick the same model family is real, measurable, and entirely invisible to the human reviewers downstream. Diversifying the model in your screening stack, or running a rules-based filter before any LLM evaluation, reduces that loop’s advantage. Most Heads of Talent cannot answer the question of what model their ATS actually uses. That should change this quarter.

    3. Stop treating cover letters and write-in screening questions as signal.

    At an industry level, this content is no longer a reliable indicator of the candidate. The information density of an AI-rewritten cover letter is approaching zero, and the information density of an AI-rewritten screening response is not far behind. Move the assessment burden onto formats that resist the loop. Live conversation, structured work product, paid trial tasks, and assessments specifically designed to evaluate how a candidate uses AI rather than whether they used it. The point is not to eliminate AI from the candidate’s side of the process, it is to stop relying on artefacts that AI has rendered uninformative.

    4. Be explicit with candidates about what AI use is welcome and what is not.

    The worst outcome is candidates using AI covertly because they assume it is banned. Anthropic’s published policy is a useful reference point. AI use to refine an application is welcome, AI use during live assessments and interviews is not. Pick a policy that matches the work, publish it on the careers site, and design the assessment around it. Ambiguity benefits no one. It quietly trains every candidate to game the system, and it punishes the ones honest enough to ask.

    5. Put humans back into the decisions that matter, and accept the cost.

    The mistake in 2026 is to assume that because AI saves time at the top of the funnel, the function can be run with fewer recruiter hours overall. The opposite is closer to the truth. When the top-of-funnel signal is degraded, the cost of that degradation is paid further down the process, by hiring managers and recruiters making judgement calls on weaker evidence. The compensating move is to expand human time on the decisions that actually matter, the late-stage interviews, the structured debriefs, the calibration meetings, and to accept that the hours saved at the top of the funnel need to be re-spent in the middle of it.

    The bigger picture

    The temptation is to respond to AI in hiring by adding more AI. Faster screening, smarter matching, AI interviewers, AI debrief notes. Some of those tools are genuinely useful and worth using. But more AI does not, on its own, address the underlying problem, which is that signal is becoming structurally unreliable in a system that is, increasingly, robots talking to robots.

    The TA functions that handle this well in the next eighteen months will not be the ones that win the AI arms race on either side of the process. They will be the ones that are deliberate about where AI helps and where it quietly hurts, that are honest with candidates about what use is welcome and what is not, and that resist the false economy of letting humans out of decisions where human judgement is still, by some distance, the most reliable signal available.

    The trust gap in modern hiring is not really about candidates. It is about whether the process itself can still be trusted to surface the people it is meant to surface. That is a question every Head of Talent should be sitting with in 2026, because the cost of getting the answer wrong compounds quickly, and it compounds in the kinds of hires that take twelve months to show up as a problem.

    Recruiting Is Having Its Developer Relations Moment

    Two forces are reshaping candidates before they ever reach a pipeline. The first is noise, as they sit buried under an avalanche of AI-generated outreach, auto-written adverts and automated rejections, almost all of it interchangeable. The second is leverage, because those same candidates can now research a company more deeply than any generation before them, comparing interview processes, reading reviews and forming a settled view of a culture long before they apply.

    The candidate has changed. The function built to reach them has barely moved.

    For thirty years, Talent Acquisition has been optimised for a single stakeholder: the employer. Time to fill, cost per hire, offer acceptance and hiring manager satisfaction still matter, and this is not a call to throw them out. But they share a blind spot. Every one of them measures the company’s convenience, and not one of them measures whether the talent market actually trusts the company behind them.

    That gap is about to decide who wins, because the work those metrics were built to track is exactly the work AI is now absorbing.

    The Active Load Is Being Automated

    Most of a recruiter’s hours still go on the active load, the mechanical engine of recruiting: sourcing, screening, scheduling, first-touch outreach, chasing updates and coordinating feedback. That engine is being automated in front of the whole profession. It is genuinely useful, and it is also a warning, because if the bulk of a recruiter’s value was administrative execution, that value is getting cheaper by the month.

    The real question for a TA leader is no longer how to do that work faster. It is what remains once the work is largely done for you, and the answer is the part machines cannot reach: brand, community, engagement, credibility and long-term affinity with the people worth hiring.

    This is not a soft footnote to recruiting. As the mechanics commoditise, the relational layer becomes the basis of competition, and the companies that win the next decade of hiring will not be the ones with the fastest funnel but the ones the market already trusts before a role is ever posted. A name is forming for this competency, and the clearest guide to it comes from a function that solved the same problem twenty years ago.

    The Gatekeeper Model Is Quietly Breaking

    The traditional recruiter works like a gatekeeper. A role opens, candidates are sourced and screened and pushed through, an offer lands, and the relationship closes the moment the requisition is filled. Everything is triggered by a vacancy, and nothing happens without one.

    That rhythm no longer matches how talented people actually move. The best of them are not waiting at the gate or refreshing a jobs page, but living in their own world, following engineers they admire, listening to podcasts, turning up at meetups and exchanging notes in communities the company has no presence in.

    What is going to matter is being where that talent already is and engaging with them dynamically rather than reactively. Not surfacing the week a role opens with a templated message, but showing up consistently in the places they gather, contributing something genuinely useful, and building a relationship that exists independently of any vacancy. By the time a role does open, most of the work is already done, because the recruiter is no longer a stranger arriving with a pitch but a familiar name continuing a conversation that started long before there was anything to sell. Reactive recruiting waits for permission, while the model that replaces it goes to the market and stays there.

    Developer Relations Already Walked This Path

    Twenty years ago, software companies hit the same wall. Developers did not want to be marketed to. They wanted to be educated, met with transparency, and given the chance to learn from people who genuinely understood their problems, and the harder a company pitched, the faster they disengaged.

    The answer was Developer Relations, and it is worth remembering how DevRel actually began, because it did not start as a job posting. It started as a competency. Engineers who happened to be good with communities began doing the work alongside their day jobs, writing the guides, answering questions in public, speaking at events and carrying the developer’s voice back into the business. It was a way of working long before it was a box on an org chart, and only at scale, in the most advanced companies, did that competency concentrate into a dedicated function with its own headcount and mandate. The mindset came first and the role followed.

    Candidate advocacy is following the same arc, and most teams are standing at the beginning of it.

    Candidate Advocacy Is a Competency, Not a Headcount

    Advocacy is not the only new muscle this era demands. As AI reshapes the function, TA will grow several of them, from workflow design and prompt fluency to sharper talent intelligence and the confident reading of data. Candidate advocacy is among the most important, because it rests on the single thing automation cannot manufacture, which is trust.

    This is also where the argument usually goes wrong, by turning into a pitch to create a brand new role. In a lean market, asking a TA leader to fund a non-req head with diffuse and lagging returns is a quick way to lose the room, and this is not that call.

    For almost every team, candidate advocacy is a competency to build into the people already on the team rather than a job to post. It is the discipline of creating genuine value for talent before the company needs anything in return. In practice that means educating rather than selling, so a recruiter explains how a career actually develops instead of reciting a job spec. It means cultivating a community rather than a database, nurturing a network around a skill or a city instead of a contact list that only hears from the company when it is hiring. It means producing open, useful knowledge, the interview guides and salary insights and career frameworks that help a person whether or not they ever apply and it means carrying the candidate’s voice back into hiring design, so feedback that lives in anecdotes today becomes a real input into how the company hires tomorrow. None of this requires an open vacancy or a new hire, and all of it compounds over time.

    At the Frontier, the Competency Becomes a Role

    In the most advanced talent functions, the same thing that happened to DevRel will happen here, and the competency will concentrate into a dedicated role. At that point the Candidate Advocate becomes the top-of-funnel growth engine for the hiring system, with a mandate that is not transactional recruiting but building talent ecosystems and drawing high-quality candidates into the network. The work spans referral ecosystem development, community building, content, employer narrative, market credibility, candidate education and long-term affinity, which makes the role, in effect, an audience builder for the talent market.

    The payoff works in two directions, it creates a strong, durable inbound channel, which is the obvious benefit, but it also makes outbound land. When candidates are drowning in AI-generated cold approaches, the company that has already built credibility and community does not read as one more stranger in the inbox. It reads as a name worth a reply, which turns advocacy into the thing that makes outbound cut through, builds champions and creates genuine desire before a recruiter ever reaches out.

    This is not a prompt to rush out and hire the role tomorrow. It is a recognition that the direction is set: the competency comes first for everyone, and the dedicated role arrives for the companies that get far enough ahead.

    Why It Usually Fails, and How It Takes Root

    None of this is new as an idea, and that is exactly why scepticism is fair. Most TA leaders have watched a talent community or a careers blog launch with real energy and quietly fade within a year. The pattern of failure is consistent. Advocacy gets treated as a project for a quarter or two, owned by everyone and protected by no one, and the moment hiring spikes the recruiters running it are pulled back to the busy work that carries a deadline. A nice-to-have loses every time it competes with a live req.

    What changes the maths is the active load lifting, though not as cleanly as the optimists suggest. In most organisations the time AI frees does not quietly return to the recruiter to spend on community work. It gets banked by the business as efficiency, and on a lean team it tends to vanish into the extra reqs each person now carries. The honest position is that this time is contested, not gifted. The opportunity is real, but capturing it means deliberately ring-fencing a portion of the recovered hours and defending it against the next hiring spike, rather than assuming a gap will open on its own. Advocacy that waits for spare time to appear will be waiting a long while.

    The teams that make it stick tend to start the same way. One recruiter, usually the most naturally connected or community-minded on the team, takes a few small steps: showing up in a community that matters, publishing something genuinely useful, nurturing a handful of relationships that have nothing to do with an open role. It stays light at first, but it is protected rather than optional and measured rather than assumed. As the load continues to lift and the early returns appear, it formalises, until in the most advanced functions it concentrates into the dedicated role described above. The companies that have committed properly, with someone genuinely accountable rather than a side project bolted onto a full desk, are the ones already seeing it pay off.

    The difference between the graveyard and the advantage is rarely the idea. It is whether the work survives contact with a busy quarter.

    The Objection Worth Naming

    Even framed as a competency, this costs something real. It asks for time, attention and a deliberate decision to invest hours that are not tied to a live requisition, and the fair question is how to defend that to a CFO. The answer is the same one DevRel used to earn its budget: not an immediate number, but a clear account of where the slow money comes from.

    Advocacy lowers the cost of attention, because outreach to a candidate who already knows and trusts the company no longer competes with the dozens of cold pitches they delete each week. It shortens future cycles, since the person who attended an event two years ago needs no convincing that the company is worth a conversation. It protects the reputation that quietly decides whether the next ten roles are straightforward or brutal to fill. And it turns rejected candidates into a source of referrals rather than a reputational risk. The error is treating advocacy as a cost with no return, when it behaves far more like a balance sheet asset, invisible in this month’s time to fill and decisive in next year’s.

    Pipelines Reset, Ecosystems Compound

    A pipeline moves in one direction, toward a single outcome, and it empties the moment that outcome is reached, which is why every hiring cycle can feel like starting from zero. An ecosystem behaves differently, because people move in and out of it over time. They learn from the company, refer others, become customers, leave and return. A software company does not treat every developer at a conference as an immediate sale, because it understands that a healthy community produces value for years, and talent behaves the same way.

    Someone who joins a webinar today might be a hire in three years. Someone rejected this week might be a hiring manager who shortlists the company next. Someone who never joins at all might still recommend the best engineer hired all year, simply because their experience was decent when it did not have to be. Those relationships hold value even when they produce no immediate hire, and where a pipeline discards that value, an ecosystem banks it.

    A Scoreboard That Reflects the Work

    When the work changes, the scoreboard has to change with it. Efficiency metrics describe how cheaply people were processed, and they say nothing about whether the market trusts the company. Alongside time to fill, a modern function watches the health of its relationships: how engaged its talent community is and whether it is growing, how many former candidates return, how many hires already knew the company before they applied, how many referrals come from people who were never hired, and how trusted the company is inside the specific talent segments it depends on. These indicators move slowly and resist a clean dashboard, but they are the leading signals of whether hiring gets easier or harder over time, which is the question efficiency metrics never answer.

    Where Advocacy Sits in a Modern TA Function

    Candidate advocacy is best understood not as a minor upgrade to recruiting but as a peer capability alongside two others that mature functions already invest in. Employer Branding shapes how the company is perceived and tells its story. Talent Intelligence reads the labour market, the availability of skills and the activity of competitors, and informs the strategic calls. Candidate Advocacy builds the relationships, creates the value, nurtures the community and represents the candidate inside the building. Together they move Talent Acquisition past requisition delivery and into continuous market engagement, turning a function that once only reacted to hiring needs into one that actively shapes where the company stands in the talent market.

    The shift is easiest to see side by side.

    Traditional Talent AcquisitionStrategic Talent Acquisition
    Fills rolesBuilds talent ecosystems
    Manages pipelinesNurtures communities
    Measures hiresMeasures trust and engagement
    Serves hiring managersRepresents both business and talent
    Reacts to vacanciesEngages the market continuously
    Optimises processCreates long-term advantage

    From Service Desk to Market Interface

    For decades, Talent Acquisition has been run as an internal service desk, with hiring managers and executives as its only customers, and that definition is too small for where the market is heading. As AI absorbs the active load, the teams that pull ahead will not be the ones with the largest sourcing operation. They will be the ones the market already trusts before a role is posted, the teams that listen, educate and contribute continuously and hold relationships that exist whether or not a vacancy is open.

    Developer Relations changed the relationship between software companies and developers by replacing transactions with trust, and that trust became an advantage competitors could not buy their way past. Candidate advocacy can do the same for employers and talent. In a market where skills are scarce, reputation travels in seconds and AI can automate most of the mechanics of hiring, it may prove one of the most valuable competencies a talent function can hold.

    Building the Competency Without Building the Headcount

    Most leaders already believe in this. What they lack is the capacity and the infrastructure to make it real while still hitting their reqs.

    It is worth being straight about what an outside partner can and cannot do here, because advocacy is the least outsourceable capability in all of Talent Acquisition. The relationship itself cannot be contracted out. The community, the brand and the voice that carries a candidate’s experience back into the business all have to be owned internally, because the moment they are visibly outsourced they stop being authentic and stop working. Anyone selling a fully outsourced advocacy function is selling the one thing that only lands when it is genuinely yours.

    What a partner can do is clear the runway so the capability has room to take root. That is the gap TA.guru closes.

    The ownership stays with you. The capacity, the craft and the scaffolding are where we help.

    The companies that treat talent like an ecosystem rather than a pipeline will not just hire more easily. They will own a reputation in their market that no competitor can shortcut. Reputation compounds, and the best time to start building it was before you needed it. The second best time is now.

    Let’s talk about how to free the capacity and build the craft, while the relationship stays yours.

    Talent Acquisition has spent six years on a rollercoaster, from the hiring boom of 2020 and 2021 to the deep correction of 2023, and on into the leaner, AI-assisted, more scrutinised function of today. Inside all that reshaping is a question every TA leader is now answering, whether they realise it or not: what is the right recruitment model for hiring in this company, at this stage, for this kind of role?

    Most TA leaders pick a primary delivery model and stick with it. The leaders getting hiring right in 2026 are consistently weighing up all four: in-house for the core, embedded for the surge and the specialist build, RPO for genuinely high-volume repeatable work, and agency for the scarce and the confidential.

    What follows is a framework for choosing between them.

    Why the recruitment model question matters more now

    Six years ago the decision was largely binary: build internal, or use agencies. The middle of the market was thinner, RPO was mostly the preserve of enterprise, and embedded was still a niche concept being championed by a small group of founders.

    Today the landscape is different. Embedded partnerships have professionalised, AI has changed what a single recruiter can realistically own, and hiring volumes swing with funding rounds and product cycles rather than following predictable headcount plans. The cost of getting the model wrong has also gone up, because TA budgets are scrutinised in a way they were not when capital was cheap.

    The model you pick shapes who owns the candidate experience, where your domain knowledge accumulates, how fast you can flex, and how much you spend per hire over a three-year window. Picking by default, or by historical habit, is one of the most expensive mistakes a TA leader can make right now.

    In-house: when permanent talent teams are the right call

    A 250-person Irish SaaS company hires 10 to 20 engineers a year, year after year. Two perm recruiters, embedded into the engineering org, attending the standups, running the EVP work, quietly outperform what any external model could do for the same spend.

    That is in-house at its best, and it is still the right answer in many companies. Permanent hiring works when demand is consistent, when the company wants to build genuinely deep internal business and TA relationships over time, when headcount is properly budgeted, and when inbound interest is strong enough that a permanent recruiter can build a real network and an evolving understanding of the market.

    Done well, an in-house team becomes a strategic muscle. A perm recruiter who has spent two years hiring a company’s Security Engineers in Dublin knows the candidates, the competitors, the comp benchmarks, and the cultural traps, and that depth is hard to replicate with anyone arriving on a short-term basis.

    Where in-house works less well is when the shape of demand does not justify a permanent hire. Bringing on a perm recruiter for a six-month surge means either carrying excess cost when volume drops, or making the role redundant inside a year, and the internal signal that sends to the rest of the company is worse than most leaders admit.

    Where it goes wrong. A Series B company hires three perm recruiters to deliver an aggressive 12-month plan. Funding extends, hiring slows in month seven, and two of the three are made redundant by month ten. The cost is not just severance, it is the message to everyone else about how secure roles really are.

    Embedded: when you need in-house quality without a permanent commitment

    A scaling fintech raises a Series C and needs 40 hires in nine months across engineering, product and GTM. An embedded partner deploys three recruiters and a coordinator within two weeks, integrates with the existing single in-house recruiter, and steps down when the surge ends. Headcount cost stays contained, the in-house recruiter keeps the long-term relationships, and the function comes out of the surge stronger than it went in.

    That is the model working as intended, and it is the kind of scenario embedded is genuinely built for. Embedded is also the model most TA leaders are least clear on, partly because the term has been stretched to cover everything from glorified contract recruiters to genuine consulting-led partnerships. The version worth talking about is the latter.

    It works when you need the quality, ownership, and integration of an in-house recruiter, but the shape of demand does not justify a permanent hire. That covers surge hiring tied to a funding round or product launch, building a new function from scratch, backfilling a Head of Talent or senior recruiter gap without a three-month delivery vacuum, or running hiring against a frozen headcount line where consulting spend is the only available route.

    The model also tends to bring a layer of value pure delivery does not. A good embedded partner is looking across the function, spotting process gaps, suggesting tooling changes, sharing what they have seen work elsewhere, and quietly improving how the TA function operates while the hires are being made. That consulting dimension is what separates a genuine embedded engagement from a high-end contract recruiter, and it is where most of the longer-term value sits.

    It is worth being honest about where embedded does not fit, because we have walked away from scopes ourselves when it was clearly the wrong call. It does not fit when scope is too thin to justify the ramp time, and one or two hires rarely make sense. It does not fit when a company is using embedded as a permanent substitute for ever building an internal TA function, because the dependency builds and the cost compounds. And it does not fit when the work is genuinely commoditised, high-volume, and process-led, because that is RPO territory.

    Where it goes wrong. A company brings in an embedded partner for a single Senior Engineer hire. Two weeks of context loading, one offer, no chance to build process depth or stakeholder trust. The work gets done, but the model was the wrong tool for the job.

    RPO: when scale and standardisation matter most

    A global financial services firm hires 1,200 graduates a year across eight countries. An RPO partner runs the entire programme end to end, with standardised assessment, reporting and onboarding. The unit cost is lower than any in-house model could achieve, and the consistency is exactly what the programme needs.

    That is RPO in its lane, and the model genuinely works in the right context. Recruitment Process Outsourcing has a reputation problem, much of it deserved, but it is built for high-volume, repeatable hiring where process standardisation, reporting infrastructure, and unit economics matter more than bespoke craft.

    Where it earns its place is in contact centres, retail, graduate programmes, warehouse and logistics, and certain volume engineering programmes where the same role is being filled hundreds of times. It also works for multi-country, multi-year hiring commitments where the RPO provider’s scale beats anything a single in-house team could realistically build.

    Where RPO falls down is when a scaling tech company picks it because the per-hire number looks cheaper on paper. The race to the bottom on cost has been a defining feature of the RPO market for a decade, and the result is often quality compromises that are invisible on the invoice but very visible in the candidate experience, in hiring manager satisfaction, and in the calibre of people who actually start. Tech hiring rarely fits the model, because the roles are too varied, the candidates too discerning, and the EVP nuance too important to justify the operational machinery RPO is built around.

    The honest test for RPO is volume and repeatability. If you are hiring 500 similar roles a year across multiple countries it deserves serious consideration, and if you are hiring 50 varied roles a year in a competitive tech market it almost certainly does not.

    Where it goes wrong. A 400-person tech scale-up signs an RPO deal to cut recruitment costs. Within six months hiring manager NPS has dropped, candidate withdrawal rates are climbing, and the senior engineers the company actually needed are being filled by agencies on top of the RPO fee. The model was the wrong fit for the work.

    Agency: a narrow lane that still earns its fee

    A CTO is leaving and the search needs to be confidential. An executive search firm with a 15-year network in CTO placements runs the process discreetly, presents three candidates, and the role is filled in eleven weeks. The fee is a fraction of the cost of getting that hire wrong.

    That is where agency still earns its keep, and there is no in-house or embedded model that competes with it for that kind of work. Agencies have spent years being talked about as if they are on their way out. They are not, but the lane in which they belong has narrowed considerably.

    Agency is the right call for one or two roles in a company, particularly when those roles are scarce, outside the in-house team’s domain expertise, or confidential. That covers the niche specialist hire where the agency has spent a decade building the network, the CFO or executive search where market mapping and a discreet approach matter more than process, a confidential replacement of an incumbent, or a role outside your team’s domain where building the search capability internally would take longer than the hire itself.

    Where agency stops earning its fee is when it becomes the default for everything, usually because the internal function is under-resourced and there is nowhere else to send the work. Paying 20 to 25 percent on roles a properly equipped in-house or embedded team could fill is one of the clearest signs that the operating model itself needs revisiting.

    Where it goes wrong. A company with one overstretched in-house recruiter defaults to agencies for every senior hire because there is no capacity to run them properly. Annual agency spend creeps past €400,000, none of those roles are genuinely scarce, and the real problem is structural rather than the agencies themselves.

    Recruitment Model Summary

    Six variables matter most when choosing between the four models: volume, predictability, time horizon, skill scarcity, budget structure, and strategic importance. The table below pulls the argument together at a glance, and is a useful starting point when you are weighing a specific hiring need against the available options.

    In-house (perm)EmbeddedRPOAgency
    Hiring volumeSteady, ongoingSurge or focused buildHigh and repeatableLow, 1 or 2 roles
    PredictabilityPredictable pipelineDefined project windowPredictable at scaleOne-off, opportunistic
    Time horizon12+ months3 to 12 monthsMulti-year contractSingle search
    Skill scarcityMainstream rolesSpecialist or new functionVolume, standardisedScarce, niche, executive
    Budget structureHeadcount approvedOpex / consulting linePer-hire or managed feeContingent or retained
    Strategic importanceCore, compoundingHigh, time-boundOperational, scaledHigh but isolated

    The portfolio mindset

    The strongest TA functions in 2026 are not the ones with the biggest in-house team or the slickest RPO contract. They are the ones whose leaders have stopped thinking about the model decision as a single answer and started thinking about it as a portfolio question.

    In-house carries the core, embedded carries the surge and the build, RPO carries the volume work that genuinely belongs in a standardised process, and agency carries the rest.

    The test worth running on your own model is a simple one. Look at the last 12 months of hiring and, for every hire, ask whether the model that delivered it was actually the right one for that specific role, or just the model that was already in place. If the second answer is true more than a handful of times, the portfolio needs rebalancing.

    That review should happen at predictable moments: every six months as a standing exercise, after every funding event, and after every leadership change in TA or the wider business. The model is not something you set once and forget, it is something you tune deliberately as the company changes.

    If running that test yourself sounds useful, we would be happy to do it with you. At TA.guru we run informal 30-minute hiring reviews with TA leaders, walking through the last 12 months of hires and where each delivery model is and is not earning its place. No pitch, and useful even if we never work together. For teams that want to go deeper, we also run a more formal portfolio audit with a written set of recommendations. Get in touch if either would help.

    Get In Touch

    Turn your hiring function into an agile recruitment engine with embedded expertise, on-demand enablement, and AI-powered knowledge tools.

    Solutions Use Cases Case Studies Plans About Us Blog Careers

    2026 TA guru. All rights reserved. Terms Of ServicePrivacy Policy