It also cuts off some jobs as you become 'overqualified' (see: We think you'll bugger off to a better job first opportunity), but the ones that open up are better in general usually.
For what it's worth a side effect of the whole "college degree required to even look at you" type of certificate inflation combined with the fact that the labor market didn't exactly rebound as hard as many people thought it was going to have meant that employers are much less likely to reject you for being "overqualified" now than they were in the past. It still happens occasionally and in extreme cases, but a lot of companies have been taking advantage of the worse market to get lots of experience/education for what is, from their point of view, a cheaper price. (Course that's kinda bad for us, ideally we would have enough positions at the levels of education we actually have and get paid the amount that we deserve, but hey, you still gotta eat

).
That said yeah, network network network. Getting a job is, as mentioned before, mainly based on who you know, and only then based on what your skills are. Obviously you need to have some qualifications (though how much you actually
need depends heavily on the field/etc.), but get to know your professors; they're the ones who will be writing you reference letters that will help you land the good positions later.
CIS in particular, while not quite as high-end aimed as a more theoretically-focused pure CS degree, still has a very large amount of things that can be done with it, ranging from being the "tech guy" at a smaller company to working as part of a large team in one of the big software names. You don't necessarily need to pick now, but I'd suggest by the time that you near the end of your Bachelor's degree that you try to narrow down a bit what exact fields you particularly enjoy (or hate less), and possibly use that to determine if you want to go for a job right then or shoot for higher education. Some fields (like AI development, for example) tend to require higher levels of education for a lot of their "entry-level" stuff, while in other fields (web development) you can pretty much jump straight in with just a bachelors and be just fine (and salaries are exceptionally good right now in a lot of places).
My last piece of advice is to code up some stuff on somewhere publicly accessible like Github and use it as a sort of "portfolio". Employers
will look at that stuff, and it's not totally unheard of for some of the more employer-focused job searching stuff to actually contact people based on their personal projects. It's always good to have some work showing that you do know how to code, or even better that you know how to work as part of a larger open-source team.