How Referrals Work and Whom to Ask

Students often talk about referrals as if they were magic: get one and you are in. Others treat them as impossible: "I don't know anyone at these companies." Both views make the search harder than it needs to be.

A referral is a small, ordinary thing. Most companies want employees to refer people, because referred candidates tend to be a good source of hires, and many pay a bonus when a referral is hired. For the employee, referring you usually means filling in a short internal form. Your job is to make that form easy to fill in, and to give them enough reason to feel comfortable doing it.

• What actually happens inside a company when someone refers you.
• What a referral does and does not do.
• What it costs the referrer, and how to keep that cost low.
• Whom to ask first, and how to find them.
• How to use AI to rank possible referrers, from your own notes.

The details differ by company, but a typical flow looks like this:

1. An employee opens their company's internal referral tool (often part of the applicant tracking system).
2. They choose the specific open role, usually by job ID.
3. They enter your name and email, upload or attach your resume, and sometimes answer a question such as "How do you know this person?" or write a short note.
4. You may receive an email asking you to complete the application.
5. Your application enters the pipeline marked as referred, and a recruiter reviews it.

Some companies require the employee to know you or have worked with you; many do not. Some let the employee say "I don't know them personally, but their work looks strong."

Recruiting surveys commonly report that referred candidates are more likely to be hired than other applicants, but exact figures vary widely, and nobody publishes reliable numbers for freshers in India. Treat a referral as a way to be seen, then let your evidence do the work. Your own tracker (article 5) will tell you how much referrals help you.

Even when the form takes two minutes, the referrer gives up a little:

• Time: finding the role, filling in the form, perhaps writing a note.
• A little reputation: their name is attached. If you look careless or dishonest, it reflects slightly on them.
• Follow-up: you may message them for updates.

So the best referral requests (article 20) reduce all three: they include the job ID and link, attach everything needed, offer a ready-to-use note, show proof of work that makes them comfortable, and promise not to chase.

Lower on the list:

• Senior managers and executives you do not know. They receive many requests, and a referral from them is no more useful to you.
• People with very large followings. They cannot answer most messages.
• People in unrelated departments who cannot judge your work, unless you know them personally.

• Your college's alumni page on LinkedIn, filtered by company (article 14).
• LinkedIn people search: company name plus "software engineer", looking at people whose current role started in the last year or two.
• The company's GitHub organisation: open an active repository, look at its contributors, and see whether their profiles show they work there.
• The company's engineering blog and talks: authors and speakers are engineers who are already public about their work.

Record each person in your tracker's People tab: name, company, role, how you are connected, what of theirs you can mention, and the date of any contact.

A few rules keep referrals from backfiring:

• Ask one person for a given role. Asking five employees to refer you for the same job creates duplicate work for recruiters and makes you look careless. If the first person says no or does not reply after a follow-up, then ask another.
• Ask for a specific role, by job ID, not "any opening". Article 20 shows why.
• Find out about the timing of your own application. In some systems, a referral creates the application and sends you a link; if you have already applied, the referral may not attach. Ask your referrer: "Should I apply first, or wait for your referral link?"
• Respect a no. Some people do not refer people they do not know. That is fair.

Once you have five to ten possible people at a company, an assistant can help you decide whom to ask first. Give it your own notes, not their full profiles, and do not ask it to find or profile people.

I want to ask one person for a referral for [role, job ID] at [company].Here are my notes on possible referrers (no names):A: SDE-1, joined 10 months ago, backend team, same college (2024 batch),   posts about Java weekly. We have no contact yet.B: Engineering manager, 9 years at the company, rarely posts.C: SDE-2, wrote a blog post on the payments retry system; I commented on it   and they replied.D: Contributor to the company's open-source SDK; profile says they left last year.My background in two lines: [your stack and main project].1. Rank them by how likely they are to respond AND to be able to refer me   for this role. Explain each ranking in one line.2. For the top two, suggest the most honest opening (what I can genuinely mention).3. Flag anyone I should not ask, and why.

An illustrative answer would rank C first (an existing interaction and a relevant topic), A second (shared college and a recent hire on a relevant team), B lower (unlikely to respond to a stranger), and flag D (no longer at the company). That matches the guidance above, and it is your notes, not the assistant's guesses, that make it useful.

Anil wants a referral for a "Software Engineer I, Backend" role (job ID on the careers page) at a payments company.

• He finds 7 possible people: 3 alumni, 2 recent hires on backend teams, 1 blog author, 1 engineering manager.
• His notes show he commented on the blog author's post two weeks ago and got a reply.
• He ranks them and asks the blog author first, mentioning the post and his own idempotency project, with his referral package (article 20).
• The author replies that they are on a different team but refers him anyway, noting "found through my blog post, strong related project."
• Anil records it in his tracker, thanks them, and does not ask anyone else at the company for that role.

• Believing a referral guarantees an interview, then being crushed when it does not.
• Asking "any opening" instead of a specific role.
• Asking many people at once for the same role.
• Starting with the most senior or famous person.
• Applying, then getting referred, without checking how the company's system links them.
• Profiling people with personality-prediction tools instead of being specific and respectful.

• Next: The Referral Request That Gets Answered: Package, Message, Follow-Up writes the request itself.
• For finding people through your college, revisit Learn in Public and Build Your Network Before You Need It.
• For the wider job search, see How to Get Your First Job as a Fresher in India: A Step-by-Step Guide.