I would not mind full RTO in a shared office, with possibility to isolate for 1 on 1 code reviews/pair programming.
Also I'm the definition of a mid-level dev, but i'm the only one pushing for more communication and shared time, organizing remote tea breaks, pair programming sessions, weekly code review and bimonthly 'formation' where we can show off skills or domain specific knowledge to others. I feel that now that I have enough seniority to propose that regularly, we are a better team, and better for juniors/interns, even if we are even less in the office than we used to be.
Many global open source development projects are very, very, successful. There's no office there.
If anything, a fully remote set of developers should encourage a significant uplift in information transfer via design and documentation.
Walking across the office and asking 'the guru' how X works, means there's little incentive to share that knowledge, simplify the code, and document it.
And that's a problem that has existed in most companies forever.
"Juniors" should be self-starters, and the 'interaction' is often and frequent code reviews.
strongest does not need to be in the same physical location as the juniors to interact with then, and that has being the case for decades already, it only got easier over time..
* Juniors need help in a structured, systematic way, which is not dependent on who is or is not in the office.
* If a team member (no matter if it's junior, new, or just anybody needing help with their ticket) can not receive help and has to fight with his task alone, you have a management problem, not WFH/RTO problem
* In my humble experience, collaboration online is much better than in open-plan offices where you either disturb your colleagues by loud talk or need to find some private room (good luck with that) that is usually smaller than a farm animal's cell and gets uncomfortable after 15 minutes.
* The whole discussion is moot because if you force RTO you will lose seniors, so who will do this whole mentorship?
I work with people in 4 different continents, in Europe my team is spread around 4 different countries. We manage to interact, remotely.
I do not understand why people think being interactions require an office together, there are other ways to foster interactions, it's a culture. If the culture is bad remotely then it's also bad in office, just in different ways, the only thing a remote team loses is the ability of poking someone else's shoulder which is generally good, you don't want interruptions. You want people to have enough slack in their work that they can be called upon for pairing or helping with something.
If everyone is so busy remotely that they don't interact anymore then in-person you'd be having issues with frustration from senior devs being interrupt to help juniors. It's the same issue, just presenting itself to the surface in a different way...