The US résumé for immigrant cloud engineers: what to cut, what to add
The CV that got you hired in Lagos or Accra was written correctly — for there. Here, the same document quietly works against you before a human ever reads it. Nobody hands you the US rulebook when you land, so here it is: what to delete, what to add, and how to make a recruiter read your work instead of your geography.
New to cloud? CAMPUX is a free, build-first course. Start here →
A US tech résumé is one page, reverse-chronological, with no photo, no date of birth, no marital status, and no nationality line. Add impact bullets with numbers, a Projects section with real cloud builds, and one line of context per foreign employer — the format is easy to fix; the bullets are what decide callbacks.
I want to be straight with you about why this article exists. I have looked at résumés from people who ran systems for banks with millions of customers, and the document sold them like a junior clerk. Nothing was wrong with the career. Everything was wrong with the translation. You are not new to work — you are new to how Americans read a page about work. That is a learnable skill, and it takes an evening, not a year.
What to cut, and the reason nobody explains
Back home, a proper CV carries a photo, your date of birth, marital status, nationality, sometimes religion and your father's name. Leaving them off would look evasive. In the US, the logic runs in reverse, and it helps to know why rather than just memorizing the rule.
US federal and state law bars employers from making hiring decisions based on age, national origin, marital or family status, religion, and appearance. An employer who has seen those details on your résumé cannot easily prove they ignored them if a rejected candidate ever claims discrimination. So the safest move for a company is to never see them at all — and some recruiters, rather than take on that risk, simply set aside résumés that include a photo or a birth date. Your CV is not being rejected because you are foreign. It is being rejected because it accidentally hands the employer a legal problem. Once you know that, the fix is mechanical.
| Cut this | Add this instead | Why |
|---|---|---|
| Photo | Nothing — no image anywhere | Appearance-based discrimination risk; recruiters discard rather than carry it |
| Date of birth / age | Nothing | Age is a protected characteristic; listing it invites the bias you fear |
| Marital status, children | Nothing | Family status is protected; it is also simply nobody's business |
| Nationality / state of origin | Nothing on the résumé | National origin is protected; work authorization is asked on the application, not the résumé |
| Full home address | City, state — e.g. Houston, TX | Recruiters only need to know you are local-ish or open to relocating |
| Objective statement | A 2–3 line summary of what you do | Objectives describe what you want; a summary describes what they get |
| “References available on request” | Nothing — they will ask | Assumed; the line wastes space you need |
| Second (and third) page | One page under ~10 years experience | The first screen is seconds long; page two dilutes page one |
| Duty lists (“responsible for…”) | Impact bullets with numbers | Duties say the job existed; impact says you were good at it |
| Unexplained foreign employer names | A one-line company context under the name | A recruiter cannot weigh what they cannot place |
One more cut that surprises people: leave your immigration status off the résumé too. Not because it is shameful — because the résumé is the wrong document for it. US applications ask the status question directly, usually as some form of “Will you now or in the future require sponsorship?” If you hold a green card, you answer no, and for most postings that puts you in the same pool as citizens. Anything more tangled than that is a conversation for your attorney, not a line on a résumé.
The format: one page, newest first, boring on purpose
The American résumé is aggressively plain. Reverse-chronological — your most recent role at the top, working backwards. One page if you have under roughly ten years of directly relevant experience, which as a career-changer into cloud, you do, regardless of how long you have worked. Standard section headings: Summary, Skills, Experience, Projects, Education, Certifications. Black text, one column, no graphics, no skill bars, no borders around everything.
The plainness is not a style preference; it is machinery. Which brings us to the three letters everyone warns you about.
The ATS, without the mythology
Most mid-size and large companies run applications through an applicant tracking system — software that parses your résumé into fields and lets recruiters filter and search. Two things about it are true at once, and most advice only tells you one.
First: the parsing is real. Two-column layouts, text inside graphics, headers and footers, and decorated templates genuinely do get mangled by some parsers, and a mangled résumé filters itself out. A plain single-column document survives everything. That is the whole reason for the boring format.
Second: the “robot rejects you for missing keywords” story is overtold. In most companies a human recruiter still makes the call — but they find you by searching and skimming for the words in the job posting. So the practical rule is this: mirror the posting's language honestly. If the posting says Microsoft Entra ID and you wrote identity management, add the term you actually have experience with. If it says Terraform and you have used Terraform, the word Terraform should appear where you used it. What you must not do is paste a wall of keywords you cannot back up — the first interview question about any of them ends the conversation, and recruiters have seen ten thousand stuffed résumés. Keywords earn their place inside real bullets, nowhere else.
Make them read the work, not the geography
Here is the quiet failure mode for immigrant résumés: a recruiter in Ohio sees an employer name they cannot place, in a city they cannot place, and their eyes slide to the next candidate — not out of malice, but because they have thirty seconds and no way to weigh what they are reading. Your job is to remove the guessing. Give every foreign employer one line of context, right under the name:
- GTBank — Lagos, Nigeria · one of Nigeria's largest banks, serving over 8 million customers
- University of Nairobi — Nairobi, Kenya · one of East Africa's largest universities, ~40,000 students
One line, and suddenly the recruiter is reading “ran identity and access for a bank with 8 million customers” instead of “worked somewhere in Nigeria.” The scale was always true; you just stopped making them dig for it. Three smaller translations finish the job: convert naira or cedi figures into dollars or, better, percentages (“cut costs 30%” travels across any border); translate titles into their nearest US equivalent (“Systems Analyst II” means little here — if the work was system administration, say systems administrator); and write dates as Jan 2021 – Mar 2024, since “2021–24” reads ambiguously to US parsers.
The recruiter is not rejecting your experience. They are declining to guess about it. Remove the guessing and the experience starts to count.
The foreign degree line
List your degree the way an American lists theirs: institution, country, degree, year. B.Sc. Electrical Engineering, University of Lagos, Nigeria, 2013. Do not apologize for it, do not bury it, do not leave the country off as if hiding it. Many employers take it at face value. Some — and more of the government-adjacent ones — will want a credential evaluation from a service like WES (World Education Services), which maps your degree to its US equivalent. Getting one costs real money and takes weeks, so I would not run to do it speculatively; but if you are targeting employers who ask, having the evaluation ready removes one more reason for a maybe to become a no. What the degree line cannot do, from any country, is prove you can do cloud work now. That proof lives one section down.
Projects are your US experience
The catch-22 you already know: postings want US experience, and nobody wants to give you the first unit of it. You cannot fix that on paper by wishing. What you can do is refuse to leave the hole empty. A Projects section — real Azure builds, with links a hiring manager can click — sits in your experience area and reads like work, because it is work. Nobody assigned it to you, which if anything says more.
A project entry earns its place when it names what you built, what it runs on, and one hard detail that proves you actually operated it:
- Retail web app on Azure — deployed a containerized three-tier app to App Service and AKS; CI/CD in GitHub Actions, infrastructure in Bicep, access locked down with RBAC; kept the monthly bill under $20. github.com/yourname/…
That bullet outcompetes an empty year every time. If you have not built anything like it yet, that is the actual gap to close — the free CAMPUX classes walk you through real builds end to end, and Class 42, landing the job, covers how to present them. The free résumé templates page is the hands-on companion to this article: US-format templates you can fill in and export today, no payment, no email wall.
Before and after: three bullets rewritten
Format gets you parsed; bullets get you called. The pattern is always the same — a duty bullet says the job existed, an impact bullet says you were good at it. Scale, numbers, outcome. Watch the same experience translated:
Weak: Responsible for maintaining bank servers and providing IT support to staff.
Strong: Kept 40+ branch servers patched and online for a bank serving 8M customers; wrote the runbooks that cut repeat support tickets by roughly a third.
Weak: Duties included managing Active Directory users and email accounts.
Strong: Administered Active Directory and Exchange for 1,200 staff across three sites; scripted onboarding in PowerShell, cutting new-account setup from two days to under an hour.
Weak: Completed Azure training courses and practice labs.
Strong: Built and deployed a three-tier app to Azure App Service and AKS with GitHub Actions CI/CD and Bicep IaC; enforced least-privilege access with RBAC (public repo on GitHub).
Notice what changed. Nothing was invented — the strong versions describe the same weeks of work as the weak ones. If you do not have an exact number, a defensible estimate (“roughly a third,” “40+ servers”) is honest and normal; a bullet with no scale at all is the only wrong answer. Go through your last two roles and ask of every line: how many, how big, what happened because I did this? The banker who reconciled accounts under deadline, the nurse who ran escalation checklists, the university IT admin who kept exam systems up — all of that converts. It just has to be written in the currency this market reads.
It worked for them.
The honest gap: what a résumé cannot do
Now the part the résumé-tips industry will not tell you, because it undercuts the product. A résumé is a multiplier, not a source. If the substance underneath is a survival job and a certificate, the best formatting on earth multiplies a small number. I have watched people polish the same one page for three months — new template, new synonyms, new summary — while building nothing, applying to hundreds of postings, and concluding the market is closed to immigrants. The market is brutal right now for everyone at entry level; that part is real. But the fix for a thin résumé is almost never on the résumé.
Two more uncomfortable truths. First, a large share of interviews in this country come through a person, not a portal — someone forwards your résumé with a sentence of vouching attached. Your community is a real network: the association WhatsApp group, the church member whose company is hiring, the cousin in Texas. The one-page document matters enormously in that moment, because it is what gets forwarded — but the forwarding is what got it read. Budget your effort accordingly. Second, certifications alone do not close the loop either — I hold 14+ of them and I will still tell you a recruiter reads AZ-104 as “studied,” and a deployed project as “did.” You want both on the page, and you want the project doing the talking. The honest ranking of what moves an immigrant career-changer's résumé, in my experience: real builds first, a person who vouches second, format third, certificates fourth. Most people invest in exactly the reverse order, because the bottom of that list is the easiest to buy.
Questions people also ask
What should I remove from my CV for a US job application?
Remove your photo, date of birth, marital status, nationality, religion, and full home address — a city and state is enough. These are standard on CVs in Nigeria, Ghana, Kenya and much of the world, but US anti-discrimination law makes employers cautious about even seeing them, and some recruiters discard résumés that include them rather than take the risk. Also cut the objective statement and the “references available on request” line; both are dead weight on a one-page document.
Should I put my visa or green card status on my résumé?
Usually no. The résumé is for your skills and your work; the application form is where status questions live. Most US applications ask some version of “Will you now or in the future require sponsorship?” — if you hold a green card, the answer is no, and that puts you in the same pool as citizens for most roles. If your situation is more complicated than that, confirm the details with your immigration attorney, not with a blog post — including this one.
How do I list foreign work experience on a US résumé?
List it exactly like US experience — reverse-chronological, with the job title, company, city and country, dates, and impact bullets — and add one short line of context under the company name so the recruiter is not guessing: GTBank — one of Nigeria’s largest banks, serving over 8 million customers. Keep the geography quiet and the work loud. Convert local currency figures to dollars or to percentages, and translate your title into its nearest US equivalent if yours would confuse an American reader.
Do US employers accept a foreign degree on a résumé?
Yes — list it plainly in your education section with the institution, country, degree, and year, the same way an American would list theirs. Many employers accept it as-is; some ask for a credential evaluation from a service like WES that states the US equivalent, and having one ready removes a reason to hesitate. What a foreign degree will not do on its own is get you the interview — pair it with a Projects section that shows current cloud skills.
Does a one-page résumé really matter in the US?
For under roughly ten years of relevant experience, yes — one page is the norm and recruiters expect it. The first look at your résumé lasts seconds, not minutes, and a second page mostly dilutes the first. Cutting to one page also forces the right discipline: every line has to earn its place. If you genuinely have ten-plus years of directly relevant work, two pages is acceptable; a career-changer moving into cloud almost never does, and that is fine.