
Gem was mostly used by me during the recruiting process, where centralizing candidate sourcing activities, tracking communication, and organizing pipelines were the key concerns. My daily routine mostly consisted of analyzing the candidates' profile, following the sequence of outreach activities, and tracking follow-ups within my various hiring pipelines.
One of the operational conveniences of using Gem was getting the ability to see all of my candidates' communications history and their stage within outreach without having to track those manually through email chains and spreadsheets. While on hiring streaks, I would constantly check response activities, recruitment notes, and candidate pipeline stages to organize my follow-ups and prevent duplicate communications.
Additionally, I used Gem while coordinating sourcing activity on multiple hiring campaigns concurrently. Review collected by and hosted on G2.com.
The platform also requires some time to be configured appropriately, depending on the recruiting process flows in place. Initially, I needed to take more time understanding the interactions between sequence, candidate status, and integration since any slight variation in processes could impact reporting and candidate management.
Another problem associated with using the platform is ensuring that the pipeline data remains clean when several recruiters make changes at the same time. In the absence of proper workflow management, duplicating candidates or even out-of-date statuses may occur.
There are also some complex workflows for reporting and filtering that come with large recruiting pipelines. Review collected by and hosted on G2.com.