You did IT in Lagos or Nairobi. Here's how to sell it in the US cloud market

You ran Active Directory for a bank. You kept a university's network alive through power cuts that would end an American sysadmin's career. Then you got here, sent out the résumé, and heard nothing. The experience is real. The problem is that recruiters can't read it — and reading it is a fixable problem.

New to cloud? CAMPUX is a free, build-first course. Start here →

Your IT experience from Lagos, Nairobi, or Accra counts on a US résumé — if you translate it into titles, tools, and scale that American recruiters recognize, add context lines that make your employers legible, and back it with one current certification. The honest part: some of it will not transfer, and I will show you which.

This article is for a specific person. Not the career-changer starting from zero — I have written for that reader elsewhere, in cloud computing for immigrants in the US. This one is for the person who already did the job. You administered Active Directory and Exchange at a bank in Lagos. You managed servers and the campus network at a university in Nairobi. You were the network admin for a telecom in Accra, or the one "IT Officer" who was actually four departments in one chair. You are not new to computers. You are new to American tech hiring — and American tech hiring, for all its talk of skills, mostly hires what it can read in six seconds.

The problem is legibility, not experience

Here is the mechanic nobody explains. A recruiter — often not technical — scans a résumé for a few seconds looking for pattern matches: titles they recognize, companies they can place, tools that match the job posting. Before the human even looks, an applicant tracking system may have filtered on keywords. Your résumé says "Senior Systems Officer, Zenith Bank Plc" and lists competence with tools named the way your market named them. The recruiter has never heard of the bank, cannot map the title, and does not see the exact keywords the posting used. Six seconds are up. Nothing about this judged your ability. It judged your translation.

That is actually good news, because translation is work you can do in a weekend, unlike the ten years of experience you already have. Three moves fix most of it: translate the titles and stack, add context lines for the employers, and modernize the top layer. Then there is a fourth move most guides will not touch — being honest about what does not transfer — and a fifth, using a certification as the verification layer. In order.

Move one: the translation table

US recruiters hire against a fairly rigid set of role names. Your job is to map what you actually did onto the name they are searching for — not to inflate it, just to say it in their dialect. This table is the center of this whole article.

Two notes on using this. First, the mapping goes on the résumé itself. If your official title was "Systems Officer II," write the US-legible function with the real title beside it: Windows Systems Administrator (title: Systems Officer II). That is not lying — it is translating a title into the term of art for the same work, and it is standard practice. What you must never do is upgrade the seniority: an officer who did admin work becomes an administrator, not a "Senior Infrastructure Architect."

Second, the "IT Officer who did everything" case deserves its own paragraph, because half the people reading this were that person. In most of our home markets, one person runs what a US company splits across three or four teams. On a US résumé, "responsible for all IT" reads as junior generalist — vague, unrankable. The fix is to break your one job into the US-legible roles it actually contained. Under the same employer, write bullets in clusters: the identity and server work (that was a sysadmin), the routing and firewall work (that was a network admin), the user support work (that was a service desk). Then decide which of those three lanes you are selling, and let that cluster lead. You were not "the IT guy." You were three roles sharing one salary — say so, in their language.

Move two: context lines that make your employers legible

An American recruiter knows what Bank of America is. They do not know GTBank, Safaricom, Kenyatta University, or MTN Ghana — which means, to them, your employer carries zero weight. Not negative weight. Zero. You fix this with one line of context under each employer name, and the line should carry scale, because scale is the thing a recruiter can respect without knowing the geography:

• GTBank — one of Nigeria's largest banks, serving millions of retail customers.
• Kenyatta University — one of Kenya's largest public universities; campus network serving tens of thousands of students and staff.
• MTN Ghana — subsidiary of MTN Group, the largest mobile network operator in Africa.

Suddenly "Systems Officer, GTBank" is not an unknown title at an unknown company. It is Windows administration inside a major bank's headcount, with the compliance pressure and uptime expectations that implies — and banking IT pressure is something a hiring manager anywhere understands. Use numbers you can defend: customer counts, user counts, branch counts, server counts. If you are estimating, round down and be ready to explain the estimate. Every number on your résumé is a promise you will keep in the interview.

The same one-line treatment applies to your degree. A computer science degree from Nairobi or Ibadan is a real degree; a credential evaluation (WES is the common one) turns it into something HR systems can process. I go deeper on that in cloud jobs with a foreign degree, and on the résumé mechanics generally — one page, no photo, no age, no marital status, whatever the norm was back home — in the US résumé guide for immigrant cloud engineers.

To a recruiter who has never heard of your employer, it carries zero weight. One line of scale — millions of customers, thousands of users — turns geography they don't know into pressure they do.

Move three: modernize the top layer — the hop is shorter than you think

Here is the part that should genuinely encourage you. The US market is not asking you to start over. It is asking you to modernize the top layer of what you already know, and for an experienced administrator that hop is measured in weeks of focused study, not years.

Active Directory → Entra ID

If you lived in Active Directory — users, groups, OUs, group policy, domain joins — then Microsoft Entra ID is not a foreign country. It is the same concepts (identities, groups, permissions, policy) rebuilt for the cloud, with different names and a different console. Conditional Access will remind you of the logic behind your old GPO decisions. And here is the market reality: most mid-size US companies run hybrid — on-prem AD syncing up to Entra ID — which means a person who understands both sides is more useful than the cloud-only kid who has never seen a domain controller. Your "legacy" knowledge is half of the hybrid skillset. Start with what Microsoft Entra ID actually is, then do the free class where we build it hands-on: Entra ID, subscriptions, and groups.

VMware / Hyper-V → Azure VMs

If you provisioned VMs on VMware or Hyper-V hosts, you already own the mental model for Azure compute: a hypervisor somebody else maintains, VMs you size and attach disks to, networks you segment. The names change — datastores become managed disks, your host cluster becomes availability sets and zones — but the thinking transfers almost one-to-one. This translation habit generalizes; the same read-across works between whole clouds, which I mapped in the Azure, AWS, and GCP equivalents table.

Cisco networking → cloud networking

Subnetting is subnetting. If you carved VLANs and wrote firewall rules for a telecom, then VNets, subnets, NSGs, and route tables are your old job with software-defined plumbing. Cloud networking is arguably the hop where home-market experience transfers most cleanly, because the underlying discipline — addressing, segmentation, least-privilege paths — never changed.

An honest hedge on the timeline: "weeks not years" assumes you actually did the on-prem work deeply, and it means weeks to working competence, not weeks to expert. With fragmented time — night shifts, family, eight to ten hours of study a week — an AD veteran can realistically be conversant in Entra ID and Azure fundamentals in two to three months. Slower than the ads promise. Much faster than starting from nothing, which is the whole point.

The honest gap: what does not transfer

This is the section the résumé-tips articles will not write, so let me write it plainly, with respect. You worked in a real IT market. And some real IT markets ran on practices the US market will not accept — not because American IT is smarter, but because it runs under different constraints and different lawyers.

• End-of-life stacks. If your environment still ran Windows Server 2008 or an ancient Exchange because the budget never came, your fundamentals are fine but your version-specific knowledge is not sellable. Lead with the durable concepts (identity, DNS, storage, backup discipline), not the versions. Nobody in a US interview wants to hear you tuned Server 2008 well.
• Unlicensed software environments. In some shops back home, licensing was aspirational. In the US it is a legal exposure companies take seriously. Never present cracked-software experience as product experience you would defend — and in interviews, do not volunteer stories that hinge on it. Your skills are real; that context is not a selling point here.
• No change management. If your shop's process was "the IT officer fixes it directly on the live server, tonight," you got very good under pressure — and you have a genuine gap. US environments, especially anywhere regulated, run on change requests, approvals, maintenance windows, rollback plans, and tickets that document everything. Interviewers probe this specifically: tell me about a change you rolled back; how did you document incidents; who approved production access? If your honest answer is "there was no process, I was the process," say that — then show you understand why the process exists. Self-awareness about the gap reads far better than pretending it is not there.
• Scale claims that will be probed. If your résumé says 5,000 users, an interviewer may ask how many domain controllers, what the backup schedule was, what broke most often. This is not hostility toward foreigners — they probe Americans the same way. It only burns you if the numbers were decorative. Keep every claim at a level of detail you can walk into comfortably.

Notice what is not on that list: your accent, your age, your degree, or your country. Those are fears, and I have addressed them elsewhere. This list is the actual technical-cultural gap, and every item on it is closable with study and honesty. The people who fail interviews from our communities mostly fail on the third and fourth items — not because they lacked skill, but because they had never seen the questions coming. Now you have.

Move five: the certification as your verification layer

Think about the recruiter's problem for a second. They see foreign experience they cannot easily verify and cannot personally evaluate. What they need is a signal that is current, standardized, and issued by an authority they trust. That is exactly what a certification is — not a substitute for your experience, but a verification layer on top of it.

For your profile, the highest-value single move is AZ-104, Microsoft Azure Administrator. Not AZ-900 alone — fundamentals certs on top of ten years of real administration undersell you — and not a specialty cert first. AZ-104 says, in one line a recruiter can read: this person's Windows and identity foundation is real, and they have modernized it to the platform we run on. A cert on top of nothing is a lottery ticket; a cert on top of eight years of AD at a bank is a credibility stack, and honestly one of the fastest ones available in this field. Add one or two hands-on Azure projects you can demo — the interview question is always "show me," and our landing-the-job class covers how to present exactly that. You can start drilling for free right now on the exam practice bank — hundreds of AZ-104-style questions, no payment, no sign-up tricks.

Questions people also ask

Does foreign IT experience count on a US resume?

Yes. US employers care whether you can do the work, and years of real systems administration, networking, or support experience count regardless of the country. What trips people up is presentation: unfamiliar employer names, unfamiliar titles, and tools described in local shorthand. Translate the titles into US-standard ones, add a short context line for each employer so a recruiter understands its scale, and keep the experience — never delete it or start your résumé from zero.

How do I list overseas work experience on a US resume?

List it exactly like US experience: employer, US-legible title, dates, then bullets that lead with what you did and at what scale. Add one context line under each employer — for example, describing a bank by its customer count or a university by its user base — so the recruiter can gauge size. Drop photos, age, and marital status, which are standard on many home-market CVs but are never included in the US. Keep it to one page if you can, two at most.

Do US employers verify foreign work experience?

Background checks on overseas employers are inconsistent — some companies use international verification services, many effectively cannot check. But that is not where verification really happens. It happens in the interview, where a hiring manager probes whether you actually did what the résumé says: how you handled changes, what you documented, how many users or servers you supported. If your experience is real, this is good news. Be specific, keep your numbers honest, and the interview verifies you better than any background check could.

Is Active Directory experience still relevant for cloud jobs?

Very. Microsoft Entra ID — the identity system behind Azure and Microsoft 365 — is built on the same concepts you already know from Active Directory: users, groups, permissions, policy. Most mid-size US companies run hybrid environments where on-prem AD syncs to Entra ID, so someone who has lived AD and then learned the cloud side is more useful than someone who only knows one half. The gap between on-prem AD and Entra ID is weeks of focused study for an experienced administrator, not years.

Which certification best proves foreign IT experience to US employers?

For someone with real systems or network administration experience, AZ-104 (Microsoft Azure Administrator) is the strongest single move. It is a US-recognized, current credential that verifies your foundation is real and shows you have modernized it to the cloud. A certificate alone does not get anyone hired — but a cert on top of eight years of real administration reads very differently from a cert on top of nothing. Pair it with one or two hands-on Azure projects you can talk through in an interview.