News for hackers. Stuff that matters.

A comment on What does it take to make Google work at scale?. Parent comment

Re:What does it take to make Google work at scale? by cmrdporcupine on Monday August 17, 2015 @08:29PM (#10076971)
Transferring within Google is easy. Yes, you would be expected to stay on your first project for a reasonable chunk of time, but transfers after that are not only possible but expected.
[ Parent | on HN ]
Re:What does it take to make Google work at scale? by ridiculous_fish on Monday August 17, 2015 @08:47PM (#10077027)
How do you reconcile that with your claim elsewhere that "staff turnover is very very low?"

I worked in the Mountain View office. Transferring is indeed easy, and people did transfer frequently. As a result turnover was high, and it was hard to build friendships, or gel as a team.

[ Parent | on HN ]
Re:What does it take to make Google work at scale? by cmrdporcupine on Monday August 17, 2015 @09:17PM (#10077100)
I thought turnover in this context was the usual use of turnover as in, people leaving the company and new ones being hired.
[ Parent | on HN ]
Re:What does it take to make Google work at scale? by ridiculous_fish on Monday August 17, 2015 @09:58PM (#10077201)
Ok. I'm not sure the distinction is that important when it comes to team camaraderie though.
[ Parent | on HN ]
Re:What does it take to make Google work at scale? by aiiane on Monday August 17, 2015 @09:36PM (#10077144)
Team turnover vs. company turnover. It's one thing to learn a new project, another to learn the entire ecosystem.
[ Parent | on HN ]