I think you over promote the utility of the formal methods taught in the degree.
Not once did I use Laplace in EE. It was all cheat sheets or applying data sheets and doing some adhoc calculations in excel or taking a wild guess and iterating.
After twenty years of doing IT related stuff I’ve forgotten how to even differentiate stuff.
1. I did learn them well, and so I did use Laplace quite often in EE.
2. I jumped careers not into IT, but into tracks which leveraged both programming and a mathematical skill set.
I'll mention: I'd be bored out of my wits doing just IT. The intersection of IT and math includes computer graphics, visualizations, robotics, machine learning, fintech, image processing, and a ton of other stuff I find much more fun and fulfilling.
That's not an implicit commentary on your path, by the way, just an explanation of mine. We all have different goals, desires, values, constraints, etc.
Yeah, I have an EE degree but have only worked in software, and I have to say you can bring any kind of mathematics to the job if you have the imagination to find the places where it is an advantage.
I sought areas where I could learn more math and use it to stand out from the crowd, albeit to mixed results, because if your manager can’t read your analysis paper he may not be impressed either, and sometimes the reverse.
If you know a little bit of math, there's no benefit.
If you know enough math to jump to e.g. medical imaging, robotics, controls, simulators, image processing, ML, or similar, there's a ton of benefit.
An EE degree ought to give enough background to get there, although it may involve a year or two of study in a particular domain, and a side project to prove you have the skills.
Not once did I use Laplace in EE. It was all cheat sheets or applying data sheets and doing some adhoc calculations in excel or taking a wild guess and iterating.
After twenty years of doing IT related stuff I’ve forgotten how to even differentiate stuff.