> My friend who had next to no experience got a job at Google as a contractor through a 3rd party company. He gets very solid pay and access to all of Google's lux facilities/food and he didn't even have to do a technical interview. I think they do this because if you suck they can basically fire you anytime.
Yup. Not a lot of people know this, but a significant percentage of people at Google are contractors (red badges). One of my friends is currently working there as a contracted web developer. He said that while working there is awesome, the turnover in the contractor ranks is very high and there is not a lot of support for newbies. It is pretty much a sink-or-swim environment. Outside of "codelabs", there isn't much documentation of their internal tools so my friend has to constantly read the source code to figure out how to use something.
But there isn't really a "trick" here, though. The point of these questions is to figure out if the candidate has enough CS fundamentals to construct a reasonable solution to a problem that they've never seen before.
I've been in an open workspace that had three or four people to a desk and it was a nightmare. Now I work at an open workspace where everyone is spread out and it is much better. The closest person to me is ~2 meters away.
"How I quit my job and went into consulting"
"How I quit consulting and went into freelancing"
"How I quit consulting and went into your mom's vagina"
"How I quit my consulting job for a month and learned to program and am now making 80k a year writing Ruby apps"
"How I quit my contractor Ruby dev gig and joined the Node.js behemoth (and why you should too)"
Stupid? You were the one who said that most interviews should only be a one-way street. That you will only let yourself get asked the questions in the article if the job applicant is a top-talent AND your company specifically wanted to recruit that person.
If I remember correctly, you also quoted the question "What's the coolest thing you've built here, personally?" and your response was "Who's getting interviewed here?".
You should've let your posts be. Own up to what you wrote.
Wow, talk about a mono-culture. I just checked some of their photos and it seems they are male-dominated, 90% white, 10% oriental-asian with an average age of 25.
Sure, I understand that the company was just trying to make money and keep the jobs of 50+ people. But that doesn't change the fact that the company wasted my time and made my experience miserable.
Yeah, the first three difficulties were really easy. Inferno was like a wall that you run into the first time you try it. I remember kicking Diablo's ass in Hell difficulty and then replaying Act 1 but in Inferno. Came across the first zombie in New Tristram and promptly died in two hits.
yup, that was the main point of frustration with Inferno.
white mobs were easy to deal with but Elite packs had disgusting affixes.
And then after grinding Act 1 (remember Butcher runs? lol) for about a month, you finally gear up enough to be able to easily kill Act 1 Elite packs.
Then you get to Act 2 and find yourself getting one-shotted by those stupid wasps (and we're not talking about Elite variety, these were just the regular wasps).
Yup. Not a lot of people know this, but a significant percentage of people at Google are contractors (red badges). One of my friends is currently working there as a contracted web developer. He said that while working there is awesome, the turnover in the contractor ranks is very high and there is not a lot of support for newbies. It is pretty much a sink-or-swim environment. Outside of "codelabs", there isn't much documentation of their internal tools so my friend has to constantly read the source code to figure out how to use something.