AI Engineering Referrals

Reach an AI Agent Engineer Through a Shared Tie

Cold applications to agentic-AI roles vanish into a stack of hundreds. The honest fix: find the engineer already shipping those systems who shares a tie with you, and make helping you cost 30 seconds.

Find your warm intro →

Free · No sign-up · See results in ~10 seconds

A plain LinkedIn search buries the people who would actually help you.

It ranks by prominence, so the most-followed, most-messaged names sit on top. FindWarmIntros surfaces the coworkers who share your school or a past employer - the people most likely to reply - and hands you a ready-to-send intro.

Example - what you’ll see
in
Someone who works at your target company
🎓 Same university as you  ·  💼 Shared past employer
🔥 Strongest
in
A recruiter at your target company
🎓 Same university as you
🎓 Alumni

✍️ 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 a tech target:

Short answer: Find an engineer at the target company who actually builds the agentic or AI-automation systems (not a recruiter), and who shares a school, past employer, or open-source project with you. Message them leading with the shared tie and one specific detail about their work, then ask for a referral into the exact team, with your resume and the job link attached so a yes takes one click.

Target the builder, not the recruiter

A referral into a specialized agentic-AI role carries weight only when it comes from someone who does that work. A recruiter can forward you; an engineer on the team can vouch that you understand tool-calling, eval loops, and orchestration. Their internal referral lands in a different queue.

Find them by their output, not their title. Search the company's engineering blog, GitHub org, and conference talks for whoever shipped the agent framework, the RAG pipeline, or the internal automation. That person, if you share a tie, is your path.

Make the shared tie do the work

The tie is your permission to skip the cold-open. Lead with it in the first line, then prove you actually follow their work before you ask for anything.

  • Open with the overlap. Same lab, same former employer, same open-source repo. Name it in the first sentence so they read you as one of theirs, not a stranger.
  • Show you read their work. Reference the specific system they built ('your talk on cutting agent hallucinations with a verifier step') so it is clear you are not mass-messaging.
  • Ask for the exact thing. A referral into the named team and req, not 'advice' or 'a quick chat.' Vague asks get vague non-answers.
  • Attach everything. Resume plus the job link in the same message, so saying yes is one forward, not a scavenger hunt.

Let the tool find the ties you would miss

The hard part is not the message, it is knowing which of the engineers building agentic systems actually shares a school or employer with you. FindWarmIntros does that finding-and-ranking part: you give it the target company, it surfaces the real people there you have a genuine tie to and drafts the intro, so you spend your time on the person most likely to say yes instead of scrolling LinkedIn for hours.

You still write the human part. But you start from a ranked list of warm paths, not a blank search box.

Frequently Asked Questions

What if I share a tie but they do not know me personally?
A shared school or former employer is enough to earn a reply, even with no prior contact. Name it plainly, keep the ask small and specific, and accept that some will not respond. One warm reply beats fifty silent cold applications.
Should I message on LinkedIn or email?
Use whichever surface shows the shared tie most clearly. LinkedIn works when the connection is obvious from your profiles; a personal email works better if the shared employer would show up there. Keep it short either way.
What do I say if they cannot refer me but want to help?
Ask who on the team owns the agent or automation work, and whether they would introduce you. A named handoff from a real engineer is still a warm path, just one step longer.
How specific should I be about the role?
Very. Name the team, the requisition, and one system they build that you could contribute to. Specificity signals you did the homework and makes the referral easy to justify internally.

Keep going

Find your warm intro →
Find your warm intro →