
I mainly use Mercor for recruiting and sourcing specialized talent, particularly for technical and project-based roles. What I like most is the speed of finding relevant candidates. The matching and profile search make it easier to narrow down people based on specific skills and experience instead of going through hundreds of unrelated profiles. I also like that it gives us access to a broader talent pool, which is particularly helpful when we're working on niche technical roles with tight timelines. Mercor mainly helps us reduce the time spent sourcing candidates for specialized roles by allowing us to find people with specific skills and relevant experience more quickly. It has been useful when we have tight hiring timelines because it gives us another channel to build a qualified candidate pool without starting the search from scratch. The matching feature saves me a lot of time during the initial sourcing stage. If I am looking for someone with a specific set of technical skills, I can narrow the pool quickly instead of reviewing a large number of unrelated profiles. It's especially useful when a role needs to be filled quickly because I can get to potentially relevant candidates faster and spend more time on actual screening and outreach. The initial setup was quite straightforward, and there wasn't a major learning curve. We could start searching for candidates fairly quickly, and once we got familiar with the matching and filters, it fit into our existing recruiting workflow without much trouble. Review collected by and hosted on G2.com.
One area that could be improved is the consistency of candidate matches. Sometimes the results look relevant based on keywords, but after reviewing the profile, the experience isn't quite as close to the role as expected. I'd also like more control over the matching filters, especially for niche technical skills and years of experience. That would help reduce the time spent manually screening borderline profiles. I would like the matching to weigh actual hands on experience more heavily instead of relying mainly on skill keywords. For example, someone who mentions AWS once shouldn't rank the same as someone who has several years of AWS project experience. More detailed filters for years of experience, specific technologies, role level and recent experience would make the results more accurate and reduce manual screening. Review collected by and hosted on G2.com.