I am an EE and it is easily work.
In school all you are getting are grades and if you get a project to 90%+ completion you can squeak by. Plus the vast majority of projects you do have already known and worked out solutions so there is very little chance you are completely in the weeds. It felt stressful at the time in undergrad but working for a while and going back to grad school really put it in to perspective. And that wasn't even engineering work.
In work it depends on what is happening but if schedule is king and things get messed up (through your fault or not) it gets very stressful getting things back to a good place while still maintaining schedule. On top of that you may not really know how to fix the issue while you are being asked to give estimates on when you will have it fixed. As you become more senior/trusted you get better at these estimates but they carry far more weight.
I owned the top level of a chip, last one to touch it before it went off to the fab, signed off on all the final full chip quality metrics. Even though I checked and double checked my results and had other people cross check my results waiting for the chip to come back was pretty stressful. A dead chip would cost huge in new masks not to mention slipping the tight schedule by months, enough to put the whole project in jeopardy. Plus the 130 engineers waiting to get this chip back to start testing would be pushed back. I don't care how cool and calm you are there's bound to be some stress in a situation like that especially when we had a fix at 2am the morning before we delivered so I had to whip through all the analysis and quickly reaffirm we were still good to go. Ultimately the chip worked, which shouldn't be surprising given the testing that goes into it but that's much heavier stress than any piddly little school project ever.
Now, that being said school was higher baseline stress than work but when delivering near deadlines work easily trumps school, even when things go smoothly.