How to assess candidates without leaving the portal you already use
You already post vacancies on a job portal and get the flow there. We explain how to add assessments to the same flow, without switching tools or duplicating work.
You don’t need to switch tools to assess candidates. If you already receive applications from a job portal like elempleo, Bumeran, Multitrabajos, or HiringRoom, you can add assessments to the same flow: Kokoro connects to the portal you already use—according to your implementation stage—so you can assess without leaving it or duplicating tasks.
The problem isn’t the tool, it’s the jump between tools
Most selection teams already have their operation set up on a job portal. That’s where they post the vacancy, where applications arrive, where they manage the first contact. The portal works, and replacing all of that with a new system isn’t realistic or necessary.
The pain shows up when, in order to assess, you have to leave the portal: export lists, copy emails, send tests through another channel, then cross-reference results by hand. Each jump between tools adds friction, typos, and candidates lost along the way. The right question isn’t “what tool do I use to assess?” but “how do I assess without leaving where I already work?”.
Assessing within the same flow you already have
Kokoro starts from a premise: the portal is an ally, not something to replace. The portal does what it does very well—bringing in a large flow of applications—and Kokoro adds a layer on top of that flow.
In practice, that means the invitation to assess travels with the portal’s own process, according to your implementation stage. The candidate who applied through the portal receives the assessment within that journey, and you get back a comparable description without having to build a parallel process.
What changes and what stays the same
Assessing from the portal doesn’t force you to relearn your operation. Here’s what stays and what gets added:
| What stays the same | What gets added |
|---|---|
| You post on the same portal | An assessment connected to that flow |
| You receive applications where you always have | Comparable signal about applicants |
| Your team works in the familiar environment | Information to organize whom to look at first |
| The portal remains the owner of the flow | A layer that helps make sense of that flow |
The idea is for the day-to-day to feel familiar. You’re not migrating: you’re adding a signal on top of what you already have.
A connection that depends on your stage
It’s worth being clear on one point: the connection with each portal depends on the portal and on your implementation stage. It isn’t a full integration available for any scenario with a single click. Depending on your case, the assessment can connect more or less automatically to the portal’s flow, and that’s configured together with the team.
What matters is that the destination is always the same: that you assess from the place where you already receive your candidates, with the least possible friction and without treating the portal as a competitor, because it isn’t one.
Want to see how assessing before interviewing works?
Free trialIf your operation already lives on a job portal, it makes no sense to pull it out of there to assess. You can see how Kokoro connects to the portal’s flow in integrations, or learn how the assessment works in the product.