How to Get a Job When You Have No Network
Applying cold to 200 postings and hearing nothing is not a networking problem, it is a distribution problem. You almost certainly have warm paths you have never looked for.
Find your warm intros →Free · No sign-up · See results in ~10 seconds
✍️ Ready-to-send intro“Hi - we both studied at [your school]. I’d love to hear about your path to a company you are targeting before I apply…”
… plus everyone else in your network who can put in a good word.
See who can refer you in - pick your target company:
You Have a Network, You Just Have Not Indexed It
When people say they have no network, they usually mean they have no close friends who can hand them a job. That is true for almost everyone. It is also the wrong bar. A network in the job-search sense is not people who like you, it is people who have a small, cheap reason to reply to you.
Add it up. A four-year school with 2,000 people per class puts roughly 20,000 alumni in the world over a decade. Two past employers of 500 people each add hundreds more. You have never met any of them, and that is fine. Shared affiliation is not friendship, it is a conversation starter that survives being from a stranger.
Find the Overlap, Not the Job Posting
The move is to stop searching by role and start searching by person. Pick 10 companies you would actually take a job at, then find who inside them went to your school or worked where you worked. That intersection, and not the careers page, is your real pipeline.
This inverts the usual order. Most people find a posting, apply, then hope. You find a person, learn what the team actually needs from them, and only then decide whether the posting is worth your time. The information you get in a 15-minute chat is worth more than the application.
- School first, employer second. Alumni respond most often, but a shared past employer is stronger than people assume, especially if your tenures overlapped by even a month or you shared a manager, an office, or a product.
- Aim two levels above yourself, not at recruiters. A senior engineer or a manager on the team can flag your name internally and knows what the req actually wants. Recruiters get 300 messages a week and are measured on closing reqs, not on being helpful.
- Make helping you cost 30 seconds. Ask one specific question you could not have Googled, like what the team is actually building this quarter, instead of asking for a referral, a call, or advice on your career. Referrals come after they have talked to you once, never before.
- Skip the resume attachment. Nobody opens a PDF from a stranger. Put the two most relevant lines in the message itself and let them ask for the rest.
What to Actually Say in the First Message
Lead with the shared thing, not the ask. The first line should be the school or the company, plainly stated, because that is the only reason they are still reading. The second line is why you are writing them specifically and not fifty other people, which means naming their team or something they built. The third line is one small, answerable question and a soft 15-minute chat offer they can decline without feeling rude.
Finding those people is the tedious part. FindWarmIntros does the finding-and-ranking step for you: you give it your schools, past employers, and a target company, and it surfaces the people there who actually share one of those with you, ranks them by how strong the overlap is, and drafts the opener you can edit. The 15-minute conversation is still yours to have. That part does not automate.
Do This for a Week and Watch What Changes
Five people a day at five target companies is 25 conversations started in a week. If a fifth reply, and warm openers usually beat that, you have five people inside your target companies who know your name. That is a network, built in a week, from a standing start.
Track it like a pipeline, not like a feeling. Names contacted, replies, chats booked, internal flags. The number that predicts an offer is chats booked, not applications sent, and the two are almost unrelated.