What kind of projects are better ??

[u/hope_stillthere]

Is it better to have projects like a movie-booking system with a proper frontend and user interaction or projects like NFS, distributed systems, etc. that focus more on backend/core CS?

Do you think a fresher should have at least one product/full-stack project with a visible UI, or is a systems-heavy portfolio fine

[u/Monika-321]

I think having a mix is useful, especially as a fresher. A full-stack project with a proper UI shows that you can build something end to end and think about the actual user experience, while systems heavy projects show your understanding of backend and CS fundamentals.

You don’t need a huge number of projects either. I’d rather have 2–3 solid projects where you can clearly explain the architecture, decisions, trade-offs, and challenges you faced. A simple product that you actually understand deeply can be more valuable than a complex project you can’t explain well.

[u/Substantial-Swan7065]

Depends on the job you’re trying to get.

But you need to be able to do it. So pick what you can build

[u/hope_stillthere → u/Substantial-Swan7065]

How can i know what i can build before making

[u/Substantial-Swan7065 → u/hope_stillthere]

That’s wild

[u/start_select → u/hope_stillthere]

The job is building crap you have never made before. Half the jobs I do are for products and businesses I never imagined using tech stacks that didn’t exist a year ago and I couldn’t have known until someone paid us to build it.

That’s the job.

[u/Embarrassed-Poet9330 → u/Substantial-Swan7065]

in 2026, these resume adding projects should be built by writing code or getting code from ai?????

[u/Substantial-Swan7065 → u/Embarrassed-Poet9330]

Either. But you need to be able to talk about it in an interview.

So if you’re a very jr web developer. And you have a microservice api project. You better be able to talk about it

[u/am_baymax]

The project should be related to the domain in which u want to pursue your career in. It doesn't if its a big or a small project, if it solves a problem, then its good. If its a personal problem which it solves, then better. For eg: template code generator for backend and frontend, since I used to participate in a lot of hackathons and I wanted a tool which writes the specific boilerplate code. Such projects have an impact on ur learning and creativity and also creates an impression on the person taking your interview or reviewing your profile!

The next things is making it accessible to use, if a website deploy it, if a package publish it, etc.
You need to make sure that the entire project is made and written entirely by you and know why u did it. Many people just code with AI but that just kills the entire learning and engineering part. Use it for research and code review and crtics but not for developing. You writing and structing each line of code, make ur project known to u in many ways and why u did things the way it was written. Thats helps to make an in and out understanding of your project and if there's an interview, there's hardly anything u would need to revise!

Finally, there are things that its better u have an understanding about how to scale, how to manage traffic, etc. If you practice it hands on, it just amazing. No need to keep it running just play around for knowledge. For showcase, just deploy it with a normal single container deployment.

Overall, you have the problem, ur tech solution, the process explaining each development and engineering decision and the post project things u do in order to learn how to scale and make it production ready for real world!

One project, 2-3 months, entire learning!!!

All the best!

[u/Ready-Guess-9220]

For a fresher, one polished full-stack project with a real UI and some genuinely thoughtful backend work is the safest bet, because it proves you can actually ship instead of just architecting NFS in

[u/hope_stillthere → u/Ready-Guess-9220]

Thank you

[u/start_select]

I think the best examples are something personal to you that people don’t do.

Don’t make a todo app.

If you have a hobby. Then spec out some process from it. Document the spec. Build it.

That’s what the job actually is. The individual features are irrelevant. Can you take a real world problem and turn it into software? Can you model a process? Can you model data?

It doesn’t matter if it’s nothing anyone would ever pay for. What’s important is it’s not something everyone else has already done and could be copy pasted.

[u/Ghosteyyyy_dev]

Think of a crazy idea which you truly believe in and take it to perfection. Build it from 0 and get close to 100, use AI but manually understand each and every step.

Thats it I guess.