The actual mechanics of turning a class project, final-year project, or lab work into a CV bullet that reads like real experience — not just a course title.
"Built a web app for my final-year project" is a common line on a first CV, and it does almost no work — it names the deliverable and nothing else. A university project genuinely can read as real, credible CV content, but it needs the same specific ingredients any other bullet needs: what you actually did, the tools or method involved, and an honest measure of the result. The difference between a project bullet that gets skipped over and one that gets a recruiter's attention is almost always specificity, not the project itself.
The difference between a project bullet that gets skipped over and one that gets a recruiter's attention is almost always specificity, not the project itself.
"Built a web app for my final-year project" tells a recruiter almost nothing: not what problem it solved, not what tools were involved, not whether it worked, not how large or complex it actually was. It's a title, not a bullet — and a recruiter skimming a CV in a few seconds has no reason to read further into it.
The fix isn't making it longer, it's making it specific: name the actual technology or method, describe the scope in concrete terms, and include a real, honestly-stated outcome — a grade, a working demo, a specific feature that functioned, a measured performance number if one genuinely exists.
Before: "Built a web app for my final-year project."
After: "Designed and built a full-stack inventory-tracking web app (React, Node.js, PostgreSQL) as a final-year capstone, implementing real-time stock updates across 3 simulated warehouse locations; received the highest grade band awarded in the cohort."
Everything in the "after" version is something the student actually knows and can speak to in an interview — the tools, the scope, and a real outcome (the grade) — none of it is invented or exaggerated, it's simply specific instead of vague.
Group and team-based coursework is common, and it's completely fair to include — but the bullet should describe your actual contribution, not imply the whole project was solo work. "Led the backend integration for a 4-person team project" is honest and still reads as a real, specific contribution; claiming sole credit for group work is the kind of overstatement that falls apart under a follow-up interview question.
If your role was narrower (one specific feature, one specific analysis), naming that specific piece precisely is stronger than a vague claim to the whole project — specificity reads as more credible, not less impressive.
A dedicated "Projects" section works well when you have several worth including, or when projects are your strongest content overall (common for technical/engineering fields). If you only have one or two strong ones, folding them into an "Experience"-equivalent section alongside any real work history is equally valid — the goal is making sure they're not buried, not following a specific section-naming rule.
“Rewrite each project bullet with the same three ingredients any CV bullet needs: a strong action verb, the specific tools or method, and a real, honest outcome.”
Yoxon's AI CV Studio rewrites your project bullets for the specific job you're applying to, keeping every detail grounded in what you actually built — never inventing outcomes that didn't happen.
Get Full Studio Access →Should I list a group project as if I did it alone?
No — describe your specific, real contribution honestly (e.g. "led the backend integration for a 4-person team project"). It's still a legitimate, specific bullet, and it holds up under a follow-up interview question in a way an overstated solo claim wouldn't.
What if my project didn't fully work or wasn't finished?
Describe what you built and what you learned honestly — a project that surfaced a real technical challenge and how you approached it is still legitimate content, as long as the description doesn't claim a working outcome that didn't happen.
Should coursework projects go in a Projects section or under Experience?
Either is valid. A dedicated Projects section works well if you have several worth including or if projects are your strongest content overall; folding one or two into an Experience-equivalent section works just as well if that's a better fit for your specific CV.
Do I need a grade or measurable result to make a project bullet strong?
It helps when one's genuinely available, but it's not required — a specific description of scope, tools, and your actual role is still a strong bullet on its own. What matters is specificity, not necessarily a number.
How many university projects should I include?
As many as are genuinely substantial and specific enough to describe well — two or three strong, specific project bullets are more useful than five thin ones. If a project can only be described vaguely, it's probably not worth the space.
More guides