Source remote candidates who can work your hours

The other half of a remote search is geography that is not a single point. A role may be open to anywhere in Poland, Portugal and Argentina but not elsewhere, because those are where the client can contract, or it may be open to a continent minus three countries for tax reasons.

Multi-location search takes a set of locations, radii and exclusions and runs one query across them, combined with the usual boolean expression over skills, titles and employers. What comes back is a single ranked list rather than nine searches a sourcer has to merge in a spreadsheet.

Location groups can be saved and reused, which matters because the answer to where can this client hire is a property of the client rather than of the requisition, and re-deriving it for every new role is where mistakes get made.

A message sent at ten in the morning London time arrives at two in the morning in Manila and sits at the bottom of an inbox by the time the candidate wakes up. Sourcing teams working across zones lose reply rate to this constantly and usually blame the message.

Outreach scheduling will convert send times into the candidate's local zone, so a sequence configured to send at nine in the morning sends at nine in the morning where the candidate is, on their working days rather than yours. Follow-ups in the same sequence follow the same rule, and a candidate who has told you they prefer evenings is scheduled accordingly.

This applies across the channels the candidate has consented to, and it respects local rest days, which differ by market and are a straightforward way to look careless in the Gulf if you get them wrong.

Sourcing across borders inevitably involves professional networking platforms, and this is where a lot of recruitment tooling makes promises it should not. Surhires does not scrape those platforms, does not run background crawlers against them and does not maintain a shadow index of profiles harvested from them.

What exists is a browser extension that captures a profile the recruiter is looking at, at the moment the recruiter chooses to capture it. Every capture is an explicit human action on a page the recruiter has legitimate access to. That is a deliberate limit, and the reasoning about platform terms is set out in full on the Chrome extension page.

The practical consequence for a remote sourcing workflow is that your searchable pool grows through work rather than through bulk acquisition. That is slower. It is also the version that does not put your agency on the wrong side of a platform's terms or a data protection regulator, and it is the version we are willing to ship.

Finding a candidate in another country is the easy part. Paying them legally is where a remote placement stalls, because the client has no entity there and does not intend to open one for a single hire.

The build includes a handoff to employer-of-record partners: the placement records that engagement will run through an EOR, captures the country, the start date and the compensation, and passes a structured handoff rather than leaving a recruiter to re-key everything into a partner portal. The candidate's documents collected during the process are carried across where the candidate consents.

To be precise about what is being claimed: Surhires is not an employer of record and does not employ anyone on your behalf. It records the arrangement and passes the data. The employment relationship, the compliance obligations and the fees sit with the EOR provider and the client, and the integrations page for each partner states whether that connection is live, in development or on the roadmap.

A remote-capable candidate record carries things a local record does not: the hours they actually work, the zone they work them in, whether they hold the right to work in the countries the client can contract in, whether they are willing to be engaged through a contractor arrangement or need employment, their currency preference, and any equipment or connectivity constraints that will come up before a start date.

These are typed fields rather than notes, which is what allows them to be searched and to feed the overlap calculation. A candidate whose record says they work fourteen hundred to twenty-two hundred in Karachi is findable for a US afternoon requisition; the same fact in a free-text note is not.

The candidate database, the search, the sequences and the capture extension ship today. The remote-specific work is in build for Wave 1: overlap as a search condition, multi-location grouping, local-time send scheduling and the employer-of-record handoff.

There is no plan to add a bulk profile index, an aggregated candidate marketplace or automated platform harvesting, and that is a position rather than a gap waiting to be filled. If your sourcing model depends on buying access to a scraped index, Surhires is not the right product and we would rather say so on this page than in the fourth demo call.