Live data from Hacker News

Why I Quit Google to Work for Myself

mtlynch.io

101–110 of 783 posts

Re: Why I Quit Google to Work for Myself

#101
post #87

Earlier quoted context omitted.

If you are going to hand out points for people to vote with, may I suggest quadratic voting.[0] [0] http://ericposner.com/quadratic-voting/

So, would you mind helping me see if I understand quadratic voting correctly? Let's say there are 4 voters: A, B, C, D, voting on policies 1-10. Everyone gets a certain number of votes (say one per policy, so 10 total). Voter A only really cares about policy 5 & 7. So they want to buy votes for these 2. They can give up their votes in, say, policies 1-4 to get 2 more votes for policy 5, and can also give up votes 6,…

I think you just described a typical day in Congress...

Re: Why I Quit Google to Work for Myself

#102
post #29

> I drastically reduced the time developers spent repairing those failures, but there were no metrics that tracked developer time. For several jobs in a row, I've felt that helping others on a team is undervalued and under-recorded. I've been planning to implement the "assist" metric, similar to basketball, on my own team for a while. The idea would be something along the lines of everyone gets a set of assist points…

The first concern I had is that assist points that people assign to other won't be directly comparable -- so an "assist leaderboard" might be misleading and potentially cause more trouble than it's worth.

A point that Dev 1 gives to Dev 2 will not likely be equal to a point that Dev 3 gives to Dev 4.

This will be especially true if everyone has the same quota of assist points to assign, as people may very easily receive different amounts of help, and thus their "actual help per assist points assigned" values will differ.

Re: Why I Quit Google to Work for Myself

#103
> Google does a good job of building a sense of community within the organization.

That is the true test. You are supposed to pretend only to buy into it but never really believe it. Understanding that things function on two levels is critical. One level is the superficial "we are a family, community, we are not evil, making the world better". But that's the trap to catch all the naive people and extract extra work hours from them (possibly at the expense of family or personal time).

There is a second level of unspoken rules - "it really is about business and internal politics". You are supposed to discover and navigate a set of unwritten rules. And these usually don't get spelled out for you, because they are kind of ugly and often diametrically opposed the official rules from the first level.

Slavoj Zizek likes to talk about this when he talks about institutional ideology and how there are rules and meta rules. The meta rules dictate how you relate to the official rules. Which ones you are supposed to break to get ahead, for instance. The other side is that you are given permission to do something but you are not really allowed to take advantage of that or you get in trouble. For example the whole "take any vacation time you want, we don't have fixed days". But you are expected to not really take more than a few or you'll be laid off eventually.

Here is an excerpt where he talk a bit about that: https://www.youtube.com/watch?v=pfO9gL28pAs (warning, he likes to use gross jokes and you might find his style unpalatable)

Re: Why I Quit Google to Work for Myself

#104
Thats not just google mate, every large company is like this. We join thinking that our engineering will make a difference but it does not work like this. If you want to climb the ladder either join high, or grow through a smaller company.

Re: Why I Quit Google to Work for Myself

#105
The article really resonated with me, as it's eerily similar to my own experience at Microsoft a couple of years back. Constant reorgs, resulting in projects being cancelled, resulting in lack of motivation, as months of your hard work are thrown out due to unclear decisions by the management.

I too was hoping for a senior level promotion. The last project I worked on, I was the only non-senior level developer in a team of 5. I went out of my way to ensure we released a well designed, built and tested system on time. At times I felt like I was committing more to the project than any of my more senior comrades. Come release time, I even saw one of the design decisions I had insisted on save us from down-time. All of this I was sure would lead me to the desired promotion.

Come performance review time, I was rated at the top performance tier, as I had the past couple of years. Unfortunately however, I was informed not enough time had passed since my last level increase, but I was sure to get it if I kept it up for another 1-2 years.

It's hard to describe the feeling of defeat I felt at that point. I resigned and left within the next few months. What I found most off putting, was when meeting my skip-manager (your managers manager) for the first time during my exit interview, all doors for a senior level promotion were suddenly open, to incentivise me to stay. Doesn't feel great when negotiations with your employer are comparable to those had with your cable provider.

Re: Why I Quit Google to Work for Myself

#106

Writing documentation and fixing bugs is in fact not the bar for a senior software engineer. I don't disagree with the promotion committee on that front. IIRC, Senior Software Engineer is a terminal level. You aren't expected to advance any more once you reach that level. Some do, but you can stay a Senior Engineer for the rest of your career and that's fine. So certainly "can fix bugs and write docs and tests" isn't…

At many organizations, Senior Engineer is not the end of the IC track, not even close. For example: ... > Senior Engr. > Staff Engr. > Sr. Staff Engr. > Principal Engr. > Sr. Principal Engr. > Distinguished Engr.

Terminal level and Max mean different things here.

Indeed you can become a senior fellow at Google, but you aren't expected to. You are however expected to hit senior at some point in your career. There's no requirement to grow further, so the bar for senior is high.

Re: Why I Quit Google to Work for Myself

#107
A little OT, but I wonder what recruiters / interviewers think of people who took time off to bootstrap their own business but ultimately went back to applying for a regular job. Having the option to go back to working for a big corporation is a good safety net, so it would be an important factor if taking a year off would drastically reduce the likelihood of being hired again.

Re: Why I Quit Google to Work for Myself

#108

Writing documentation and fixing bugs is in fact not the bar for a senior software engineer. I don't disagree with the promotion committee on that front. IIRC, Senior Software Engineer is a terminal level. You aren't expected to advance any more once you reach that level. Some do, but you can stay a Senior Engineer for the rest of your career and that's fine. So certainly "can fix bugs and write docs and tests" isn't…

At many organizations, Senior Engineer is not the end of the IC track, not even close. For example: ... > Senior Engr. > Staff Engr. > Sr. Staff Engr. > Principal Engr. > Sr. Principal Engr. > Distinguished Engr.

"terminal level", in the sense being used by the OP, doesn't mean "end of the IC track". It means a level that you can be at "forever". Often times the junior engineering levels have some expectations around eventually being promoted (ie, "up or out").

Re: Why I Quit Google to Work for Myself

#109
post #2

Author here. Happy to answer any questions about the post or about my experience at Google.

Is your experience common for rank and file Googlers or specific to your role/department? Lots of unrecognized maintenance work, constant project changes, lack of transparency between employees and management. Sounds like an undesirable situation, are these issues that are so widespread there that transferring to another project isn't a likely solution?

[deleted]

Re: Why I Quit Google to Work for Myself

#110
When someone tells me "I'm a software engineer at XYZ", the first thing I ask is - in what team are you in? If your role is to maintain internal web pages or to build random tools for the marketing team then yeah... it doesn't have any meaning. Sure, you still get the benefits of being an employee at XYZ, but it's not super fulfilling. I'd say %30 of developers work on cool things in these companies and the rest of the dev just fill in the blanks. I've worked at a few of the Big-5 and that's what I've observed mostly.

An other thing is - don't get pay by the hour. If you want to maximize your ROI you need to generate passive income there's no other secret. Your day is limited to only a few hours.

Post reply on HN