For freshers, projects are the experience section. The right two or three projects — described with links, stack and numbers — routinely beat a thin internship.
Deployed beats local. Used-by-others beats used-by-you. Measured beats vague. A to-do app clone signals tutorial-following; a tool your classmates actually use signals engineering. Prioritize: real users > live deployment > public code > completed tutorial.
"Placement Portal | React, Node.js, PostgreSQL | github.com/you/portal — Built a job portal used by 300+ students; reduced application errors 40% with form validation; deployed on AWS with CI/CD." Also strong: club-event booking systems, department notice boards, mess-feedback apps — anything with real campus users.
"Crop Disease Detector | PyTorch, Flask — Trained a CNN to 92% accuracy on 10k images; deployed as a web app with 500+ uses." Strong pattern: pick a local dataset (college, city, agriculture), answer a real question, publish the notebook and a dashboard.
"Attendance Tracker | Flutter, Firebase — 200+ downloads on Play Store, 4.3★." App-store presence is powerful proof. For non-CS branches: automation scripts, Excel dashboards, CAD models, IoT prototypes — described with the same verb + stack + number pattern.
Format: title line with stack and link, then 2–3 bullets: what you built, one technical decision, one measurable outcome. Start bullets with verbs (Built, Trained, Deployed, Reduced). If it lacks numbers, add scale: data size, request rate, test coverage, users.
Two or three, described well, beat six listed as one-liners. Lead with the most impressive.
Only if you extended them meaningfully. Recruiters recognize standard tutorial clones instantly; add real features, real deployment, or real users.
Yes — a public repo with a decent README doubles a project's credibility. Add a live demo link when possible.
Free, no watermark, no credit card — used by students before every application.
Add your projects in the builder free →