Building a US tech network from zero (when you know nobody in the industry)
Every career guide says "network your way in," and every one of them assumes you already know people in the industry. You don't. Your network is at church, in a WhatsApp group, and back home. Here is how to convert the network you actually have — and build the one you don't — without pretending to be someone you're not.
New to cloud? CAMPUX is a free, build-first course. Start here →
You build a US tech network by converting the network you already have (the cousin in IT, the church, the diaspora association) into specific, small asks, then adding LinkedIn comments, Azure meetups, and informational interviews on top. It is slower than the guides promise, but referrals move US hiring more than any job board.
If you came here from Lagos or Accra or Nairobi, you already know how careers work through people — back home, nothing moved without a relationship. The US is not different in kind, only in mechanics. Here the relationship-machine is called "networking," it runs partly on LinkedIn, and it has scripts and norms nobody wrote down for you. This article writes them down.
And here is why it matters more than another fifty applications: a referred candidate usually gets a human look at their résumé instead of an ATS filter deciding alone, and most US companies pay their employees a bonus — often a few thousand dollars — when someone they refer gets hired. So when you ask for a referral, you are not begging; you are offering someone a chance to get paid for knowing you. The exact share of hires that arrive through referrals moves around by survey, so I won't invent a number — but the direction is settled, and every recruiter will tell you the same thing.
The honest gap: networking feels like begging when you were somebody back home
Nobody else writes this section, so I will. You were a banker in Lagos. An engineer in Accra. You had an office, a title, people who called you sir or madam. Now some article is telling you to message strangers asking for fifteen minutes of their time, and every instinct says this is beneath you — or worse, that it looks desperate.
Here is the reframe, and it is a fact about how this country works, not a pep talk: in the US, asking for an informational conversation is standard professional behavior at every level. Vice presidents do it. Twenty-year veterans do it when they change industries. Nobody reads it as weakness; most read it as competence, because it shows you understand how hiring here works. The person who never asks is not seen as dignified. They are simply not seen.
There is a second half to the reframe. Networking done right is not extraction — it is trade. You comment usefully on someone's post before you ever message them; you send the association's job channel a lead you can't use; you tell the next person from your church what you learned. People who build real networks give first, and your community already taught you how.
The person who never asks is not seen as dignified. They are simply not seen.
1. The cousin-in-IT conversation, done right
Almost everyone has one: a cousin in Texas "in IT," a brother-in-law who "works with computers," someone from your association who made it into tech. And almost everyone burns this contact the same way — with the vague ask. "Let me know if you hear of anything." Your cousin says "of course," means it sincerely, and then nothing happens, because you handed them a job with no defined task and no deadline. Vague asks die of vagueness.
A specific, small ask is a different thing entirely. Compare:
- Vague: "Let me know if you hear of anything." — Requires your cousin to remember you every time a job appears, forever.
- Specific: "Can you look at my GitHub repo for 15 minutes and tell me if it looks like real work or student work?" — Bounded, doable this week, and it makes you look serious.
- Specific: "Does your company post cloud support or junior admin roles? If one opens, would you be willing to refer me? Here is my one-page résumé so you have it." — Now the referral bonus works in your favor, and your cousin has everything they need on file.
- Specific: "Can I ask you 20 minutes of questions about what your team actually does day to day?" — This one teaches you how to talk about the job in interviews.
Notice what the specific asks share: a size, a timeframe, and a clear yes-or-no answer. That is the whole trick — it respects the other person's time, which is exactly why it works. And if the repo ask lands, make sure there is a repo worth looking at; Class 42 on landing the job covers turning lab work into things a cousin — or a hiring manager — can actually inspect.
2. LinkedIn that works (and the LinkedIn that wastes your time)
LinkedIn matters in the US more than it did back home, and it rewards a specific kind of behavior. Three things to get right.
Your profile is a pointer, not an autobiography
Recruiters spend seconds, not minutes. Your headline should say what you are aiming at, not what you were: "Cloud Engineer in training — Azure | Former banking operations" beats "Experienced professional seeking opportunities" by a mile. The profile's real job is to point at proof: your GitHub, your projects, the labs you have actually done. If someone lands on your profile and can click through to real work within one scroll, the profile has done its job. Everything else is decoration.
Commenting with substance beats cold DMs
The instinct is to message strangers asking for jobs. Resist it. A cold DM from an unknown name asking for something is the easiest message in the world to ignore, and most are. What works slower but far better is becoming a familiar name first: find ten people who post about Azure, cloud careers, or breaking into tech, and leave comments that add something — a question that shows you did the lab, a detail from your own study, a respectful disagreement. Do this for a few weeks and something strange happens: when you eventually send a connection request, they recognize you. You are no longer a stranger asking. You are that person with the thoughtful comments.
The three-line connection note
When you do connect, always add a note, and keep it to three lines: who you are, why them specifically, no ask. For example: "I'm moving into cloud engineering from nursing and studying Azure. Your post on breaking in without a CS degree matched my situation almost exactly. Would be glad to connect." That's it. No job request, no résumé attached, no life story. You are opening a thread, not cashing it in.
One more thing, because people from professional cultures back home worry about it: the green "open to work" banner is fine at entry level. The advice to avoid it is meant for senior people trading on scarcity. Your problem is the opposite — visibility. Recruiters filter searches by who is likely to reply, and the banner is that signal. Use it.
3. The community you already have is a network — use it deliberately
Here is something the standard networking guides cannot tell you, because their authors don't have it: the Nigerian association, the Ghanaian union, the church, the mosque — these are high-trust, high-speed networks that broadcast wins and warnings faster than any job board. Someone's daughter gets a cloud job in Dallas, and by Sunday everyone from Houston to Minneapolis knows the story, the company, and roughly the salary.
Most people let this network work on them passively. Use it on purpose instead:
- Announce what you are doing. Tell the WhatsApp group, plainly: "I am studying Azure cloud engineering, aiming for a cloud support or junior admin role by next year. If anyone knows someone in tech, I would value an introduction." This feels exposed. Do it anyway — you cannot be referred for a goal nobody knows you have.
- Find the ones who crossed already. Every diaspora community has three or four people who made it into tech. They are usually glad to help someone from home — many remember exactly how alone they were — but they help the people who ask specifically, same rule as the cousin.
- Look for the professional associations. Beyond your own community's groups, there are African-diaspora professional and tech associations in most large metros, and national ones online. Their events are networking with the awkwardness halved, because half the room already understands your story.
- Give back into the pipe. Post the job leads you can't use. Share what you learn. Vouch for the next person. Networks reward the people who feed them, and your reputation inside the community is an asset that compounds.
One honest caution, because this network carries scams as fast as wins: anyone selling guaranteed placement or fake résumé experience is selling a fire that burns you in a background check. Verify everything — including us. That is why the entire 42-class bootcamp and the exam practice bank are free and public: check what we teach before you pay anyone a dollar, here or anywhere else.
It worked for them.
4. Meetups and Azure user groups: showing up twice beats attending once
Nearly every US metro has free tech meetups — Azure user groups, cloud groups, "tech career" gatherings — findable on Meetup.com or the Microsoft community pages. They are the fastest way to put your face in front of working engineers, and most people use them exactly wrong: attend once, stand awkwardly at the edge of the pizza table, collect no jobs, never return.
Two corrections. First: the return visit is the whole strategy. Nobody remembers you from one attendance. At the second and third, organizers greet you by name and regulars talk to you instead of past you. Familiarity is the currency, and it only mints on repeat visits. Pick one group and go every month; that beats sampling five groups once each.
Second: the question you ask matters more than the business card you hand out. After a talk, the person who asks "I set up the same alert rule in my lab and it fired twice — did you hit that?" has just told the whole room they do real hands-on work. That one question beats an hour of mingling, and it is another place the free labs quietly pay off — you can only ask a practitioner's question after a few weeks of actually touching the tools in the classes.
Night-shift honesty: if evening meetups are impossible most months, that is not failure. Go when you can, and lean on the channels that fit fragmented time — LinkedIn and informational interviews work at 1am; a Tuesday meetup does not.
5. Informational interviews: the script, the questions, the follow-up
An informational interview is a short conversation with someone doing the job you want — not to ask for a job, but to learn how they got there and how hiring works at their company. Immigrants underuse it because it feels presumptuous. It isn't; it is so normal here that career centers hand out templates for it.
The outreach — four sentences, no more
Who you are. Why them. A small specific ask. An easy out. Like this:
"I'm a former banker from Lagos, now studying Azure and aiming at cloud support roles. I found you because you made a similar move a few years ago. Could I ask you three questions about how you got your first US role — 15 minutes on a call, or by message if that's easier? If you're busy, no problem at all."
Every sentence earns its place. The easy out matters most — it makes saying yes feel voluntary instead of extracted, and it is why this template gets replies where long messages get silence. Expect most people to ignore you anyway; that is normal, not personal. If two in ten reply, the system is working.
What to actually ask
- "What does your team actually do in a normal week?" — teaches you the language of the job.
- "When you interview junior people, what separates the ones you say yes to?" — intelligence you cannot get from a job posting.
- "What would you do in my position, with my background?" — invites them to invest in you.
- Never: "Can you get me a job?" — that question ends the relationship you just started.
The follow-up that keeps the thread alive
Thank them the same day, in two lines. Then — the part almost nobody does — come back six or eight weeks later with evidence you used their advice: "You told me to focus on one cert and build something public. AZ-104 is booked for March and here's the deployment project I built." That message turns you from someone they talked to once into someone they are invested in. People refer candidates whose progress they have watched; when a role opens, you are no longer a cold applicant.
Where each channel actually pays off
No fake percentages here — nobody honestly has them — but after years of watching people make this jump, the qualitative picture is consistent:
| Channel | Effort to start | Time to pay off | Odds it produces a referral |
|---|---|---|---|
| Cousin / community contact in IT | Low — one honest conversation | Fast, if the ask is specific | High for one referral; limited beyond their company |
| Diaspora association / church network | Low — you're already inside | Unpredictable, then sudden | Medium — depends on who crossed before you |
| LinkedIn commenting + connection notes | Medium — weeks of steady showing up | Months | Medium, and it compounds; also feeds recruiter searches |
| Cold DMs and mass applications | Low per message | Rarely | Low — the channel everyone overuses because it feels like work |
| Meetups / Azure user groups (repeated) | Medium — evenings, travel | 2–3 visits before anything | Medium-high locally; regulars refer regulars |
| Informational interviews + follow-up | Medium — outreach and nerve | Weeks to months | High per relationship — the follow-up is what converts |
| A cohort of classmates | Costs money, unlike the rest | Compounds for years as classmates get hired | High over time — the first one in pulls on the rest |
Read the table as a portfolio, not a menu. The cousin conversation and the association announcement cost almost nothing this week; LinkedIn and informational interviews run on night-shift time. You do not need every channel firing — two or three running steadily for a few months is the plan.
6. A cohort is a network — the part I have skin in
I will be straight that I am selling something in this section, so weigh it accordingly. But the logic stands on its own: referral programs work because people vouch for people they have actually worked with, and a cohort manufactures exactly that. You spend 2.5 months building real Azure projects next to other people making the same jump — many with stories like yours — and you finish knowing how each other works under pressure. Then the first classmate gets hired, their company has a referral bonus, and suddenly your cohort has someone on the inside. The WhatsApp group never dies; it just changes subject from homework to job leads.
Whether that is worth $1,800 to $2,000 depends on your situation, and for some readers the honest answer is not yet — do the free classes, run the free channels above, and see how far they carry you. What I can say without hedging: for someone whose time is fragmented across shifts and family, structure plus a live instructor plus a built-in network is the highest-probability version of this whole plan, because it bundles the accountability and the contacts that solo learners have to assemble piece by piece.
Questions people also ask
How do I network in tech as an immigrant with no US connections?
Start with the connections you do have and make them specific. A cousin or church member anywhere in IT becomes useful the moment you give them a concrete, 15-minute ask instead of a vague one. Then add three channels in parallel: comment with substance on LinkedIn posts in your target field, attend one local Azure or cloud meetup repeatedly rather than many meetups once, and request short informational interviews with people one or two steps ahead of you. None of it pays off in a week. Most of it pays off inside a few months of steady, unglamorous repetition.
Do referrals really matter for getting a tech job in the US?
Yes. A referred application typically gets a human look instead of dying in the applicant tracking system, and many companies pay employees a bonus for referring someone who gets hired — which means the person referring you benefits too. The exact share of hires that come through referrals varies by company and by survey, so treat any single number with suspicion, but the direction is settled: two candidates with the same résumé are not equal if one arrives through an employee. That is why building even a small network beats sending fifty more cold applications.
Is it okay to use the LinkedIn open-to-work banner?
At entry level, yes. The argument against the banner — that it signals desperation — mostly applies to senior people whose value is scarcity. When you are breaking in, your problem is not looking too available; it is being invisible. The green banner tells recruiters running searches that you will answer their message, and recruiters filter on exactly that. Pair it with a headline that says what you are aiming at, for example Cloud Engineer in training — Azure, and a profile that links to real work, and the banner helps far more than it hurts.
What should I say in a LinkedIn connection request?
Three lines: who you are, why them specifically, and no ask. Something like: I am moving into cloud engineering from nursing and studying Azure. Your post on breaking in without a degree matched my situation almost exactly. Would be glad to connect. That is the whole message. You are not asking for a job, a referral, or a call — you are starting a thread. People accept requests like this because saying yes costs them nothing. The asks come later, after you have commented on their posts and become a familiar name instead of a stranger.
How do I ask someone for an informational interview?
Keep the outreach to four sentences: who you are, why them, a small specific ask, and an easy out. For example: I am a former banker from Lagos now studying Azure and aiming at cloud support roles. I found you because you made a similar move a few years ago. Could I ask you three questions about how you got your first US role — 15 minutes on a call, or by message if that is easier? If you are busy, no problem at all. Short, specific, and easy to decline gets far more yeses than a long story or a request for a job.