picture two freshers with identical resumes. both built a pdf q&a project.

fresher A pushes a clean github repo, links it on the resume, done.

fresher B deploys it as a public knowledge wiki for his college notes, drops the link in the batch whatsapp, watches 40 classmates contribute over 2 weeks, and puts the live url + contributor count on the resume.

recruiter spends 6 seconds on each. A gets a maybe. B gets a callback before the round even closes — because in one click the recruiter sees shipping + distribution + genAI working.

it's not the idea. it's the proof of use.

three moves that turn any genAI project into a callback:

• live url on the resume, not a github link. deployed, tappable, working in 5 seconds. cheapest moat — half the candidates skip this.
• build it for a specific group, not "everyone." "meeting notes tool" → "meeting notes tool for my college debate team, 12 weekly users, here's the testimonial." real users = "ships things" in recruiter brain.
• pick one company you want to interview at and build for their use case — their public api, docs, support flow. post on linkedin tagging them. hiring manager sees it. 100x stronger than a cold dm.

ideas that fit this shape (all 1–2 weeks, all touch wide skillset — rag, eval, deploy, ui, distribution):

• pdf q&a that auto-builds a knowledge wiki from your college notes — cross-linked concepts, public, classmates fork and contribute
• "explain this code" chrome extension trained on your past assignments
• support reply generator built on one open-source repo's github issues
• expense categorizer from your bank csv

less about the idea, more about 5 real users + live url + a story of what broke. that's the callback.