I don't mind it being me, as a matter of fact, it's often me, as I am in a more senior position and have a lot of historic context. However, a lot of time has been spent on documenting most things, so often I am just going over the docs with the new onboarder, which is okay, as long as it's done in a structural manner.
> You don't have normal boundaries. Grown-ups at work know that they will interact with other people. You inventing that people should not interact with you, or interact only in your own terms even when it is inconvenient for them.
I don't mind interacting at all, nor do I mind onboarding. I do mind, however, being interrupted all the time, on information, that could easily have been condensed in an onboarding package if the company gave people the space, time and initiative to create such a package.
What I am pointing out is that the OP experienced bad onboarding and thought the solution to that is being in-person in the office. I would argue what they simply had was a badly planned onboarding, with randomly shared responsibility across the team, and an ad-hoc learning plan. If the OP's company uses that lesson and makes a better onboarding process, that'd be great and they might even reconsider the need to be there in person.
> you are complaining about doing your job: working with colleagues and sharing information so that they can progress.
I would love share the information, but I want to do it in a structured manner, and not in chunks and without disruptions.
That's why schools and unis have classes, and classes have predictable and scheduled time frames. It's not just a building with teachers, and random children entering ad hoc and asking whatever question came to their head, then leaving, and coming back 5 min later.
And what's wrong with wanting lots of this information to be self-service? That's the whole idea of knowledge bases, of onboarding docs, of developer handbooks. What does it have to with people being in person or not? I'd argue if the OP's company spent the effort in actually putting all that knowledge in writing, they will have an easier and less disruptive onboarding to the team, with reduced bus factor, and clearly documented steps.