When I interview students/newgrads, they very often carefully simulate the code in their head before running it. Is this behavior learned from whiteboard interviews & written exams? Aversion to seeing errors or test failures? Experienced devs just embrace the fail/fix cycle.
I suspect it may be that it historically has worked for them. In school, you often are the one who wrote the code, you likely wrote it very recently, and there is little long term benefit to writing tests. At work, the opposite is often true.