A 400-person IT services firm opens eight engineering reqs in a single quarter. The Head of TA adds a screening tool that performed well in the demo. Six weeks in, screened candidates are sitting in the vendor's dashboard, not in Greenhouse. The engineering manager wants a pipeline update. The recruiter pulls two separate reports, reconciles them manually, and sends a number that's already stale. The screening tool isn't the problem. The ATS integration is.

ATS integration determines whether a new recruiting tool adds to your workflow or multiplies it. For mid-market IT hiring teams running 60 to 150 active reqs, the gap between a tool that connects nominally and one that closes the loop, pulling reqs from the ATS, screening candidates, and pushing structured results back as records, is the difference between a cleaner pipeline and a second system to maintain. Before signing any contract, these are the questions that tell you which one you're buying.

What ATS Integration Actually Means in a Recruiting Stack

ATS integration in recruiting software falls into three distinct tiers, and only one of them removes work from your team. Most vendor demos show the first two and describe them as integration.

  • Tier 1: Job posting only. The tool posts open reqs to job boards. Applications flow back into the vendor's system, not your ATS. Your recruiting team works in two places.
  • Tier 2: One-way application intake. Applications from job boards land in the ATS. Screening still happens in the vendor's tool, and results don't make it back. Your ATS record is incomplete; the recruiter bridges the gap manually.
  • Tier 3: Bi-directional with structured data passback. The tool reads open reqs directly from your ATS, processes candidates, and pushes screened results back as records, with structured data rather than a simple disposition flag. Your ATS stays the source of truth.

At 20 reqs a year, Tier 1 or Tier 2 is livable. At 80 active reqs, the manual gap compounds fast. According to HR.com's Future of Recruitment Technologies 2025-26 report, only 43% of organizations rate their TA tech stack as good or excellent, and 55% now name integration with existing systems as a top priority when selecting new recruiting technology. Teams know the integration gap is real. Most are still working around it.

The ATS Integration Questions That Matter Before You Sign

During any vendor evaluation, these six questions separate a genuine integration from a marketing claim. Ask for live demonstrations, not slide decks.

  1. Does it read open reqs directly from our ATS? If the answer is "import a CSV" or "create reqs manually in our tool," you're looking at Tier 1 at best. A real integration pulls live reqs by API.
  2. Does it push screened candidates back as ATS records? Screen results that live only in the vendor's dashboard are invisible to your ATS, your hiring manager's view, and your reporting. Ask to see a candidate record in your ATS after a screen completes.
  3. Does it pass structured screen data, not just a pass/fail flag? A disposition code tells a recruiter nothing useful. Structured data from a screening conversation, covering what the candidate said, which criteria they met, and where they fell short, makes the recruiter's review faster and the hiring manager's debrief grounded.
  4. Does it support our specific ATS? "Integrates with major ATS platforms" sometimes means three. Ask by name: Greenhouse, Lever, Workable, Bullhorn, Ashby. If your ATS is API-capable but not on their named list, ask what a custom integration requires and who owns the maintenance.
  5. Does it handle multi-board intake without duplicate records? If your team sources from LinkedIn, Indeed, Dice, and your own career page at the same time, the integration needs to consolidate applications into a single candidate record in the ATS, not create four entries for the same person.
  6. What if we don't have an ATS? Some mid-market IT teams run hiring out of spreadsheets or a shared inbox and have put off the ATS decision for years. A recruiting layer that requires an existing ATS leaves this segment behind. Ask whether the tool provides a barebones ATS for teams that don't have one.

These questions don't require a technical evaluation team. They require a demo that shows the actual data flow from start to finish.

Job Boards and the Application Intake Layer

The integration conversation is usually about the ATS, but the job board layer is where the chaos starts. When a req goes live on LinkedIn, Indeed, Dice, and a company career page at the same time, applications arrive through four channels with inconsistent data, different field maps, and no automatic deduplication. Without a structured intake layer sitting between the boards and the ATS, the reconciliation happens manually.

A recruiting tool with real ATS integration handles that intake layer: applications from every connected board flow into a single candidate record in the ATS, with source tracked. The recruiter sees one pipeline. The ATS sees complete data. The gap between job boards and the ATS is exactly where unqualified applications pile up and qualified ones get lost in the noise. Closing that gap is an integration question before it is a screening question.

For IT roles specifically, a req might draw simultaneously from LinkedIn's tech vertical, Dice, and a direct sourcing campaign. Multi-board intake without deduplication creates enough administrative overhead to slow a two-person recruiting team to a crawl. The structured screening layer for IT roles is only useful if the candidates it processes are actually reaching the ATS.

How Eximius Fits Into an Existing Stack

Eximius is built as an add-on layer, not a replacement. For teams with an existing ATS, Greenhouse integration is live, with Lever, Workable, and Bullhorn in progress; any API-capable ATS connects via a custom plan. Eximius reads open reqs from the ATS, runs Sia's structured screening conversations across chat, voice, or video, and pushes screened candidates back as records with structured data attached. The ATS remains the source of truth. Recruiters see one pipeline, in the system they already use.

For teams without an ATS, Eximius provides a barebones one: post jobs, maintain a candidate pool, screen, schedule, and shortlist without buying a full enterprise platform first. The application intake gap doesn't require a six-figure ATS to fix.

According to the 2025 Employ Recruiter Nation Report, 76% of TA leaders expect to replace or significantly overhaul their primary recruiting platform within two years. That evaluation is already underway at most organizations. The question is whether the next tool in the stack makes the ATS more useful or less central to the workflow. The integration model is the answer to that question, and it needs to be verified before the contract is signed.

Frequently Asked Questions

What is bi-directional ATS integration in recruiting software?

Bi-directional ATS integration means the recruiting tool both reads data from the ATS, such as open reqs and candidate records, and writes structured results back to it, such as screened candidates and screen outcomes. One-way integration only pushes applications in; bi-directional keeps the ATS as the live source of truth without manual data entry between systems.

How do I know if a recruiting tool's ATS integration is real?

Ask the vendor to demonstrate the end-to-end data flow in a live environment: show a req being pulled from your ATS, a candidate being screened, and the result appearing as a structured record in the ATS without any manual steps. A slide deck about architecture is not a demonstration of integration.

Does Eximius work with Greenhouse, Lever, and Workable?

Greenhouse integration is live. Lever, Workable, and Bullhorn are in progress. Any ATS that exposes an API can be connected via a custom plan. Eximius also provides a barebones ATS for teams that don't currently use one.

What happens to applications from multiple job boards when using an ATS integration?

A well-built intake layer consolidates applications from LinkedIn, Indeed, Dice, and other connected boards into a single candidate record in the ATS, with source tracked and duplicates merged. Without this layer, the same candidate can appear as separate records from each board, and reconciliation falls to the recruiting team.

Why do so many teams still struggle with ATS integration despite widespread ATS adoption?

ATS adoption is near-universal, but deep integration between the ATS and other recruiting tools is not. HR.com's 2025-26 research found that only 43% of organizations rate their TA tech stack as good or excellent, and integration with existing systems is a top evaluation criterion for more than half of organizations selecting new tools. Most tools advertise integration but deliver it at a surface level that still requires manual work to close the gap.

The integration model you choose shapes how every new tool in your stack performs for the next few years. A shallow integration means every new capability creates new reconciliation work. A deep one means your ATS gets more useful each time you add a layer. The checklist above takes 20 minutes in a demo. The decision it informs is worth the time.

Want to see what structured ATS integration looks like on your specific req volume? Book a demo and we'll run your next role through the Eximius workflow.