---
title: "27 questions to ask on an ATS demo"
description: "Ask these 27 ATS demo questions to test recruiting workflows, usability, reporting, integrations, security, AI, implementation, support, and pricing."
canonical: "https://recooty.com/resources/blogs/questions-to-ask-on-an-ats-demo"
author: "Recooty Team"
date: "2026-09-15T00:00:00+05:30"
updated: "2026-09-15T00:00:00+05:30"
image: "https://recooty.com/resources/blogs/media/2026/09/09-questions-to-ask-on-an-ats-demo-f4ed4090076d.png"
---

# 27 questions to ask on an ATS demo

The best [ATS](https://recooty.com/applicant-tracking-system) demo questions make the vendor perform your real hiring work. Ask about common tasks, exceptions, data movement, permissions, AI decisions, support, and cost.

For a current comparison, see this guide to [AI-powered applicant tracking systems](https://recooty.com/resources/blogs/best-ai-powered-applicant-tracking-systems). Record the answer, the evidence shown, and any limitation so each vendor can be compared on the same basis.

I would send the scenarios before the meeting. That gives the presenter time to configure a useful demonstration and leaves less room for a generic product tour.

## Key takeaways

- Give every ATS vendor the same representative job and candidate journey.
- Ask the presenter to show each workflow live instead of describing it.
- Include recruiters, hiring managers, HR operations, and technical reviewers as needed.
- Test awkward cases such as duplicates, rescheduling, reopened jobs, and failed integrations.
- Separate current capability from configuration, custom work, integration, and roadmap plans.
- Score usability and evidence during the demo while details are fresh.

## Which workflow questions should you ask?

Workflow questions reveal how the ATS handles ordinary recruiting from requisition to hire.

Teams comparing [recruiting software](https://recooty.com/) can use this overview to assess which workflow fits their hiring process. Ask the presenter to use realistic fields, stages, and users rather than a polished sample account that hides setup work.

1. **How does a manager request and approve a job?** Ask to see routing, comments, changes, approval history, and what happens when an approver is absent.
2. **How do we create jobs from templates without carrying old errors forward?** Check field defaults, locked content, version control, and local variations.
3. **How are jobs published and updated across our careers page and job boards?** Confirm supported channels, source tracking, refresh timing, and editing limits.  
When the role is ready, you can [post a job for free](https://recooty.com/free-job-posting) to start reaching candidates.
4. **What does the mobile application experience look like?** Complete an application from a phone and test document upload, validation, accessibility, and confirmation.
5. **How does the system handle one candidate applying for several jobs?** Look for one person record with separate application histories, permissions, and outcomes.
6. **How are duplicate candidate profiles detected and merged?** Ask what data is preserved and who can reverse or audit a merge.
7. **Can we configure different pipelines by role, country, or business unit?** Check templates, required stages, exceptions, and reporting consistency.
8. **How do recruiters search and rediscover past candidates?** Test ordinary terms, filters, tags, previous activity, consent, and retention boundaries.

## Which collaboration and candidate experience questions matter?

These questions show how occasional users and applicants experience the system. A capable recruiter interface cannot compensate for managers who avoid feedback tasks or candidates who struggle to apply.

1. **What does a hiring manager see when asked to review a candidate?** Count the steps and check access to relevant evidence, comments, and prior decisions.
2. **How are interview scorecards created and completed?** Test criteria, rating scales, evidence fields, reminders, and protection from other interviewers' opinions.  
Use an [interview question generator](https://recooty.com/tools/interview-question-generator/) to prepare role-specific questions before the conversation.
3. **How does interview scheduling work across calendars and time zones?** Include a panel, reschedule, cancellation, reminder, and video meeting link.
4. **Can recruiters send personal and template-based emails from the candidate record?** Check sender identity, replies, history, attachments, scheduling, and bulk controls.
5. **What can candidates do through a portal or scheduling page?** Review status information, withdrawal, rescheduling, privacy requests, and accessibility.
6. **How does the ATS prevent candidates from being forgotten in a stage?** Ask about stage age, overdue tasks, alerts, dashboards, and escalation.
7. **How are agencies, referrals, and sourced candidates handled?** Confirm ownership, source credit, duplicate rules, communication, and permissions.

## Which reporting and integration questions should you ask?

Reporting depends on clean workflow data, while integrations depend on specific fields and triggers. Ask for live results and technical detail instead of accepting a dashboard image or partner logo.

1. **Can you build our required recruiting reports during the demo?** Use real filters for time to hire, source, stage conversion, open jobs, and recruiter workload.
2. **Can we inspect and export the records behind a chart?** Confirm file formats, field coverage, scheduled delivery, and permission controls.
3. **How does the ATS connect with our HRIS or onboarding system?** Ask which fields move, in which direction, at what trigger, and how failures are reported.
4. **What do your API and webhooks allow us to do?** Check authentication, documentation, rate limits, events, testing, monitoring, and plan restrictions.
5. **How will our historical data be migrated?** Ask about mapping, cleaning, attachments, activity history, validation, failed records, and ownership.
6. **How do we export our data if the contract ends?** Confirm timing, formats, attachments, relationships, fees, and deletion after return.

## Which security and AI questions belong in the demo?

Security and AI questions need concrete answers because the ATS stores personal data and may influence candidate review. Bring the right technical or legal reviewer if these areas affect approval.

1. **How do roles and permissions work in practice?** Create a recruiter, manager, interviewer, and report viewer, then test what each can see and change.
2. **Which security and privacy controls can our administrators configure?** Review two-factor authentication, access, retention, deletion, audit history, hosting, and subprocessors.
3. **What data does each AI feature use, and where does it go?** Separate job data, candidate data, customer content, model training, storage, and third-party processing.
4. **Why did the AI produce this match, score, summary, or recommendation?** Use a sample with missing or ambiguous information and examine the explanation and correction path.
5. **Can AI trigger a rejection or other consequential action without review?** Confirm default behavior, configuration, logging, user approval, and the ability to disable features.

## Which commercial question should close the demo?

Pricing should be tied to the configuration just shown. A headline amount has little meaning if required integrations, support, users, or AI functions sit in another plan.

1. **What is the full three-year cost for this exact scope?** Include subscription, implementation, migration, integrations, API access, careers page work, training, support, usage charges, added users or jobs, and renewal assumptions.

## How should you score the answers?

Use a simple scale and record evidence. For example, score each item from zero to four: unavailable, workaround required, partly meets, meets, or exceeds the requirement.

Add three notes beside every score:

- Evidence shown during the demo
- Limitation or dependency
- Follow-up owner and due date

Do not average away a failed launch requirement. A high overall score cannot make a missing HRIS handoff or required permission acceptable.

## What should you ask Recooty to demonstrate?

For Recooty, use the same scenarios and ask to see one-click distribution to more than 250 job boards, the no-code careers page, customizable pipelines, scorecards, scheduling, talent pools, analytics, access controls, and the relevant integrations.

Test AI Candidate Matching and explainable resume scoring with your own job criteria. Ask the presenter to show strong and weak match reasons, then change or correct candidate information and review the result.

Our [guide to choosing an ATS](https://recooty.com/resources/blogs/how-to-choose-the-right-ats-for-your-business) can help you define the shortlist before demos begin.

## Frequently asked questions about ATS demos

### How long should an ATS demo be?

Allow enough time to complete your priority scenarios and discuss limitations. A focused first demo may take 45 to 60 minutes, while a technical or final validation session can examine integrations, security, reporting, and implementation separately.

Do not compress hands-on questions into the last five minutes.

### Who should attend an ATS demo?

Include the project owner, a frequent recruiter user, and a representative hiring manager. Add HR operations, IT, security, legal, finance, or procurement for sessions covering their requirements.

Keep each meeting small enough for participants to ask questions and record evidence.

### Should vendors receive questions in advance?

Yes. Sending scenarios in advance encourages a relevant demonstration and gives the vendor time to use suitable sample data. It also makes comparison fair because every presenter receives the same brief.

Reserve a few unplanned exception questions to see how the product behaves outside the prepared path.

### Is a demo enough to choose an ATS?

No. Use a trial or sandbox where possible, review documentation and contract terms, check integrations and security materials, speak with relevant customers, and validate total cost.

A demo proves that a skilled presenter can perform a task. User testing shows how your own team handles it.

## Structured data

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Article",
      "headline": "27 questions to ask on an ATS demo",
      "description": "Give every ATS vendor the same representative job and candidate journey. Ask the presenter to show each workflow live instead of describing it. Include recruiters, hiring managers, HR operations, and technical reviewers as needed. Test awkward cases such as duplicates, rescheduling, reopened jobs, and failed integrations. Separate current capability from configuration, custom work, integration, and roadmap plans. Score usability and evidence during the demo while details are fresh.",
      "inLanguage": "en",
      "author": {
        "@type": "Organization",
        "@id": "https://recooty.com/#organization",
        "name": "Recooty"
      },
      "publisher": {
        "@type": "Organization",
        "@id": "https://recooty.com/#organization",
        "name": "Recooty",
        "url": "https://recooty.com/",
        "logo": {
          "@type": "ImageObject",
          "url": "https://recooty.com/wp-content/uploads/2020/10/recooty-logo.png"
        }
      },
      "datePublished": "2026-09-15",
      "dateModified": "2026-09-15",
      "@id": "https://recooty.com/resources/blog/questions-to-ask-on-an-ats-demo#article",
      "url": "https://recooty.com/resources/blog/questions-to-ask-on-an-ats-demo",
      "mainEntityOfPage": {
        "@type": "WebPage",
        "@id": "https://recooty.com/resources/blog/questions-to-ask-on-an-ats-demo#webpage"
      }
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "How long should an ATS demo be?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Allow enough time to complete your priority scenarios and discuss limitations. A focused first demo may take 45 to 60 minutes, while a technical or final validation session can examine integrations, security, reporting, and implementation separately."
          }
        },
        {
          "@type": "Question",
          "name": "Who should attend an ATS demo?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Include the project owner, a frequent recruiter user, and a representative hiring manager. Add HR operations, IT, security, legal, finance, or procurement for sessions covering their requirements."
          }
        },
        {
          "@type": "Question",
          "name": "Should vendors receive questions in advance?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. Sending scenarios in advance encourages a relevant demonstration and gives the vendor time to use suitable sample data. It also makes comparison fair because every presenter receives the same brief."
          }
        },
        {
          "@type": "Question",
          "name": "Is a demo enough to choose an ATS?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "No. Use a trial or sandbox where possible, review documentation and contract terms, check integrations and security materials, speak with relevant customers, and validate total cost."
          }
        }
      ],
      "@id": "https://recooty.com/resources/blog/questions-to-ask-on-an-ats-demo#faq"
    },
    {
      "@type": "ItemList",
      "name": "27 questions to ask on an ATS demo",
      "numberOfItems": 3,
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "How does a manager request and approve a job? Ask to see routing, comments, changes, approval history, and what happens when an approver is absent."
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "How do we create jobs from templates without carrying old errors forward? Check field defaults, locked content, version control, and local variations."
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "How are jobs published and updated across our careers page and job boards? Confirm supported channels, source tracking, refresh timing, and editing limits."
        }
      ],
      "@id": "https://recooty.com/resources/blog/questions-to-ask-on-an-ats-demo#item-list"
    }
  ]
}
```