My bachelor's was actually called Software Engineering (it was 10 years ago, so it migh've changed a lot), on Faculty of IT. It was mostly just applied programming (but also indepth - from assembly through smalltalk, to bash, C and Prolog), with a lot of courses about SDLC, UML, DevOps, and all that.

We also had a lot of advanced math, from integrals to logic, and some CS like data structures, algorithms and all that jazz.

It was not as theoretical as actual Computer Science on other faculties, and was more devops oriented, but I did learn a lot of fundamentals about every language I can imagine, including lambda calcul, and also all the math I could ever need. And I'm pretty glad I was forced to learn about proper processes, am able to read and correctly design an UML, and have some insight into various types of the SDLC - which apparently isn't that common, judging by my experience when actually working. Not that it ever matters - all it ever got me was being internally annoyed that people are using/doing it wrong, but it's not a big deal because everyone understands eachother, and there's no reason to point it out and be smug about it.

But yeah, CS was mentioned a lot, but the difference was mostly that CS is theoretical and way more math heavy, while SWI is pretty similar in most of the circulum, but instead of obscure theoretical proofs about big O of algorithms, you are learning about UML and SDLC.

Also, I got to do an Ethical Hacking optional course, which landed me a job in cybersec and started my carrier (before I moved to gamedev), so that's also nice.

In general, it gave me a lot of "technical soft skills", it was also team project oriented and asked us to have all the requirements and documentations and architecture designs 100% formally written, and that is a really good skill to have.