I might be able to provide some useful information - I actually was a Comp Sci student who basically stumbled into robotics as a profession with essentially only having a background in coding, software and data from school and absolutely 0 prior robotics experience or knowledge whatsoever.
I'm a roboticist at a manufacturing business of ~60 people, my main time hog is programming an arc welding unit that basically constantly gets new, enormous jobs in small batches. Also because I'm sort of an over-eager people pleasing naive person I'm also the systems administrator here which I'm sure you can imagine is... busy. Lots of computers to turn off and back on and all that.
Most of what I do is OLP (offline programming) which means I create jobs (programs) for our bots on my workstation using software that does a relatively good job of simulation before I load it onto the actual robot. It's absolutely never even close to accurate - but the sim software is more for my benefit so I know what I've done and what needs to be done and such. My programs are on-average longer than mass-production by a large margin (like... anywhere from 6 or 7 welds to over 100) so they get a little... uh... intricate is a nicer word for convoluted, right?
I cannot restate enough times or with more conviction that I knew nothing coming into this. Less than nothing, if that's possible. In a nutshell, the situation I came into required learning a metric buttload of brand new stuff - robotics 101, for starters - everything about the manufacturers of our automated systems, their respective coding languages (no, there is no unified language yet and yes, they pretty much all use their own), everything about the offline programming and sim software, CAD modeling (again, basically no background beyond having a pirated version of autocad as a kid), digging up my linear algebra notes and text (I hope you really enjoy planes and axes and relativity and all that good stuff :D).
Welding, I knew nothing of beyond "don't stare at it." CNCs, PLCs, never heard of them. And then just throw in the fact that I'd never even been in a factory setting let alone worked in one and tradespeople kind of intimidated the hell out of me (which was so dumb, turns out they're generally far more chill than the nerd types I generally was comfortable with).
So these are just like... what comes to mind while I sit here on my smoke break. I could go for hours but this message is probably already enormous. The biggest challenge though? The absolutely relentless, well, I don't want to say failures but let's call it constant lack of success. Until it all started to come together, there were long stretches of some pretty serious doubt that I'd be able to do it. Hell, when I interviewed for the job, I'm not even kidding when I say I did my best to convince them that I couldn't do it because I wasn't sure that I could. But they needed someone and for whatever reason were able to see something I couldn't. The last person in my position sort of got them up and running with all this new stuff and then immediately left so I didn't have anyone to reference or anyone to train, or mentor me because even with so little experience I was still the most experienced person here.
Actually it's funny, looking back I'm glad the tech support guy aspect was there because that easy stuff I'd been doing since I was a kid sort of provided some constant easy personal wins that kept me from completely feeling like a failure, aha. It took time, but I'm pretty good at this now. Everything I thought I'd hate about it sort of ended up being really neat and I like being a nerd covered in dirt all day. Every day is different, I still know virtually nothing but the thing is, this field is still incredibly new and i'm constantly meeting people and seeing these opportunities that I didn't even know existed.
There's not a lot of "robot psychiatry" degrees even, yet. Or programs. CNC and stuff sure but at least around here there's almost nobody really doing this stuff - my employer had been advertising this job for months and if I was the best there was? Yeah. So much opportunity. I guess my point in this little introduction was that it doesn't really matter if you have no idea where to "start." Just... start looking for jobs like that, even if they sound like something you won't like (you totally will.) I mean, beyond computer science - my real skill is being able to pick up coding languages quickly, a relative fearlessness when it comes to playing with new, expensive technology, and apparently a ton of patience and perseverance that i'll be honest I didn't even know that I had until all this.
If you have any questions, please, fire away. I don't know if you ever thought about being a roboticist in a manufacturing environment but it is far more fun and exciting than it sounds.