How to Source Candidates for International Remote Roles

This guide is for recruiters and sourcers who find talent for foreign companies, agencies or Nigerian startups hiring across borders. It covers the intake questions that decide where you can look, search syntax that works on LinkedIn, Google and GitHub, outreach that gets replies across time zones, the data protection rules that apply when you contact strangers in the UK, the EU or Nigeria, and how to keep a pipeline that holds up when the hiring manager changes their mind. The examples are written from Lagos, with real time-zone maths, because that's where many of our readers do this work.

Quick answer

Sourcing for an international remote role means finding and contacting suitable people, usually passive candidates, in the countries where the employer can actually hire them. Confirm the hiring model (employer of record, contractor or a local entity), the required time-zone overlap and the pay band first. Then run country-specific Boolean, X-ray and GitHub searches, send a short message that states location eligibility and pay, give privacy information on first contact, and screen for eligibility early.

What sourcing means in international remote hiring

Sourcing is the part of recruitment that finds and engages candidates before they apply. A recruiter then runs the process: screening, interviews and the offer. In smaller teams one person does both. In larger ones, a sourcer hands warm candidates to a recruiter.

International remote sourcing adds a variable that local sourcing doesn't have: whether this person can legally be hired where they live. A brilliant backend engineer in Accra is a wasted hour if the company can only employ people in the UK and Ireland. A role labelled "remote" can mean remote within one country, remote across a region, remote worldwide for contractors, or remote only for people who already have the right to work somewhere. If you are unsure what labels like "EMEA" mean in an ad, our guide on reading EMEA in a remote job description explains them, and the companion piece on US-only and Canada-only restrictions covers the common North American limits.

So the job has three layers:

1. Defining where you may search.
2. Finding the right people inside those borders.
3. Contacting them lawfully, in a way that suits their country, language and working day.

Start with the intake meeting: where can this hire live?

Before writing a single search string, sit down (or get on a call) with the hiring manager and get clear answers. Assumptions made at this stage tend to come back when the offer goes out.

Intake questions to ask every time

• How will this person be hired? As an employee through the company's own entity, as an employee through an employer of record (EOR, a third party that legally employs the worker on the company's behalf), or as an independent contractor? If you need to explain the difference to a candidate later, our guide to contractor versus EOR employee arrangements sets it out from the worker's side.
• Which countries are confirmed? Ask for the actual list, not "Europe" or "anywhere".
• How many hours must overlap with the team, and which hours? "Four hours with New York" rules out different places from "four hours with Berlin".
• What's the pay band, and does it vary by location? Some companies pay one global band. Others adjust pay by country. You need to know before you message anyone.
• Which languages are required, and at what level? "Fluent French" for a support role means a different talent pool from "French is a plus".
• What are the three things a candidate must have, and what is merely nice to have? Sourcers waste more time on vague must-haves than on anything else.
• Are there countries the company won't hire in? Sanctions, banking problems or past payroll trouble can rule out countries even when the role says "worldwide".

How the hiring model shapes your search area

Treat this table as a starting point for the conversation, not a rule. Every company sets its own policy, and the policy changes. Write down the confirmed answer in the requisition notes so the recruiter, the hiring manager and you are working from the same list.

Turn time-zone overlap into a sourcing map

Overlap requirements often matter more than the country list. Work them out in hours, not labels. Nigeria is on West Africa Time (WAT, UTC+1) all year, with no daylight saving, so the gap with other cities changes when their clocks change.

The same thinking applies to every candidate country, not just Nigeria. A four-hour morning overlap with New York is easy for someone in Bogotá, workable for someone in Lagos (afternoon into evening) and hard for someone in Nairobi. Make the overlap window part of your search criteria before you start, so you are not rejecting good people at the final stage.

Build search strings that work across countries

Good international sourcing is mostly good searching. The skill is knowing each platform's syntax and accepting that job titles, skills and spelling vary from country to country.

LinkedIn Boolean search

According to LinkedIn's own help page on Boolean search, LinkedIn supports AND, OR and NOT (which must be typed in capitals), quotation marks for exact phrases and parentheses for grouping. The same page says wildcards (*) and brackets or braces are not supported, and that + and - aren't officially supported, so use AND and NOT instead. LinkedIn applies the operators in this order: quotes, parentheses, NOT, AND, OR. That precedence trips people up, so wrap every OR group in parentheses.

Example (hypothetical) string for a remote customer success role open across Africa and Europe:

("customer success" OR "client success" OR "account manager") AND (SaaS OR software) AND (Zendesk OR Intercom OR HubSpot) NOT (intern OR student)

Put location in LinkedIn's location filter rather than the keyword box. Then run the same string once per country on your confirmed list, so you can see how many people each market gives you.

Allow for job titles that differ by country

The same job carries different titles in different markets. Build OR groups that cover them:

• A "software engineer" in one market is a "developer", "programmer" or "SDE" in another.
• UK and Nigerian CVs often say "programme manager". US profiles say "program manager". Include both spellings.
• French-speaking markets may use "chargé de clientèle" or "responsable relation client" for customer-facing roles. Spanish-speaking ones may use "atención al cliente". If the role needs a second language, search in that language as well.
• Seniority labels vary widely. "Senior" at a startup can mean three years. At a bank it can mean ten. Search on skills and years where you can, not only on the title.

Google X-ray search

X-ray searching uses Google to search the public pages of another site. Google's help page on refining searches documents quotes for exact matches, site: to limit results to one site or domain, a minus sign to exclude words, before: and after: for dates, and filetype: for file types such as PDF. Many sourcers also use OR in Google, though that page doesn't list it, so check your results.

Example (hypothetical) X-ray for public profiles of data engineers in Lagos:

site:linkedin.com/in "data engineer" "Lagos" (Airflow OR dbt) -jobs

filetype:pdf combined with a job title and a city can surface public CVs and portfolios. Treat anything you find this way with care (see the data protection section below).

GitHub search for technical roles

For developers, GitHub is often more honest than a profile summary because it shows actual work. GitHub's documentation on searching for users lists qualifiers including location:, language: (the main language of a user's repositories), followers: and repos: with greater-than and range operators, and created: for account age. Multi-word terms need quotation marks.

Example (hypothetical) searches:

• location:lagos language:go followers:>=20 finds Lagos-based users whose repositories are mostly Go and who have at least 20 followers.
• location:"cape town" language:typescript repos:10..60 finds Cape Town users with between 10 and 60 repositories that are mostly TypeScript.

Location on GitHub is whatever the user typed, so search variations: "Lagos", "Lagos, Nigeria", "Nigeria", "Abuja", "Port Harcourt", "Ibadan". A large share of people leave the field blank, so GitHub search is a supplement to other channels, not a complete census of any city.

Channels beyond LinkedIn

LinkedIn is the default, which is exactly why the best candidates in some markets get dozens of messages a week. Widen your mix by role.

Your own applicant tracking system (ATS) is the channel sourcers most often forget. People who reached the final round for a similar role six months ago already know the company and have been vetted. Whether you may contact them depends on what they were told when they applied, which leads to the next section. For choosing and running an ATS, see our guide to applicant tracking systems for remote recruiters.

Write outreach that works across countries and time zones

The first message decides most searches. International candidates have learned to be suspicious, and in Nigeria many have seen fake "remote recruiter" messages, so a vague message reads like a scam. Our guide on spotting fake recruiters on LinkedIn shows what candidates are looking for, and your message should pass that test easily.

What every first message should include

• Your name, the company (or "on behalf of" the client, named if you are allowed) and a link to the real careers page or vacancy.
• Where the role is open to, in plain words: "open to people living in Nigeria, Ghana, Kenya and South Africa, hired as contractors".
• The overlap hours in the candidate's time, not yours.
• The pay band and currency, if the company allows it. Senior people often ignore messages without one.
• One specific reason you contacted them: a repository, a talk, a project, a past employer.
• A low-effort next step: "Open to a 15-minute call this week?"

Example (hypothetical) outreach message

Hi Amaka, I'm Tunde, a sourcer working with [Company], a payments software company with a fully remote team. We're hiring a Senior Backend Engineer (Go) and the role is open to people living in Nigeria, hired as a full-time employee through an employer of record. The team works 9am to 1pm New York time together, which is 3pm to 7pm in Lagos from November. The band is [range] a year in US dollars. I came across your rate-limiting library on GitHub, and that's very close to what the team is building. Would you be open to a 15-minute call this week? Our privacy notice, which explains how I found your profile and how we use your details, is here: [link].

Notice what it doesn't do. It doesn't ask for a CV first, doesn't ask the candidate to pay for anything, and doesn't move to WhatsApp before the candidate chooses to.

Timing and follow-up

Send messages during the candidate's working morning, not yours. If you're in Lagos sourcing for a Pacific-time team in Manila, that means your early morning. One follow-up after four or five working days, then one final short note, is polite almost everywhere. More than that starts to look like pressure. Keep track of local public holidays: messages sent during Eid, Lunar New Year or the Christmas period sit unread.

Data protection rules when you source across borders

Sourcing means collecting personal data about people who never asked you to. Several legal regimes apply, depending on where the candidate is and where the company operates. What follows is general guidance, not legal advice. The company's privacy or legal team should sign off its own process.

GDPR: tell people how you found them

Under Article 14 of the EU GDPR, when you obtain someone's personal data from a source other than them, you must give them privacy information within a reasonable period, at the latest within one month. If you use the data to contact the person, you must give it no later than that first contact. In practice, this is why the example message above links to a privacy notice. The UK GDPR contains the same rule.

UK ICO guidance on finding candidates

The UK Information Commissioner's Office (ICO) has draft guidance on finding candidates. As of October 2026, the page says the consultation has closed and the guidance is under review after the Data (Use and Access) Act. The main points are:

• If you use publicly available information, you are a controller and are fully responsible for how you use it.
• Searching recruitment-focused platforms may be reasonable. You should not search candidates' personal social media profiles, even public ones.
• Posting a vacancy to all your followers is not direct marketing. Sending someone a direct message on social media is, so the direct marketing rules apply.

The ICO's companion page on data protection and recruitment adds that you shouldn't keep candidates' details "just in case". You may keep them for future vacancies only if you genuinely intend to use them, tell the candidates and say how long you'll keep them. The same page warns against using special category information found online, such as a disability, to make recruitment decisions.

Nigeria: the Nigeria Data Protection Act 2023

When the people you source live in Nigeria, the Nigeria Data Protection Act 2023 is relevant. KPMG Nigeria's review of the Act notes that it was signed into law on 14 June 2023 and set up the Nigeria Data Protection Commission (NDPC), replacing the earlier bureau. The Act includes data protection principles and rules on lawful processing. The safe working habits are the same as under GDPR: collect only what you need, be open about where you found someone, honour requests to be removed and don't keep data indefinitely. Check the Act's text, or your company's counsel, for the exact obligations.

A simple compliance routine for sourcers

1. Use recruitment platforms and professional sources, not personal social accounts.
2. Store sourced profiles only in the company's ATS or CRM, never in a personal spreadsheet.
3. Link the privacy notice in your first message.
4. Record the source and date for every profile.
5. Delete or anonymise people who say no, or who don't reply within the retention period your company has set.

Screen for eligibility before the hiring manager sees anyone

A sourcer's credibility rests on the hit rate of the profiles they pass on. For international remote roles, check these on the first call, before any skills discussion:

• Country of residence now, and plans to move. Someone relocating in two months may fall outside the approved list.
• Right to work, where the role needs existing work authorisation.
• Hours. Can they reliably cover the overlap window? Ask what they did in their last remote role, not just "are you flexible?"
• Pay expectation and currency. Some candidates quote in local currency and some in dollars. Settle which one you're talking about before anyone repeats a number.
• Notice period and any non-compete clauses.
• Working setup. Laptop, internet and power backup. In Nigeria that usually means an inverter or solar backup and two internet connections, such as a fibre line plus a MiFi or phone hotspot. Ask respectfully, the same way for every candidate.

Assessing whether someone can actually work well remotely is a separate skill, covered in our guide to assessing remote work readiness.

Track what works, market by market

Without numbers, international sourcing turns into guesswork. Track these in your ATS for each role and each country:

• Response rate: replies divided by people contacted.
• Interested rate: people who agree to a call divided by people contacted.
• Pass-through rate: candidates the hiring manager accepts divided by candidates you submit.
• Source of hire: which channel and which country produced the person who got the offer.

These numbers settle arguments. If the team swears there are "no good candidates in Africa" for a role but your Lagos and Nairobi submissions pass the hiring manager's screen at the same rate as London ones, you have evidence to show them. If one country gives you high reply rates but nobody fits the overlap window, drop it from that role's search.

Sourcing from Nigeria: what you bring and what to sort out

Plenty of international sourcing is done by people in Lagos, Abuja and elsewhere in Nigeria for companies abroad. Being in WAT is an advantage. You overlap fully with central Europe in winter, mostly with London, and you can reach US East Coast mornings in your afternoon.

A real example shows what employers ask for. A closed six-month contract ad for a remote Talent Sourcer at Remofirst, listed on the Octopus Ventures job board, listed LinkedIn Recruiter, Boolean search, GitHub, Lever or Greenhouse and Hunter.io as tools. It asked for two to four years of sourcing experience, ideally in startups hiring internationally, plus familiarity with GDPR. That ad was no longer accepting applications when we checked in October 2026, and the listing we opened was labelled South Africa, so read it as an illustration of the skills employers want, not as a vacancy.

Practical points for Nigeria-based sourcers:

• Tools. Paid seats such as LinkedIn Recruiter are normally provided by the employer or agency. Ask before you accept a contract that expects you to pay for your own.
• Hours. Agree core hours in writing. Sourcing for US West Coast teams can push calls past 9pm Lagos time.
• Payment. Foreign clients often pay through Deel, Remote, Payoneer or a bank transfer. Our guide on receiving dollar payments in Nigeria compares the options.
• Career path. The recruiter career guide covers the skills and progression, and the recruiter salary guide covers pay in dollars and naira. To find work doing this, see our planned guide on getting a remote talent sourcer job. For engineering-focused roles, see the guide to becoming a remote technical recruiter.

Common mistakes in international remote sourcing

• Searching before the country list is confirmed. The most common cause of wasted searches. Get it in writing.
• Copying one string across all markets. Titles, languages and spellings change, and so should your OR groups.
• Hiding the location and pay. Candidates assume the worst, or assume it's a scam.
• Messaging in your own time zone. A message that arrives at 2am lands under twenty newer ones by morning.
• Treating "worldwide" as worldwide. Ask the company which countries are excluded, because some usually are.
• Keeping sourced data forever. Old spreadsheets of CVs are a liability under GDPR and the NDPA.
• Passing on profiles without an eligibility check. One ineligible submission can cost you a hiring manager's trust for the rest of the search.

Frequently asked questions

What is the difference between a sourcer and a recruiter?

A sourcer finds and first contacts candidates, usually people who aren't actively applying. A recruiter manages the hiring process from screening to offer. In small companies one person often does both, and many recruiters start as sourcers.

Can I source candidates worldwide for a "remote" role?

Only if the company has confirmed it can hire in those countries. "Remote" often means remote within certain countries, depending on the company's entities, employer-of-record coverage or contractor policy. Get the approved country list at the intake meeting before you search.

Is it legal to message candidates on LinkedIn without their consent?

Generally yes, but you have obligations. Under GDPR Article 14, you must give privacy information no later than your first contact. The ICO's draft guidance treats direct messages as direct marketing, so those rules apply too. Link a privacy notice in the message and follow your company's legal guidance.

Which Boolean operators work on LinkedIn?

AND, OR and NOT in capitals, quotation marks for exact phrases, and parentheses for grouping. LinkedIn's help page says wildcards and brackets aren't supported and that + and - aren't officially supported. NOT is applied before AND, and AND before OR, so put every OR group in parentheses.

How do I find developers in a specific city on GitHub?

Use GitHub's user search with the location: qualifier, combined with language: and, if you like, followers: or repos: ranges. For example, location:lagos language:python followers:>=10. Search several spellings of the place, because users type their own location and many leave it blank.

Should I include salary in sourcing messages?

Yes, wherever the company allows it. A pay band and currency show the role is genuine, filter out mismatches early and get more replies from senior people. If the band varies by country, quote the one that applies to that candidate.

Can I do international sourcing from Nigeria?

Yes. Many companies and agencies hire sourcers as contractors, and Nigeria's time zone overlaps well with Europe and partly with the US East Coast. Check each vacancy for where applicants may live, because some sourcer roles are restricted to the UK, the EU or the US.

Key takeaways

• Confirm the hiring model, the approved countries, the overlap hours and the pay band before writing any search string.
• Work out time-zone overlap in actual hours for each candidate country. It often narrows the pool more than the country list does.
• Build search strings for each country, following the documented syntax for LinkedIn, Google and GitHub, with OR groups covering local job titles and spellings.
• Put location eligibility, overlap hours in the candidate's time, pay and a privacy notice link in the first message.
• Under GDPR, privacy information is due by first contact. The ICO's draft guidance advises against searching personal social media and treats direct messages as direct marketing.
• Check eligibility on the first call, and track response and pass-through rates by country.

Next steps

If you want to do this work for an international company, browse remote admin and HR roles on WorkRemote and check each listing's "where applicants may live" line before applying. After a search for "sourcer" or "recruiter", use "Get email updates" to get a free daily email of new matching jobs. Before interviews, practise with our recruiter interview questions, where you're likely to be asked to build a Boolean string live.

Sources

• Use Boolean search on LinkedIn, LinkedIn Help
• Refine Google searches, Google Search Help
• Searching for users, GitHub Docs
• Art. 14 GDPR, Information to be provided where personal data have not been obtained from the data subject (gdpr-info.eu)
• Finding candidates, Information Commissioner's Office (draft guidance)
• Data protection and recruitment, Information Commissioner's Office (draft guidance)
• Nigeria Data Protection Act 2023 review, KPMG Nigeria
• Talent Sourcer (6 months contract), Remofirst, Octopus Ventures job board