What are the red flags to watch for in a recruiting software demo?

A presenter who returns to slides whenever you ask how something works is usually covering a gap between the marketed capability and the shipped one. A refusal to load your sample data, even anonymised, suggests either parsing that struggles outside curated examples or a sales process that has never had to survive contact with real files. Answers that arrive as coming soon or on the roadmap should be treated as absent, however credible the timeline sounds. And watch what happens when someone asks an unplanned question. A team that says they will check and come back with a written answer within a day is behaving well. A team that improvises a yes is showing you how support tickets will be handled after signature, which is far more consequential than the feature you were asking about.

It is unpolished in specific ways. The presenter works inside the product for most of the session, occasionally hits a slow load or a page they need to navigate back from, and narrates what they are doing rather than reading. They are willing to say a capability does not exist, and to explain what customers do instead. They ask about your process before showing anything, and adjust the sequence to match it. They bring someone technical when the questions turn technical rather than deflecting to a later call. None of this proves the product fits, but it establishes that you are seeing the real thing. Pair that impression with a hands-on trial, since a demo can only ever show you a product being used by someone who already knows it well.

Ask for the awkward case, politely and specifically. Give them a resume in an unusual format and ask the parser to handle it live. Ask to see a candidate who applied to three roles and how the system avoids showing them as three separate people. Ask to schedule an interview where two panellists sit in different time zones. Ask for the report your leadership requests most, generated in front of you rather than shown as a screenshot. Then ask what happens when it goes wrong: how a mis-parsed record is corrected, how a rejected candidate is reinstated, how a bulk import that fails halfway is recovered. Vendors rarely rehearse error paths, so the answers are more candid. This is also the fastest way to judge the depth behind the feature list.

Pressure tactics are the clearest. Discounts that expire this week, a proposal that arrives with an incorrect user count in the vendor's favour, or reluctance to send written pricing before a further call all signal a sales culture you will still be dealing with at renewal. Vagueness about what makes the bill grow is another: any vendor should be able to state plainly whether cost is driven by recruiter seats, employee headcount, hiring volume, integrations or storage. Contract terms deserve the same scepticism, particularly automatic renewal windows, notice periods and what happens to your data after termination. Read how recruiting software pricing is structured beforehand so a confusing quote stands out as confusing rather than as normal.