2,808 karma · joined November 13, 2008
I run a game company developing http://fracturedveil.com and help governments, film/tv productions and companies worldwide on issues related to technology, open source and manufacturing.
We talked about how we should break the news that we supported git. Marking the bug fixed was a good approach to it as then we knew those that cared enough to click on the little star on the issue would know, and that would be a pretty good start.
A few people noticed in the 1/2 hour or so between the launch and the issue change, so that was funny to watch. We'll do a formal post later. Right now we're mostly watching and seeing what happens so we can make sure the site is in good shape.
So....try it out and let us know how you like it.
http://code.google.com/p/support/issues/detail?id=2454
Or to the project creation page:
http://code.google.com/hosting/createProject
We hope you like it.
1) Phone screens: If you aren't referred or we don't really get a good feel from your resume what kind of developer you are, there are preliminary phones screens which can seem...insulting to experienced programmers. Then you get a phone screen with an engineer.
2) On-sites: These are often with people who are -not- on the team you may be joining. We try to avoid team interviews for a number of reasons. But you are likely to talk with 1 or 2 people from a future team .
3) In engineering interviews, you shouldn't see stupid manhole questions. You should see 'how would you do' questions, preferably ones that allow you to talk about how it should be solved, write on the whiteboard code that would solve it, and then what kind of optimizations you would apply to the problem, etc... Through this discussion we can see what kind of developer you are. This should ideally be a discussion among peers about how to approach a programming/Google relevant/computer science problem.
4) Get a reference. Want the best kind? Write open source code that gets used and point it out in your cv/res. That'll lead to Googlers who you can use to put your resume in the system (the best way to go, trust me) A reference that has familiarity with your code and a subsequent link to that code in your cv is gold if you are a decent programmer. I've see people who interview really poorly be saved by their code submissions.
Happy to answer other questions.
They might have, but this story isn't that conclusive.
We released this all some time ago under apache 2.
The shunting of those who want to blog/surf to the balconies was pretty nice for those who don't want the typey typey glowing screen distraction.
Mind you, I've only been to the one ted (2010) so maybe I'm not the big authority here, but I found 'A' people approachable and friendly and I'd say it was pretty great.
Chris (disclaimer: googler)
"Similarly, when the device is in free-fall and therefore dangerously accelerating towards to ground at 9.81 m/s^2, its accelerometer reads a magnitude of 0 m/s^2."
http://developer.android.com/reference/android/hardware/Sens...
Google gets resumes and random text from 1000s of people a day looking for a job, all over the world, completely bereft of any sort of qualification. That's the vast majority of resumes any large business like Google will see. It's like Spam writ large.
So we have resume screeners who look at those random resumes and try to separate wheat from chaff. For some, we have a phone screen that is literally to check the most basic of facts to see if the resume is at all consistent with the name at the top, then a real phone screen with an engineer, then an onsite, then offer.
Each step loses people, but the first, separating the clear bs from the real is where the huge gap comes from.
That said, I hope we have more false negatives than false positives every step of the way, and for that, all I can say is that I wish it didn't have to be that way. Well, that, and this: Get referred by a Googler, skip many of the above steps :-)
Here's previous edge question compilations:
What Is Your Dangerous Idea: http://amzn.to/fTgjYk
And others: http://amzn.to/fkoFdv
(yes, affiliate links) I have essys in two of them. :-)
1) They have principles. I know the GC personally and he is a very principled guy. So are ev and biz.
2) Having principles isn't counter to the ability to recognize gains. In fact, the idealist in me hopes and has seen how they are intimately connected.
Also, remember that if you start giving into every request like this without a fight, they'll end up looking like a patsy. They fight and they know that they'll be taken seriously by law enforcement and by their users. I'm glad twitter did this.
So grades matter, but not forever...