3 ms·

>come in at 1 and work till 10 I did an internship at Google, so I have only seen one team in action for a small period of time. That said, there were a shocki

>come in at 1 and work till 10 I did an internship at Google, so I have only seen one team in action for a small period of time. That said, there were a shocking number of meetings-- daily standups, one-on-one meetings, video conferences with California, weekly team meetings, cross-functionals and a few extra bits of coordination bureaucracy. These were scattered throughout the day in a way that put firm limits on how free of a schedule you can make for yourself.

nostrademons 16y ago
It depends a lot on which team you're working on, how tightly they're colocated, and what your role on the team is. When I was working on the effort to move all the different search properties into google.com - which involved teams in 5 different offices scattered all across the U.S. and China - there were quite a few meetings, several at odd times to accommodate the time zones. (My tech lead took the brunt of that herself, though.) When I was working on the visual redesign, which mostly involved a tight team colocated in a single cube - I came in when I felt like, because if I needed to talk to someone, I could just turn around and ask them something. Also, oftentimes interns don't have a firm grasp on which meetings they can skip and which they really should show up for. There are at least 4 weekly or bi-weekly meetings on my calendar that I rarely go to unless the particular week's topic is relevant to what I'm doing. I always go to meetings that are specifically scheduled with me, and usually go to the daily standups. It takes a while to develop the organizational awareness to make the distinction, though a usually good rule of thumb is that meetings that someone specifically sets up with you should be attended, while meetings that you're invited to simply by virtue of being a member of some group can safely be skipped.

nostrademons 16y ago

It depends a lot on which team you're working on, how tightly they're colocated, and what your role on the team is. When I was working on the effort to move all the different search properties into google.com - which involved teams in 5 different offices scattered all across the U.S. and China - there were quite a few meetings, several at odd times to accommodate the time zones. (My tech lead took the brunt of that herself, though.) When I was working on the visual redesign, which mostly involved a tight team colocated in a single cube - I came in when I felt like, because if I needed to talk to someone, I could just turn around and ask them something. Also, oftentimes interns don't have a firm grasp on which meetings they can skip and which they really should show up for. There are at least 4 weekly or bi-weekly meetings on my calendar that I rarely go to unless the particular week's topic is relevant to what I'm doing. I always go to meetings that are specifically scheduled with me, and usually go to the daily standups. It takes a while to develop the organizational awareness to make the distinction, though a usually good rule of thumb is that meetings that someone specifically sets up with you should be attended, while meetings that you're invited to simply by virtue of being a member of some group can safely be skipped.