Delete "References Available on Request": The 2026 Proof-of-Work Link Playbook

Here is the uncomfortable truth: no recruiter has ever picked up the phone because your resume said "References available on request." Not at TCS, not at a Bengaluru product startup, not anywhere. That line is not neutral. It burns a line of prime space and quietly signals that you have nothing better to show.

Meanwhile, candidates landing interviews for resume portfolio links have made a simple swap. They replaced that dead line with 3-4 clickable links that prove they can do the job: a live project, a deployed app, a case study, a two-minute walkthrough video.

This guide gives you the exact playbook: which links to use, how to deep-link instead of dumping a homepage, how to track clicks without being creepy, and copy-paste examples for freshers and experienced professionals. Set aside 60-90 minutes and you can rebuild your resume's proof section today.

Think about how a recruiter at a mid-size Indian company actually works. They open a stack of 150-300 applications for one role, scan each for a few seconds, and shortlist maybe 10-15. Their question is never "does this person have references?" It is "can this person do the work, and can I verify it fast?"

• It answers a question nobody asked. Everyone has references. Saying so proves nothing.
• It wastes premium real estate. The bottom of page one is read; a dead line there is a missed pitch.
• It shifts the burden to the recruiter. "On request" means more work for them. Links mean zero work.
• It looks dated. In a market where off-campus hiring runs on GitHub, Kaggle and LinkedIn, old-format cues make you look behind.

A resume makes claims. A link lets the reader check them. Shortlists go to whoever makes checking easiest.

A proof-of-work link points to something you made that a stranger can open in one click and understand in under 60 seconds. If it needs a login, a download, or an explanation from you, it does not count.

• Publicly accessible, no login wall
• Loads on a phone (recruiters often review on mobile)
• Explains itself in the first screen
• Still works six months from now

A homepage link drops the recruiter at github.com/yourname and asks them to hunt. A deep link lands them directly on the one repo, page, or case study that is most relevant to the job. Deep links respect the reader's 30 seconds.

The rule: each link should answer one recruiter question. "Can they build?" links to a deployed app. "Can they think?" links to a case study. "Can they communicate?" links to a walkthrough video.

What you link depends on what the hiring manager needs to believe about you. Here is a starting point for common roles in the Indian market. The salary bands are rough, illustrative ranges only, and vary by city, company, and year.

1. 1.Pick the 3 pieces of work you are proudest of.
2. 2.Rank them by relevance to the exact job you are applying for.
3. 3.Give the top one a deep link; use the other two as support.
4. 4.Swap the order for each application. Ten minutes of tailoring beats one generic resume.

Trackable means you learn whether anyone clicked and from where, so you can tell which resume version is working. It does not mean identifying individual recruiters. Keep it about numbers, not people.

1. 1.Host proof on a page you control. A simple personal site or Notion page lets you add analytics such as Plausible or Google Analytics. You cannot add analytics to someone else's platform like GitHub.
2. 2.Add UTM tags to your own pages. Tag each application so your analytics shows which one brought the visit.
3. 3.Use a link shortener with click counts for third-party pages. Most shorteners show total clicks and rough location.
4. 4.Use video tools that show views. Most walkthrough-video platforms tell you how many times a video was watched.

yourname.dev/case-studies/checkout-redesign?utm_source=resume&utm_medium=pdf&utm_campaign=razorpay-pm-oct26

Your resume has two readers: software that parses it and a human who skims it. Links must survive both.

• Show the visible URL text, not just a hyperlinked word. Some systems strip the underlying hyperlink and keep only what is printed.
• Keep URLs short and clean. A custom short path such as yourname.dev/upi-app beats a 90-character string.
• Put links in the header or a 'Proof of Work' block, not buried inside a text box or graphic that ATS cannot read.
• Submit as a text-based PDF unless the employer asks for Word, and click every link once on the final file.
• Skip QR codes unless you also print the URL. Screen readers and ATS cannot scan them.

PROOF OF WORK
Live app: yourname.dev/upi-expense-tracker (2,000+ monthly users)
Case study: yourname.dev/case-studies/checkout-redesign
Code: github.com/yourname/upi-expense-tracker
Demo (2 min): loom.com/share/your-video-id

These are illustrative examples using fictional candidates. Copy the structure, not the exact wording.

Example 1: CS fresher from a tier-3 college

Off-campus hiring for freshers from lesser-known colleges is rarely about the college name. A working, deployed project with a clean README makes the college name matter less, because it lets the recruiter verify skill in one click.

Example 2: Data analyst with 2 years of experience

Show one strong project and a two-minute explanation. It beats five half-finished repos every single time.

You do not need weeks to turn old work into proof. Modern AI tools compress the boring parts, but you must still verify every claim and number. Never let a tool invent metrics for you.

• Claude Code or Cursor: ask it to read your repo and draft a README with setup steps, screenshots list, and a project summary, then edit it in your own voice.
• GitHub Copilot: helps add tests and comments to older projects so the code looks maintained.
• ChatGPT or Claude: turn your rough project notes into a structured case study: problem, approach, result, what you would do differently.
• Hire Resume's builder: keep a clean, ATS-safe layout while your proof block stays consistent across versions.

1. 1.Broken or private links. A 404 or 'request access' page is worse than no link. Test in incognito, on mobile data.
2. 2.Homepage dumping. Sending a recruiter to a profile with 40 repos makes them do the work, and they will not.
3. 3.No context. A bare URL with no label leaves the reader guessing why they should click.
4. 4.Too many links. Cap at 3-4. More dilutes your best work.
5. 5.Stale work. A 2021 tutorial clone reads as a lack of growth. Prune anything you would not defend in an interview.
6. 6.Leaking private data. Remove API keys, client names under NDA, and real customer data from repos and dashboards before linking.

"References available on request" is a promise. A deep link is proof. Recruiters, especially at product companies and startups, reward whoever lets them verify skill fastest. You now have the exact structure: 3-4 deep links, each answering one question, formatted for ATS, tracked just enough to learn what works.

Start small. One deployed project, one README, one two-minute video. That is enough to outperform the majority of resumes still ending with the same tired line.

Don't tell them you can do the work. Hand them the work.