News for hackers. Stuff that matters.
Re:How Google Sold Its Engineers on Management by com2kid on Monday April 20, 2015 @03:41PM (#9410383)
I am a manager, who also serves as a tech lead, for the record I'm at Microsoft.

My job has a number of facets. One is to help provide mentoring to junior engineers. I have seen entry level engineers who never had any mentoring at all, and they end up stagnating. I have seen, in some cases, the same engineer, moved onto a team with a strong technical lead who believes in a lot of 1 on 1 mentoring, and watched that engineer undergo dramatic growth.

I also know a number of engineers who never got that sort of technical mentoring, and I watched as their career stagnated.

So that is the first part of my job.

Another part is to provide technical direction. I have smart people working for me, problems tend to have more than a single good solution. Put these two facts together and there is, on occasion, some disagreement about how a problem should be solved. At that point I step in and make a decision so that something can be done. Design by consensus does not work. I have seen "democratic" teams spend over two months debating the merits of various solutions that both had about equal, but different, benefits and drawbacks.

At some point, someone just has to make a decision.

I also am responsible for things like enforcing a coding standard (yes it is arbitrary, but I have long term responsibility for the code), reminding developers to write their unit tests, and worrying about our branching structure.

Next up, I am here to be the voice of my team. I represent my team in meetings, presenting the technical aspects of our plan, coordinate our APIs with other teams, and provide technical input to other teams' discussions.

I work with UX, PM, Marketing, and upper management to ensure the product's overall success. When technology adoption decisions need to be made, I am the one going around campus meeting with other tech leads to understand what they have to offer. When external companies present respond to an RFP I am the one going over their proposal, emailing them back asking for additional benchmarks or to clarify their measurements.

And finally I am the one that shit rolls to. If my guys make a decision, I am the one that goes in front of management and takes responsibility. No one yells at my developers, no one talks down to them, no one hurls insults at them. If one of my engineers makes a mistake, I am the one who stands up in front of our GM, and the first thing out of my mouth is "it is my team, I take responsibility for this happening."

When things get to hot at a meeting, I'll get a text message requesting my presence. I tell each one of my employees, "I am the one who is getting paid money to be yelled[0] at, if someone is mad, you direct them to me."

I really don't understand how a manager with 50+ reports can manage all of this. The guidelines I've seen is that at more than 7 or 8 reports you just don't have time for anything but the most basic of career management advice help.

Managers are supposed to meet 1:1 with employees for an hour each week, any less than that and things start to feel sort of distant, I know from first hand experience when I don't meet with my manager for several weeks! Combine this with the technical and non-technical roles that managers have to fulfill, and I do not see how 50 DRs could ever work.

Re:How Google Sold Its Engineers on Management by gramerc on Monday April 20, 2015 @04:08PM (#9410541)
I am a manager, who also serves as a tech lead, for the record I'm at Microsoft.

Ex-MSFTee and Google SDE here - At Microsoft my manager served both as a manager in a traditional sense, as well as a tech lead. At Google, my manager and tech lead (TL) have always been distinct roles filled by different people. My manager, though an experienced dev himself, leaves all the various aspects of daily technical leadership to his TLs and focuses on just people and project management. From a line management perspective, both my TL and I report to the same manager.

My experience is that this organization allows managers to manageably have a lot more DRs than my managers at MSFT could. Another benefit is that the TL role is a natural fit for people who do want to step into a clear role that allows them to increase their impact and leadership as senior engineers but are not interested in traditional people/career management work.

Re:How Google Sold Its Engineers on Management by boomzilla on Monday April 20, 2015 @04:44PM (#9410763)
Are there multiple tech leads per one people manager? I can't imagine someone who can act as a tech lead for a team of 50 engineers and still manage to write code. I have a reservation with tech leads who stop writing code as in my experience they'll stagnate (the time frame is maybe 2,3 years).

A manager manages people mostly by process: a lot of things they look at can be quantified as metrics. So it's alright to have 50 reports (one hour on each a week seems reasonable). A tech lead needs to be able to get to details while still need to have an overview of everything. And then there is the need to keep up with the industry and that means a few hours of paper reading at least every week.

Re:How Google Sold Its Engineers on Management by gramerc on Monday April 20, 2015 @05:03PM (#9410862)
Are there multiple tech leads per one people manager?

Correct. My manager has 4 TLs reporting to him. My TL has a team of 7 not including himself, which is actually on the higher extreme. My previous TL had a team of 4 which is more typical. For career/HR-y management aspects I interact 1:1 with my manager for those, as does my TL. TLs will naturally offer career guidance/mentorship informally by virtue of technical seniority (where applicable) as well as feedback to managers and promo committees that will feed into conversations regarding the technical readiness for promotion for someone on their team.

I have a reservation with tech leads who stop writing code as in my experience they'll stagnate (the time frame is maybe 2,3 years).

TLs at Google stay quite technical (and mine certainly does) and write code as a routine matter of course.

Re:How Google Sold Its Engineers on Management by HeyLaughingBoy on Monday April 20, 2015 @04:56PM (#9410817)
50 reports (one hour on each a week seems reasonable)

What else is that manager expected to do?

Re:How Google Sold Its Engineers on Management by maxxxxx on Thursday April 23, 2015 @05:42PM (#9430070)
How is the pay for manager vs tech lead? In my company managers get paid much better and have more levels to move up to whereas a tech lead typically has maxed out his potential for promotions.
Re:How Google Sold Its Engineers on Management by victorhn on Monday April 20, 2015 @04:08PM (#9410545)
> I also know a number of engineers who never got that sort of technical mentoring, and I watched as their career stagnated.

I think i am currently going on this direction. Assuming i don't have access to such thoughtful companies as yours (my country's sofware industry is underdeveloped), do you know how could i get that kind of technical mentoring needed for my career?

Re:How Google Sold Its Engineers on Management by boomzilla on Monday April 20, 2015 @04:27PM (#9410674)
Do a project of your own. Pick some problem you see around you and solve it to the stage that you deliver the final product. It could be as simple (or complicated) as a website for people to play Sudoku (if that's your thing). You'll learn a lot about software: how to pick the right data structures, how do you persist said data structures, how do you set up user login, how do you draw a 9x9 grid in HTML, etc. There is a lot of details that you can only learn by doing. You'll also train yourself to think as an owner of a problem, rather than a drone who gets told what to do.

Technical wise, if you want to get deep into a sub field (deep learning seems to be the buzzword these days, no pun intended), then pick some open source projects in that domain and try to contribute to it.

Re:How Google Sold Its Engineers on Management by nicolethenerd on Monday April 20, 2015 @04:39PM (#9410743)
There's codebuddies.org, which hosts free study sessions on Google Hangouts for a variety of programming topics.
Re:How Google Sold Its Engineers on Management by steamy on Monday April 20, 2015 @04:05PM (#9410530)
I have seen "democratic" teams spend over two months debating the merits of various solutions that both had about equal, but different, benefits and drawbacks.

Can't just these "democratic" teams solve these problems by a vote measure?

Re:How Google Sold Its Engineers on Management by com2kid on Monday April 20, 2015 @04:50PM (#9410795)
> Can't just these "democratic" teams solve these problems by a vote measure?

That'd be nice, but without some sort of formal decision making process, discussions end up going on forever.

Speaker of the House is a role that exists for a good reason.