The first thing I was asked when I interviewed with Microsoft was what I wanted to do and what I wanted to avoid. I said, no frontend, something related to distributed systems and they put me up for interviews with an Azure team.
With Google, it was like "interview first, accept the offer before knowing where you are going to be placed, and we will put you in some team".
Google absolutely has the problem you described and I forgot to mention it in my prior comment. With Google you have no clue what team you'll be on when you're evaluating the offer, but once you've accepted the offer you're given more choice with regards to placement.
On the Google case, even being an industry hire, it was like pulling teeth to figure out where the offer actually was, and who I would be working for, and being able to actually speak with them (as your manager is key to success). I was also told during the interview that they just interview you in general at Google, not for a particular team, which was also unsettling.
However, once you accept a Google offer you're given more choice as to what team you'll be on. With Microsoft (if you weren't a returning intern) you're given very little to no choice and it can be quite arbitrary where you end up.
Certainly both of these systems have massive flaws, but I think the Microsoft system would lead to far lower retention for non-intern college hires.
I guess I was lucky because I'd already had relevant experience, so I knew exactly what I did and did not want to do. Luckily, the offer I went with was up-front and I ended up doing exactly what I wanted to do.
Playing devils advocate, could it be a lack of experience that is the issue with new hires?
People interested in backend work get placed on frontend, people interested in frontend work get placed on backend. As a result, retention for Microsoft college hires is rather poor. Contrast this with Google where once you're selected you're often given a choice of a few teams and you can indicate your preference.