Most referral requests fail because they create an unpaid writing assignment for your contact. You ask for a favor, and their brain immediately calculates the tax: open a blank editor, recall your career history, invent a narrative that fits their employer's current open slots, and type out a recommendation they have to sign their own name to. They freeze, stare at the notification, and mark it unread until the guilt fades.
If you want an introduction that moves, stop asking them to write your pitch. Give them the text ready to paste.
Write the two-line blurb yourself before you reach out. Keep it tight, factual, and focused on operational match rather than general praise. Make it so they can forward your message with a single click and zero edits. When the friction drops to zero, the reply rate changes because replying takes less time than feeling guilty about ignoring you.
Shift your opening question away from the open job requisition and toward the internal state of the team. Ask about what broke last Tuesday, how the on-call rotation looks, or whether the infrastructure can handle their current scale. People who work inside a company love talking about their operational friction much more than they love playing HR coordinator for their friends. Once you are talking about the mechanics of their daily engineering work, the specific role naturally surfaces as the place where those problems intersect.
Remember that a referral changes your entry point, not your evaluation. It skips the screening queue that filters out valid candidates based on keyword heuristics, but it does not lower the technical or behavioral bar inside the loop. Treat the introduction as a way to get a direct read from someone on the inside, not as a shortcut past the technical screen.
Top comments (0)