The problem at least I see with school projects is mainly that these tend to be really hard to read (tabs everywhere, bad naming conventions, etc), and the projects tend to be extremely simple (todo app, blog, etc) with this inconsistency done within a group of 3-6 people where that person can't explain what part they did or how it works. Beyond that, you will also need to know how your tools work for your job along with the algorithm grind. Some basic understanding of things like APIs, Rest protocols, authentication, storage can go a really long way to not only building a more impressive project but also being able to answer questions asked by the job you apply for. Above all, jobs love to see people who want to actually learn, because that's what we do at the end of the day.
It turned out to be true.
With that being said being in computer science is a lifelong learning career and you will learn most of what you need at work and through side projects.
But in order to get started paying attention in class and working on a side project or two will be incredibly helpful to get your foot in the door. Do you know what area of computer science you are interested in?
Also, if you are interested in software engineering getting started as a fullstack engineer is easier in my experience. So being able to build a web app using your choice of technology, being familiar with APIs, and being able to answer easy Leetcode questions would be helpful to get you through junior level interviews. (unless you want to be in big tech in which case the leetcode questions will be harder).
-Do competitive programming.
-Learn new languages and technologies and do some projects.
-Do some research and try to get it published.
-Learn emerging technologies like Artificial Intelligence, Cloud, IoT, etc.
-Choose any one particular area and keep learning in that.
Hope this helps! Good Luck!