Remote is about the desk, not the passport
"Remote" means you don't have to go to an office. It doesn't mean anyone, anywhere can be hired. To hire you, a company has to pay you legally where you live. That means a contract that works under local law, and often tax and social security handled through a payroll.
A company can usually do that in only three ways: through its own local company (an entity), through a third party that employs people on its behalf, or by engaging you as an independent contractor. Each option has costs and limits, so most employers choose a list of countries and stick to it.
GitLab, one of the best-known fully remote companies, is open about this in its public handbook. It says it hires in countries where it has an entity without hiring restrictions, and that it isn't currently hiring in locations that don't have an entity or a PEO (a professional employer organization). That's a remote-first company with a clear country list. Many others work the same way without saying so.
The five location types on workafro
workafro sorts every role by what its location line says. From most to least specific:
| Type | What the location says | Who can usually apply |
|---|---|---|
| Country | "Remote, Kenya", "Lagos (Remote)", "South Africa" | People living in the named country or countries |
| Region | "East Africa", "MENA", "West Africa" | People in the countries of that region |
| Africa-wide | "Africa", "Sub-Saharan Africa", "Pan-African" | People anywhere on the continent, unless the text narrows it |
| EMEA | "Remote, EMEA" | Europe, the Middle East and Africa, often with a shorter list in the job text |
| Worldwide | "Anywhere", "Worldwide", "Global" | The widest group, but limits can still apply |
We leave out roles whose location just says "Remote" with nothing else, unless another source we read lists African countries for them and the employer's own description backs that up, and roles that name only places outside Africa, such as "Remote, US" or "Anywhere in France". A role can be open to you and still not be a good bet, so read on. You can browse each country's list, for example remote jobs in Kenya or remote jobs in Ghana.
Words that narrow a location
The location line is the headline. The details are in the job text and the application form. Search the page for these phrases:
- "Must be based in", "must reside in", "must be authorized to work in": this is a hard limit.
- "We can hire in the following countries": a list, often near the end. If your country isn't on it, don't apply.
- "Within UTC-2 to UTC+3" or "overlap with 9am-5pm ET": a time zone limit, not a country limit. Our time zone overlap guide shows what these mean from African cities.
- "Candidates in X preferred": a soft preference. You can apply, but be realistic.
- A market in the title: "Account Executive, DACH", "Sales, Nordics" or "Support, Brazil" means the job serves that market. Even with an EMEA or worldwide location, these roles usually want someone based there.
Also open the application form before you write a cover letter. A "country of residence" dropdown that skips your country tells you more than the ad does.
Why payroll decides who gets hired
When a company has no entity in your country, it can use an employer of record (EOR). Deel describes an EOR as an organization that employs and pays workers compliantly on a company's behalf. Oyster says an EOR legally employs workers on behalf of another business. Remote describes hiring through its own entities and converting contractors to locally compliant employment contracts.
The company pays the EOR a fee for each person, and the EOR has to cover your country. If their provider doesn't support your country, or the cost is too high for the role, the company may say no even to a strong candidate.
The third route is a contractor agreement. It's simpler for the company, but some companies avoid it in certain countries for legal or tax reasons. Our guide to contractor vs employee remote jobs explains what each setup means for you.
Sanctions are another limit. US-based programs often exclude residents of countries under US embargo. Google Summer of Code, for example, says residents of US-embargoed countries aren't eligible. If your country is affected, check before you apply.
Worldwide often comes with hours
Plenty of "worldwide" roles still need you online at certain times. A team in New York that wants four hours of overlap from 9:00 to 13:00 Eastern Time is asking someone in Lagos to work 15:00 to 19:00 in winter, when New York is on UTC-5 and Lagos on UTC+1. For someone in Nairobi (UTC+3), the same window is 17:00 to 21:00.
That's doable for many people. It's harder for a role that wants overlap with US Pacific Time, which falls late at night across most of Africa. Read the time zone line as carefully as the location line.
A two-minute check before you apply
- Read the location line. Skip roles limited to countries where you don't live.
- Search the job text for "based", "reside", "authorized", "countries" and "time zone".
- Open the application form and look at the country list.
- Check the company's careers FAQ or handbook. Some publish where they hire.
- If it's still unclear, ask the recruiter one short question: "Are you able to hire someone based in Ghana, as an employee or a contractor?"
Never say you live somewhere you don't. Payroll, tax forms and contracts need your real address, and a mismatch found after you start can end the job. It's better to spend your effort on the many roles that can hire you in your own country. Start with all remote jobs open to Africa, and see our guide to EMEA remote jobs from Africa for the most common in-between case.
