The projects on your CV are the same projects on everyone else's CV. Same RAG demo on the same PDFs. Same Kaggle classifier. Same Streamlit dashboard. Same Titanic dataset, same MNIST, same fine-tuning notebook copy-pasted from a Medium article. Your GitHub looks like everyone else's GitHub. Your "final year project" looks like the one three years before yours, and the one three years after.
Recruiters see two hundred CVs a week that all look like yours.
The market changed. The bar moved. The projects that got someone hired in 2021 won't get you a callback in 2026. This essay is about what to ship instead — five projects that signal you've done the work nobody around you bothered to do.
Most students stop at the first phase of a project — sometimes from inexperience, sometimes from laziness — right when the problems start to become interesting. Some teachers and alumni will tell you that's fine, that juniors should focus on junior-level tasks and let the senior work come with time. We disagree, and the labour data does too.
Entry-level software roles have not slowed. They have collapsed.
What was once a junior job is now done by AI. What's left for juniors? To say "yes" repeatedly to a model until it finishes the job. Nonsense. Now is the time for juniors to step into what was once considered beyond their level.
A portfolio speaks before you do — recruiters and clients read artifacts, not transcripts. Projects are where you develop taste, and knowing what to build is harder than knowing how to build it. They teach the full lifecycle — shipping, maintaining, deprecating — not just the fun middle part everyone gravitates to.
Projects that look like work but won't get you hired.
These are the projects every recruiter has already seen this week. They're not wrong to build — they're wrong to put at the top of a CV. Cross them off; what remains is the brief for the rest of this essay.
What good looks like.
Before the specifics, here is the bar every project below should meet. Score the project you would put on your CV today. Be ruthless — recruiters are.
The version every student ships — and the version that gets you on a call.
For each project, toggle between the MVP everyone builds and the shipped version that earns an interview. Same five problems. Two very different artifacts.
Pick one. Not five.
One project, shipped to the standard above, beats five half-built ones every time. Pick the one closest to a real user you have access to — the lawyer in your family, the manager at your internship, the doctor friend. Domain access is the unfair advantage students underuse.
Ship before it's ready. Polish in public. Nobody hires the person who's "still working on it" forever. Write about it. Get one real user — not your study group; one person who didn't know you before, who chose to use it, and who'd notice if it broke. That's the line between a project and a product.
The students who do this will be the juniors who don't get replaced. Everyone else is competing for the seat that AI is quietly removing.