Skip to main content

Product updates – August 06, 2025: Faster Candidate Review. Criteria Weights and Versions. More Control Over Video Responses.

New updates and improvements to HiPeople.

Updated over a month ago

Faster candidate review

Speed through candidates while staying in detail view. Click back and forth — or use shortcuts — to move even faster through AI application screening data.

Make scoring truly yours

You can now assign custom weights to each AI application screening criterion — so scoring reflects exactly what matters to you. Adjust the values, watch the scores respond in real time, and shape your decisions.

We’ve also introduced criteria set versions, letting you step back in time to review previous configurations and their corresponding scores.

Process every application

AI application screening now works with Word files, as well as applications without a resume — like those created from LinkedIn, Indeed, and more. You can now process every application without any manual effort.

More control over video responses

You can now fine‑tune how candidates respond to your video questions. Set response time limits to keep answers focused, consistent, and easy to compare. Add take limits to capture authentic first impressions, just like you would in a real conversation.

Improvements

  • Search now makes it effortless to find the right candidates in your application screening view. No more scrolling.

  • Export resume screening insights with one click — ready to share, analyze, and act on.

  • New talent pool entries now trigger instant notifications, so your hiring team is always first to know when great talent appears.

  • A redesigned usage metering view keeps you aware of your credit consumption, so you’re always in control.


Fixes

  • The application screening view now appears for every member of the hiring team, exactly as it should.

  • Copying data (e.g. candidate emails) from the dashboard with Command + C now works smoothly, without clashing with dashboard shortcuts.

  • Fixe a bug where inviting large numbers of teammates caused problems.

Did this answer your question?