Also, a related question, but from the engineers' perspective: What are the biggest hurdles you face when being onboarded to a team as an engineer?
Two things stand out to me:
1) the ability to create content, and have that content consumed, that lets new folks come up to speed. Reading and comprehending is a lot harder for a lot of people than we like to admit.
2) Letting people know that failure and experimentation as part of learning is ok and expected. It’s generally easier for new folks to sit and do nothing than to try, fail, and ask for clarification and help. Paving the path for the latter both culturally and technologically is extremely difficult at scale.
In my experience, CS graduates with any experience lack far behind in skill/knowledge than fresh graduates with EE/ECE degrees. The latter just seem to understand how computer software works and can really do any task, while the former seem to just memorize a whole bunch of ways of doing things with no fundamental understanding of what is going on under the hood, and have to be taught explicit processes on how to do things, with an inability to self learn.
The gunwales.
The biggest initial hurdles I see:
Understanding the process, tools, and little details of local development for the team and product.
Understanding who does what on the team, and how to deal with each personality, role, and processes.