And software engineering is quite dissimilar, if not completely different to computer science. Creating API's, building user interfaces, testing, has little to do with computer science, or information theory, or mathematics. Yes, it has some overlap, but not nearly as much as academics like to think.
Take an example as implementing a 3D renderer. A computer scientist might argue that underlaying 3D calculations should be correct. A software engineer might optimize for speed, and simply allow incorrect/imprecise calculations, as long as the rendered result does not look very different.
Except underlying that 3D renderer is a whole bunch of Computer Science research that had to be done in order to allow the engineer to make an optimized implementation. And I doubt a decent Computer Scientists would argue that. In fact, you might need some more CS (or science in general) to figure out what tolerance can be allowed for. Further more, while an optimized implementation is good, an optimized algorithm is probably even better, and right there i more CS.
Take an example as implementing a 3D renderer. A computer scientist might argue that underlaying 3D calculations should be correct. A software engineer might optimize for speed, and simply allow incorrect/imprecise calculations, as long as the rendered result does not look very different.