No US experience? How to get your first cloud job anyway

Every posting wants US experience. Nobody will give you the first one. That loop has a name — the catch-22 — and it has exits, none of which involve lying on a résumé or paying anyone to fake your history. Here is the honest map: the portfolio move, the five realistic on-ramps, and the referral math.

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

You get your first US tech job without US experience by going around the filter: build a public portfolio a hiring manager can verify from any desk, take an on-ramp role — help desk, MSP, NOC, W2 contract, volunteer infrastructure — and get referred by someone who has seen your work. It takes months, not weeks.

Name the problem precisely first, because vague problems produce vague plans. You were a banker in Lagos, an engineer in Accra, an IT administrator in Nairobi. You apply to a "junior" cloud role here and the posting asks for two years of US experience. You apply anyway. Silence. Fifty times. Here is the thing: "US experience" is a lazy proxy. What the employer actually wants to know is — can this person do the work, and can I verify that? Your ten years in Accra answers the first question perfectly, but the employer cannot verify it cheaply, so the résumé goes in the pile. Everything in this article is a way of answering the verification question without needing the US job you cannot get yet.

The core move: a public portfolio is US-verifiable experience

Here is the fact the catch-22 depends on you not noticing. The reason "no US experience" hurts is not geography — it is verifiability. A recruiter in Dallas is not going to call your former manager in Lagos. Time zones, unfamiliar phone numbers, a company they cannot look up — the reference goes unchecked, and unchecked means it may as well not exist. Your professional history gets silently deleted from the process.

A public GitHub repository breaks that logic. Infrastructure code you wrote, a pipeline that deploys it, a README explaining what you built and why — a hiring manager can read all of it in ten minutes, from their desk, without calling anyone, in any country. It cannot be exaggerated the way a résumé bullet can, because the work itself is sitting there. A repo a hiring manager can read beats a glowing reference they will never call. The portfolio is the substitute for the verification the US market refuses to do on your behalf.

What goes in it? Real deployments, not copied tutorials. Infrastructure as code, a small app deployed once by hand and once through a pipeline, a write-up of what broke in between. I wrote a tactical companion for this: how to get Azure experience with no job walks through exactly what to build, in order, on a free-tier budget. And to see what inspectable work looks like, our own labs are public at github.com/kloudcaptain/campux-labs — that is the standard to aim at.

Nobody in Dallas will call Lagos to check a reference. Anyone, anywhere, can read your GitHub. Build the thing that can be verified.

The realistic on-ramps, in order of accessibility

The portfolio gets you taken seriously. It usually does not, on its own, get you a cloud engineer title as job one — anyone who says otherwise is selling something. What it does is qualify you for the on-ramp roles: jobs that hire on aptitude, put US experience on your résumé, and sit one or two moves from cloud work. Ordered from most accessible to least. Treat the pay figures with suspicion — they move with the market and your city — but the ordering is stable.

Help desk and desktop support: the widest door

Nobody dreams of help desk, and if you ran systems back home it can feel like a demotion. Take it anyway if it is what opens. The logic, stated plainly: the US market does not doubt your intelligence, it doubts its ability to verify you. Help desk is where employers accept that risk cheaply, and six months in you are no longer unverifiable — you have a US employer, a US manager who answers the phone, and a track record in the systems American companies run on. From inside, you also see the internal postings outsiders never do. The trap is comfort: the paycheck steadies and five years pass. Decide your exit before you enter.

MSPs: brutal pace, unmatched exposure

Managed service providers — companies that run IT for many small businesses at once — are nearly always hiring, because the work is relentless and turnover is high. I will not dress that up: the tickets never stop, and some MSPs will burn you out if you let them. But there is no faster way to touch more technology. One year at an MSP shows you more environments, more failure modes, and more Microsoft 365, networking, and server administration than three years inside a single company's IT department. For someone building a résumé from zero US lines, it is a compressed apprenticeship. Take the two-year tour, extract everything, and move.

NOC roles: the operational half of cloud

Network operations center jobs — watching monitors, triaging alerts, escalating incidents — map more directly onto cloud work than most people realize; monitoring and incident response are half of what cloud engineers do all day. NOC roles often run on night shifts, which is miserable — but if you already work nights as a CNA or in a warehouse, a night-shift NOC role is a lateral move in schedule and a massive move in direction. One caution: ask in the interview what you will actually touch. Some NOC seats are pure alarm-watching with no hands on anything, and those teach less.

Contract-to-hire: legitimate, and here is how it works

This one deserves a full explanation, because in our communities "agency" and "contract" have picked up a scam smell — sometimes deservedly. So let me separate the real thing from the fake thing.

Legitimate W2 contracting works like this: a staffing agency (TEKsystems, Robert Half, Insight Global, and hundreds of smaller ones) employs you — you are their W2 employee, taxes withheld from your paycheck like any job — and places you at a client company for a defined contract, often three to twelve months, often "contract-to-hire," meaning the client intends to convert good contractors to permanent staff. Companies use this constantly because it lets them try people without the commitment of a permanent hire. That lowered commitment is precisely your opening: a client who would never permanently hire someone without US experience will absolutely take a six-month contractor with a strong portfolio, because their risk is capped. A large fraction of US tech careers started exactly here.

The test that separates a real agency from a scam is one sentence: a real agency pays you; a scam asks you to pay them. Nobody legitimate charges for placement, for "mandatory training," or — the one I want to say loudly — for putting fake experience on your résumé. You have seen that pitch in the WhatsApp groups: $500 and they will list you at a company you never worked for. Do not touch it. Background checks here are routine, fabricated history is grounds for firing years later, and for an immigrant the consequences of a fraud finding can reach far beyond one job. One more plain fact: when an application asks "will you now or in the future require sponsorship?", a green card holder answers no, and that answer removes a whole category of employer hesitation. Know what your status lets you truthfully say — and confirm anything visa-specific with your attorney.

Volunteering infrastructure: real work, and a US reference

The most overlooked on-ramp costs nothing and may already be sitting in your Sunday. Your church, your mosque, your association, the local nonprofit — most run on shared passwords, a donated laptop, and someone's cousin who "knows computers." Offer to run it properly: set up the Microsoft 365 tenant, sort out who has access to what, get backups working, document it. This is real admin work — identity, access control, backup and recovery are the same disciplines you will be paid for later, with real stakes. A church losing its donor records is a genuine disaster you will have prevented.

And it produces the thing money cannot easily buy: a US-based reference. A pastor or executive director who says "this person has run our systems for eight months, here is my number" is a reference a recruiter will actually call — local number, verifiable organization, no time zones. The résumé line is real too: Volunteer IT Administrator, [organization], City, State. One caution from experience: define the scope in a friendly email, or you will become the unpaid IT department for every device in the congregation.

Referrals: why one warm name beats fifty cold applications

Now the mechanic that shortcuts everything above, and that immigrants systematically underuse because nobody explains it. Most US companies have an internal referral system: an employee submits your name, your résumé enters a separate, smaller pile that a human actually reads, and the employee often gets a bonus if you are hired. They are not risking their job on you — they are vouching lightly, saying "worth a look." That is all a referral is. It is not corruption, not a favor you must repay, and asking for one is normal, expected behavior.

The math is lopsided. A cold application is one résumé among hundreds, screened by software looking for keywords like "US experience" — the exact filter you cannot pass. A referral skips the software and lands in front of a person, and a person can look at your GitHub. This is where the portfolio and the referral lock together: the referral gets a human to look, the portfolio gives the human something verifiable to see. One genuinely beats fifty. I have watched it happen from both sides of the hiring table.

Where do referrals come from when you "know nobody in tech"? Your community is a better network than you give it credit for. The cousin in Texas "in IT." The nurse on your shift whose husband is a sysadmin. The association WhatsApp group where someone posted their new cloud job last month — congratulate them, then ask how. University alumni from back home who are now here. Then build outward: local meetups are free, cloud community Slacks and Discords are free, and a specific, respectful message — "I saw your team uses Azure; I built something similar, here is the repo, could I ask you two questions?" — gets answered far more often than "please refer me." Give people an easy yes: work they can glance at, a clear ask, no desperation.

If you already did IT back home, the problem is legibility

Plenty of people reading this are not starting from zero at all — they ran Active Directory in Lagos, or the network for a bank in Nairobi, or the servers for a university in Accra. Then the applications go nowhere, and the conclusion is that the experience does not count here. That is usually wrong. The experience counts; it is unreadable in the format you are presenting it.

US recruiters hire against a fairly rigid set of role names. Your job is to map what you did onto the name they are searching for. Not to inflate it — to say it in their dialect.

Two things make this land. Add a context line under each employer, because "Systems Administrator, First Bank" means nothing to an American recruiter who does not know it is a tier-one bank with thousands of staff — one clause naming the size and sector fixes that. And modernize the top layer, because the hop is shorter than you think: Active Directory to Entra ID, on-premises virtualization to Azure compute, on-premises networking to virtual networks. You are not restarting, you are renaming and updating.

The degree question, and the two gates

Every application passes two filters that check for different things, and conflating them is why this question causes so much anxiety.

Gate one is the administrative checkbox. A recruiter or a tracking system checks whether you meet the posting's stated minimum. If it says "bachelor's degree required", the gate checks for a bachelor's degree. Notice what it does not say: it does not say a US bachelor's degree. The standard phrasing on tech postings is a degree "or equivalent experience", and much of the industry publicly dropped hard degree requirements for technical roles years ago. Your foreign degree usually clears this gate as it is.

Gate two is the hiring manager, and it produces the offers. They are answering one question: can this person do the job without breaking my environment? They probe it by asking what you built, why you made those choices, and what happened when something failed. No degree of any nationality answers that. Deployed work you can explain under questioning does.

On credential evaluation: it is worth the money in specific situations rather than as a default. Public-sector roles — federal, state or city — very often require a foreign degree to be evaluated by a recognised service before it counts, and that is the clearest case for paying for one. For most private-sector cloud postings it is not required, and the money is usually better spent on an exam fee and a project. Get it evaluated when an employer asks, or when you are aiming at government work.

Building a network from zero

Networking feels like begging when you were somebody back home, and that feeling is worth naming rather than talking past. You are not asking for charity; you are trying to become a known quantity in a market that hires known quantities. Three moves do most of the work.

The conversation with the relative already in IT. Most people waste it by asking for a job. Ask instead for fifteen minutes on what their team actually screens for, what their own route in looked like, and whether they would look at your project and tell you what is missing. That is a question people enjoy answering, and it ends in a relationship rather than an awkward no.

A profile that points somewhere. Yours is not an autobiography; it is a pointer to the work. The headline says what you do or are becoming, and the profile links to the repository. Commenting with substance on other people's technical posts does more than cold messages, because it makes you visible to their network repeatedly rather than once.

A three-line connection note. Who you are, one specific reason you are contacting them, and one small ask. Specific beats flattering, and small beats open-ended — "would you look at this and tell me what you would change" gets answered far more often than "can you help me get a job".

The honest gap: what this article cannot do for you

Here is the section the course-sellers will not write. Everything above is real, and none of it is fast. Working shifts and studying eight to ten hours a week, a portfolio worth showing takes months, not weekends. The first job that says yes will probably pay less than your skills deserve and carry a smaller title than you held back home — the banker becomes a help desk tech, and that costs something real in pride, even when the trajectory afterward is steep. Certifications alone will not save you either; a pile of them without inspectable work reads as theory, the exact wall I wrote about in passed AZ-900 and still not getting interviews.

Some of it is outside your control. Markets tighten and loosen; a strategy that lands interviews in six months in one city takes twelve in another. Your accent will cost you some phone screens with lazy screeners — a real loss, and the partial answer is the same as everything else here: verifiable work and referrals route around lazy screeners, because people who have seen your repo do not care how you pronounce "router." The direction is settled even when the timelines are not: verifiable work plus an on-ramp role plus a referral is how people in your position get in. I have never seen a durable shortcut around those three, and I have seen many expensive fake ones.

The age worry deserves one honest paragraph, because I know it is sitting there. Starting at 35 or 40 is not a handicap here for a concrete reason: the on-ramp roles reward exactly what a decade of professional work built in you — reliability, escalation judgment, calm under pressure, the discipline to study after a night shift. A 22-year-old competitor has none of that. You are not starting from zero; you are transferring assets the résumé filter cannot see — one more reason to route around the filter.

Questions people also ask

Can I get a tech job in the US without US work experience?

Yes, but rarely by cold-applying to jobs that say "2+ years US experience required." The people who break in without US experience do it through side doors: a public portfolio a hiring manager can inspect, entry roles like help desk and NOC that hire on aptitude, W2 contract roles through staffing agencies, volunteer infrastructure work that produces a US reference, and referrals from people who have seen their work. It takes longer than anyone selling a course will admit — plan in months, not weeks — but the path is real and people walk it every year.

Can I get a US cloud job with a foreign degree?

Usually yes, without doing anything to the degree. Job postings that require a bachelor's almost never specify a US one, and most tech postings now say "or equivalent experience" anyway. Credential evaluation is worth paying for in specific cases — public-sector roles often require a foreign degree to be evaluated by a recognised service before it counts — but for most private-sector cloud postings the money is better spent on an exam fee and a project.

How do I put my IT experience from back home on a US resume?

Translate the title into the one US recruiters search for, then add a context line so the employer is legible. A systems officer who ran Active Directory, Exchange and Windows Server is a Windows Systems Administrator here, and "First Bank" means nothing to an American recruiter until a clause tells them it is a tier-one bank with thousands of staff. Then modernize the top layer, since the hop from on-premises identity and virtualization to their cloud equivalents is shorter than it looks.

Are certifications enough without a US degree?

They clear the first gate, which is administrative, and they do not clear the second. A certificate gets you past the checkbox a recruiter or tracking system applies. The hiring manager is asking whether you can do the job without breaking their environment, and only work you built and can explain under questioning answers that. Pair one role-based certificate with two or three real projects rather than collecting more exams.

Does a GitHub portfolio really count as experience to employers?

To a filter, no — an ATS scanning for "3 years experience" will not read your repos. To a human, often yes. When a hiring manager or engineer actually looks at your GitHub and sees infrastructure code, pipelines, and README files explaining decisions you made, that is direct evidence you can do the work — evidence they can verify in ten minutes without calling anyone. It will not replace experience for senior roles, but for a first role it does the one thing your foreign work history cannot: it lets an American verify you personally. Your job is to get it in front of a human, which is what referrals are for.

Is contract-to-hire through a staffing agency legit or a scam?

Legitimate W2 contracting is a normal, huge part of US tech hiring — the agency is your employer of record, taxes come out of your paycheck, and you work at the client site with a real chance of conversion to a permanent role. The test is simple: a real agency pays you; a scam asks you to pay them. Walk away from anyone who wants money for training, placement, or putting fake experience on your résumé — that last one can end your career and, for an immigrant, create problems far worse than unemployment. Never lie on a résumé, and confirm anything visa-related with your attorney.

Do US employers call references in another country?

Almost never. Time zones, phone costs, language assumptions, and verification difficulty mean a reference in Lagos or Nairobi usually goes unchecked — which quietly deletes your professional history from the process. That is exactly why a public portfolio and one US-based reference matter so much: the portfolio is verifiable from any desk in the world, and a supervisor at a US nonprofit or church whose systems you administered is a reference a recruiter will actually call. One checkable US reference plus inspectable work beats ten impressive references nobody will phone.

How do I get a referral if I don't know anyone in tech?

You know more people than you think. A referral in the US usually means an employee submits your name through an internal portal — they are vouching lightly, not staking their job on you. Start with your actual network: the cousin "in IT," your church or association, alumni from your university back home who are now in the US, coworkers at your current job whose relatives work in tech. Then build the network you are missing: comment usefully in cloud communities, attend free local meetups, and message people doing the job you want with a specific question rather than "can you refer me." Most people are happy to refer someone who has clearly done the work — your portfolio is what makes the ask easy to say yes to.