Choosing hiring software · 5 min read
What to ask in a hiring software demo
A demo is a sales presentation unless you take control of it. Use these questions to see how the software handles your real hiring work, and to compare vendors on the same terms.
Prepare before the demo
Most demos follow a script designed to show the best parts of the product. To get useful answers, send the vendor a short brief a few days before:
- Two or three of your real roles, with their job descriptions.
- Your hiring stages, from application to offer.
- Who will use the system: recruiters, hiring managers, interviewers, agencies.
- Your must-have requirements, in order of importance.
- The tasks you want to see done live.
Ask them to run the demo with your roles rather than their sample data. Bring at least one recruiter and one hiring manager. Agree beforehand who asks which questions, and have a scoring sheet ready. Our ATS selection checklist works well as that sheet.
Questions about fit with your process
- Can you set up our stages exactly as we described them, and change them per role?
- Show us how a new job is created from start to finish. How long does it take?
- How do applicants apply? Can they do it on a phone without creating an account?
- Can we embed our open roles on our careers page?
- How do CVs from email, careers fairs or agencies get into the system?
- Can outside recruiters or agencies work in the system, with access limited to their own roles?
- What does a hiring manager see when they log in? Can you show us that view now?
Watch the clicks, not just the answers. If the presenter needs several screens to do a simple task, your team will too, and they will be doing it far more often.
When an answer is 'yes, with a workaround' or 'that is on our roadmap', write it down exactly as said. A workaround you use every day becomes a real cost, and a roadmap item is not a feature until you can use it.
Questions about screening and shortlisting
- How does the system compare applicants with the job's requirements? Is it keyword matching or something more?
- Can we see why an applicant was scored or ranked the way they were?
- Can we edit the requirements and see the ranking update?
- How does it handle CVs in different formats and layouts?
- What stops a good applicant from being filtered out by mistake?
- Who makes the final decision: the system or a person?
If you can, run a few of your own CVs through the system, handled under your normal privacy rules, and check whether the shortlist matches your own judgment. For the thinking behind fair screening, see how to screen CVs against requirements. If Spark Careers Enterprise is on your list, ask to see an applicant's fit analysis: the score against the job's requirements, the matched and missing skills, and the short summary behind the ranking.
Questions about interviews and teamwork
- How do applicants book interviews? Can they pick from our interviewers' free times?
- Does it support live video interviews, recorded interviews or both?
- How do interviewers submit feedback? Can we use our own scorecard?
- How does the system remind people who have not given feedback?
- Can we control who sees salary details, notes and feedback?
- Which messages can we send to applicants, and can we edit the templates?
If you run structured interviews, ask the presenter to build your interview scorecard in the system during the demo. How long it takes tells you a lot about everyday use.
Questions about data, reporting and security
- Which reports are built in? Show us time in stage, time to hire and source of hire.
- Can we export all applicant and job data, at any time, in a standard format?
- Where is our data stored, and who at your company can access it?
- How do we record consent, set retention periods and delete data on request?
- Is there a log of who viewed or changed records?
- What happens to our data if we leave?
Decide before the demo which numbers you want to track, so you can ask to see them. Our guide to hiring metrics lists the ones worth measuring. Check the employment and data protection rules where you hire, and ask how the system supports each of them.
Questions about cost, setup and support
- How is pricing calculated, and what makes it change?
- What is included in setup and training, and what costs extra?
- How long does setup usually take, and what do you need from us?
- How do we reach support, during which hours, and how quickly do you respond?
- How long is the contract, what is the notice period and does it renew automatically?
- Can we run a trial with one of our real roles before signing?
- Can we speak to a current customer who hires in a similar way to us?
Ask for every price in writing, including setup, training and the cost of adding users later. A low starting price can rise quickly once more people need access. Also ask what support looks like during setup compared with afterwards, because the answer is often different.
If you speak to a current customer, ask what surprised them after they signed, what they still do outside the system and how long it took their hiring managers to use it without help.
After the demo
The hour after a demo is when impressions are strongest and details fade fastest. Follow the same steps after every vendor so the comparison stays fair:
- Score the system against your checklist the same day, while the details are fresh.
- Write down anything the vendor promised, and ask them to confirm it in writing.
- List the questions they could not answer, and send them by email.
- Ask the hiring manager who attended a simple question: would you use this every day?
- Compare scores across vendors only after every demo is done.
A good demo leaves you with clear answers, not just a good impression. If a vendor avoids a question or keeps returning to their own script, note that too. It tells you something about how they will work with you after you sign.
Your next hire, start to finish, in one place.
Free workspace. No card. Full scoring free for 7 days.