How One Bad Internship Built a Framework for Vetting Campus Job Offers

A software engineering student in Bangalore accepted a campus placement at a small startup without researching the company, later finding himself the sole IT employee managing over six hours of solo development work nightly alongside college. He left the internship five days before his semester six finals, citing no mentorship, shifting requirements from a non-technical founder, and no new hires. Reflecting on the experience, he identified the 30-minute window between a campus recruitment presentation and the application deadline as the most critical decision point in a placement season. He subsequently built a personal screening framework that involves reading job descriptions critically, checking whether the tech stack is realistic for a fresher, and verifying that role titles accurately reflect actual responsibilities. His key finding is that vague or inflated job descriptions often signal a poor fit, and that rejecting mismatched opportunities before applying is far less costly than discovering problems after acceptance.