While at a previous job, and being responsible for onboard new co-workers, having easy tasks ready at day one help create a sense of purpose and being part of the team.
We would alway try have a new co-worker deploy something to production on day one. Ideally something they could point to on the website a say "I did that". Combined with your point 6, letting them know that they did something that mattered created a sense of being part of the company on day one.
It just depend of the company whether or not pairing up with someone makes sense. If you don't really work that way day to day, then you shouldn't give new employees that impression. There is however a point to not having people feel like they are just picking off a list of never ending tasks, which could just as a easily have been solved by someone else.
1. Pair programming: lots of pairing between senior and junior devs.
2. Improve the onboarding docs: It helps when you have a set of onboarding work and the new hire does a good job improving and clarifying them as they learn
3. Easier tasks: we almost always have a set of tasks we need to do that’s easier, and we can get someone started on these
4. Hiring self starters: I think it’s important for people to “own their one development”. It’s incumbent on them to own their onboarding as much as it is on the team
5. Find a place to apply unique skills: it usually doesn’t take too long before the new hire sees an area where they have past experience that can help solve a pain point. This is important to encourage.
6. Lots of positive encouragement: obviously it’s important for the whole team, especially managers, to create at atmosphere of trust and safety where the new hire can give and receive frequent feedback.