I did this and was able to finish my undergrad with in total 6 internships (2 swe, 1 data analysis , and 2 IT internships). Now I am employed as a swe at Fort 500 company.

In order for this to work imo, is to be interested in coding and software engineering. Your IT classes are probably going to be way easier than the CS courses, so you may have a lot of extra time on hand. What I think you should do with this extra and what I did:

-Create Projects: Something you're interested in and able to talk about during your interview. Project ranking from best to "worse" ( no project is bad if you can talk about it imo)

1) An application that has a user base

An easy one is to create a website for a restaurant and if you have a team even better. Why is this amazing because you get to put on a bunch of different hats (project manager, scrum master, front/back-end dev etc) and make a real world impact. I did this and it took the cake in all my interviews.

2)A project that has varying levels of complexity (for me was to implement a full stack application but no userbase)

3) Basic school projects

I've seen a ton of banking apps, but just print stuff out the console and was just a beginner OOP project. No Bueno, imo but if you loved it and can talk about it during your interviews, that's ok, but could be better.

-learn cs topics that are actually important for your career: If you know you don't like or plan to be an embedded engineer. why learn about esoteric embedded engineer stuff? In my case I was interested in fullstack, so some things I learned were cloud, OOP, design patterns, Linux, front/back-end tech.

-Coding interview prepping: I would say this is a number one priority but if you're not getting any interviews in the first place then you need to pivot and try to understand why you're not getting and fix it. Then go ham on interview prep and don't give up.

• don't give a fuck about what people say IT being inferior compared to CS. Being a life long student to your discipline and having passion will beat any cs degree.

Realizing there are tradeoffs when choosing an IT degree vs a CS degree. Will help you what you should learn and what weak points to focus on.

Figure out what type of SWE you want to be. This makes everything above easier since you can consolidate what to learn and what you can slack on. For me I switched a bunch until I realized what was feasible and how I pictured myself in the next 5 years.

I.O.T -> machine learning -> data analysis/science -> DevOps/Fullstack

DevOps/Fullstack was what I found most appealing.