Content is a portfolio, even when it's messy — that's advice I gave 100+ freshers at the VSICS induction seminar, and it's the single biggest gap I see between students who get calls back and students who don't.
What actually gets opened
A README a stranger can read and run in under two minutes. Recruiters skim, they don't excavate. If your project needs a paragraph of setup instructions before anyone can see it work, most won't get there.
Three real things beat ten course completions
A certificate says you attended. A shipped project with a live URL and a repo says you can finish something under real constraints — that's the harder, rarer signal, and it's the one that actually predicts job performance.
Deploy publicly, even the small stuff
A live link costs you an afternoon and changes how every project reads. "I built X" is a claim. "Here's X, running" is proof.
Write about what broke, not just what worked
A short post about a bug you chased for six hours tells a recruiter more about how you think than a polished success story does. It's also, not coincidentally, more interesting to read.
GenAI engineer and AI product builder with 2+ years shipping production-grade AI systems: RAG pipelines, fine-tuned LLMs, hybrid retrieval and multi-modal apps across vision, speech and OCR, architected end to end from ingestion to deployment. Leads engineering for SCULT INDIA's 14-member team, founded the 500+ member TechVerse Enclave community and has mentored 200+ students. Three hackathon first prizes: Changethon 2025 (IIT Roorkee), Product Genesis at Vividhotsava 2025 (CSJMU Kanpur) and BYTEBATTLE (MeetKats).
Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at colleges. Email pranjulrathour41@gmail.com.
