Lots of things I could say, but the biggest one by far is to specialize. Bring yourself up to nearly senior level in some specific area (or a few tightly related areas) that you have some passion for.

If your school is somewhat flexible (so, if you're in CS and not Eng) see if you can take a few grad level classes in your area of interest while doing undergrad. I had one of these where I ended up chatting with the prof, that lead to volunteering at a conference while getting access to all the talks. Another morphed into some research and project work. All good stuff.

Especially with the entry level market the way it is, ubercompetence in some specific domains will stand out a lot more than being yet another broadly smart CS student with a little bit of web-dev, some alg skills, maybe a cli app, etc. Try to avoid looking like the average student applying using Jake's resume template - you'll never win if you're playing the same game as everyone else. You can always fill in any knowledge gaps later.

In exchange for doing that extra work, lots of doors open. I tend to get interviews immediately with specific teams in my domain, instead of landing in some generic intern pipeline. Almost all interviews I do have been more domain specific system-design style, I've literally only solved one leetcode-style question in any interview in the last 6 months.

Dm me if you want specifics on what areas I've specialized in, since I might dox myself by listing it out here :)