Typical day manager google

Matt Welsh has been with Google since 2010. His current position is called “tech lead manager” (TLM): Welsh is responsible for the technical side of projects and for managing a team of people. More details about his role in the company can be read here , if there is such a desire.

The other day, Welsh laid out a detailed schedule of his day, which I think will be interesting for most readers of both Megamind and Habra with Geeks. According to the author, every day he is different from the previous ones, so he did something like an average routine, which can be found in the sequel.

6:45 Getting up, preparing the kids, preparing breakfast for them and for yourself, shower.
')
8:30 Trip to work by bike (about 10 minutes), breakfast, workplace.

8:45 am Checking various parameters of corporate projects - traffic, network operation, status of data centers.

9:00 am Checking email. Welch has to constantly get distracted by email, but working with Inbox has partially fixed this problem.

9:30 Work on a description of a new feature that the Welsh team is developing for Chrome.

10:00 Chat with one of the team members, proceedings with a bug report. Log analysis, bug report update.

10:30 Morning is not filled with meetings, so Matt has a whole hour of his favorite activity - the creation of code. He understands MapReduce in Go, adding new features, and trying to make it all more convenient. Matt does not have time to finish - there are other duties that are more urgent.

11:30 Video chat with a colleague from Google headquarters, discussion of a new project.

12:00 Hike to the cafe for lunch, reading Hacker News.

12:30 Connection with the team, discussion of the agenda for one internal corporate conference.

13:00 Meeting with the team responsible for recruiting new employees for the project. Sometimes it is easy to choose an applicant for a place, sometimes it is very difficult.

14:00 Weekly team meeting. At such meetings, usually one or several people represent the entire team so that the rest can continue to work on the project. Discussion of the results, discussion of the progress of the project. Sometimes quarterly goals are discussed at such meetings. Sometimes meetings are not held at all.

15:00 Individual meetings with employees. The goal is to discuss the technical details of the work, clarify some psychological issues, discuss the career plans of employees.

16:00 Three days a week, Matt leaves his job an hour earlier in order to ride an hour on a bicycle.

17:00 Returning home, shower, cooking dinner with the family, chatting with the kids.

19:00 Preparation of children for bedtime, reading books.

20:00 Work with e-mail, if something is missed in the morning. "Taking work at home" Welch avoids. Then - a movie or a book, chatting with your wife.

Matt notes that he is now involved in a much larger number of projects than at the beginning of his work in the corporation. He has a lot more meetings with people now, and almost all the technical work, programming, etc. perform team members.