But instead, I mistakenly emailed him, concerned that he was holding 1:1s with everyone else on the team except for me. He then hastily called a 1:1, apologized for forgetting my existence, and then immediately informed me that I was now behind on his expectations of my productivity.
My friends advised me to go to HR, so I did. Whereupon I found out he had already paid them a visit to inform them of me. At this point, the google immune system geared up to encourage me to leave of my own volition. I tried to get on to other teams. Friends in the company tried to get me onto their teams. These efforts were blocked.
Deciding this was a game not worth playing further, I left a month later when I got a compelling offer elsewhere.
Waste of 4 months IMO - but I also believe that if I had just been allocated to a more relevant team things would have turned out far better.
At the 3 month meeting, the manager openly admitted that while he managed two teams, he devoted most of his energy to the other one. So in his defense, he was overallocated. His other team was more interesting. But I think he already wanted me gone at that point so that wasn't an option.
My failing was explained to me that since I was a "Senior Engineer(tm)" I was supposed to arrive at google an expert in all their technologies so I could be a successful generalist and finish my starter project (in a brand new unfamiliar field to me) in <2 weeks. Whatever.
In contrast, I reached productivity <48 hours after starting my next gig, which did make use of my skills.
They make up those expectations after the fact, of course. Rather than have the decency to say, "I just don't like you, and don't want you on my team" your manager had to build an objective-looking "performance" case and it sounds like he was a total twat about it.
No one gets anything serious done in the first 2 weeks, and you're not expected to. That's what Codelabs (which are very good, and I wish more companies paid attention to that) are for.
One thing I disliked about the Google environment was that, because it's so hard to have a real accomplishment in your first year, whether you "succeed" depends on others' assessments (i.e. politics). I prefer to be in an environment where, after 3 weeks, I can reach the "so good they can't ignore you" state.
I like high-productivity environments better because I can prove, in the first month, that I'm actually worth a damn. Political issues always exist, but they're less threatening when you've already proven that you're good at what you do.
So they intentionally remove any element of choice in allocation, and throw people into the hopefully representative ensemble of all hiring teams at Google to test how one mixes with the average ideal spherical Googler. But if one ends up 2 sigma to the left of the mean, one is pretty much hosed. And that would likely have a 2-3% false rejection rate assuming this is a normal distribution and that most Google teams are sane. Not bad actually, but sucks for me.
Except that I don't think such a distribution is normal but more likely vastly oversamples the stinkers due to a twisted form of survivor bias because the stinkers have the highest departure rates, putting them constantly on the prowl for new meat oops I mean Nooglers (my small team lost several people during the short time I was on it and several Nooglers switched teams* hours before they would have started to avoid this allocation - I have a really funny photo of several sets of deflated welcome balloons next to what was supposed to be their desk after they had sat around for a couple weeks).
*The most important thing I learned at Google was that I should have secured my allocation before arriving as a condition of accepting employment. Failing that, one can sidestep the process on the first day if one has a friend on a team that is in need of people if one is insistent enough.
This is speaking as a comp eng. student who has gotten very little hands-on hardware experience. I've now worked two years doing pretty much exclusively software; the closest I got to real design was product verification and manufacturing support.
Google is one of the few companies where the 20% is a real thing for most people branch out, on either their own project, or another teams project.
As far as most companies, the side-project with other teams is simply not an option.
Thus, your manager decides if you have 20% time or not.
There are good managers at Google who value 20% time and will encourage you to work cross-hierarchically with other teams or on personal side projects, and there are others who are absentee so you can pull that off furtively. If you get a hard-ass with a lot of project-specific ambition, you're not going to get away with 20% time.
Google inadvertently makes it worse by conflating project leadership with people management, which means that your boss is also held responsible for the performance of a specific project. That creates a huge conflict of interest, because the employee might be a better fit for another project, but the manager has to eat a loss on the project where he is.
There's an escalation path if your manager is outright forbidding you from taking 20% time, and the manager can be disciplined by the Powers That Be for that.
Google also doesn't always conflate project leadership with people management (it depends on the team, and the org chart is explicitly setup so that this is not a given). There're pros and cons to both: if you're on a project where your manager is the tech lead, he'll know your work better (which can help you get promoted faster), but it also means that if you disagree with him on the technical direction of the project it can be harmful to your career. Out of my 4-year Google career, I've spent 2.5 years on teams where my manager was directly involved in the project, and 1.5 years basically doing my own thing or on loan to other teams with minimal involvement from my manager. I don't have a clear preference for one or the other, as I've found that my manager was always supportive of me as a person even when his primary responsibility was managing the project, and willing to let me move to another team when I'd outgrown his area of interest.
(It probably helped that I would work like hell to help my manager's project succeed first, and then transfer off once it launched. Most people are more inclined to help you succeed if you help them succeed.)
Seems what Valve does instead puts credibility on the open market. This makes sense, as that one term, credibility, actually encapsulates a complex panoply of things, and markets are good at regulation even when faced with complexity.
American corporatism is based on Original Sin (the so-called "Puritan work ethic"). If you're not "saved" by some rich institution (a job) then you're judged to be a leech and a failure. Most companies take advantage of this by continuing it into Credibility Scarcity-- you're worthless until told otherwise.
I've worked for "startups" that don't do this. You start out as an "idiot." The manager has to look over your shoulder every 30 minutes, and gets worried because you are programming using "blocks." You're dictated to in terms of which libraries you use. All this total micromanagement, yet the manager knows so little about iPhone development, he has no idea what "delegates" are or that they're the most common pattern in the SDK.
What you're discussing is the Credibility Drought. Companies define credibility so that only managers have it, in order to create an artificial scarcity that makes employees easier to control. That's what enables the managerial extortion that forces employees to serve local goals (the manager's own career) rather than the benefit of the company (or the growth of the individual).
Very few companies formally allow a manager to unilaterally fire. That's way too much of an HR/lawsuit risk. Instead, these closed-allocation dinosaur companies define credibility in such a limited way that managers can either support or not support the employee, and then if the person is not supported, that person's credibility is zero and the manager isn't firing that person. "The company" does it, after "careful review" of "objective" performance statistics. On top of this, they set tight headcount limits so that for anyone to get a good project requires a special favor, allowing the company to say "no" and appear consistent on the matter.
Google is aware enough of this problem to allow engineers at above a certain level to acquire independent credibility.
At Staff, you can pull a Yegge (quit your project in public) and be OK. If you're a SWE 3 and you try that, you're fucked.
So Google may be different from the full-on closed-allocation nightmare corporation, but you only if you either (a) start at a senior level, or (b) get on visible, desirable projects when you start, so you can get promotions quickly. The only time it isn't difficult to transfer to something better is immediately after a promotion (and there are some managers who withhold promotions to keep people captive; Google, to its credit, has a system that occasionally overrides managerial objections to promo).
The sad thing is that I don't doubt that Google is better than 95 percent of large corporations its size in terms of internal mobility, individual autonomy, and engineer-centric culture. It might be better than 98%. It's still pretty awful for a large percentage of people who work there, and the fact that it's so much better than most of what else is out there is a damnation of Corporate America, not an endorsement of Google.