Candidates often undersell strong projects by describing them poorly, or oversell weak ones in a way that collapses under a single follow-up question. A clear structure fixes both.
Problem, then solution, then outcome
"Students were manually checking eligibility for 15 workshop tiers, so I built a chatbot that answered common questions instantly, reducing repeat queries by an estimated 40%." Specific, structured, verifiable.
Be ready for "what would you change"
This is close to a guaranteed follow-up. Have a genuine answer — even a small one — ready. It's often the question that most reveals real understanding.
Quantify where you honestly can
"Reduced response time" is weaker than "cut average response time from 2 days to under an hour." Even rough numbers, clearly labeled as estimates, add credibility.
Don't hide the limitations
"It doesn't handle edge cases well yet" said confidently is more impressive than pretending a student project is production-perfect. Interviewers have built things too — they know the difference.