We see this with engineers of all ages, but especially with new grads. All have just spent 16 to 22 years working under a model where: you get an assignment, you come up with a solution, you are marked on your result, and then you move on…
Our education has trained us that involving others is something done at the end.
A lot of our new hires need help shifting their approach (and getting over insecurities) to consider that all their products need iterative review well before the work is complete.
My experience has been "Get stuck, avoid the senior engineer because they have no bloody clue what's going on and talking to them actively makes things worse for months afterwards".
I'm not a new dev (but I am a new data scientist) and can definitely relate to what you said. I'm so used to "if you get stuck, just figure it out" as the norm for things I'm assigned to do, and getting used to "I'm stuck, I should reach out to someone who's more experienced than me" has been difficult. I'm always afraid of inconveniencing or interrupting my higher-ups, even though they never seem to be bothered by it. I guess it's just an irrational social fear.
Our education has trained us that involving others is something done at the end.
A lot of our new hires need help shifting their approach (and getting over insecurities) to consider that all their products need iterative review well before the work is complete.