Skip to main content

Do You Have What It takes to be a Googler?

If you're trying to get hired at Google, don't bother bragging about your GPA or marks.
Laszlo Bock, Google's senior vice president of people operations, told the New York Times that the company looks far beyond grades (Google is actually hiring more and more people that never went to college). 
What does it take to impress a Googler and rather be one?
Bock says that the number one thing that the company looks for is not I.Q. but learning ability. Candidates need to be able to process things "on the fly" and draw conclusions from seemingly unconnected info. They also need to be "emergent" leaders. Google isn't necessarily looking for the president of the chess club. It's looking for people who know when to lead and when to follow. 
" What’s critical to be an effective leader in this environment is you have to be willing to relinquish power," he says. 
Humility and ownership are two other big pieces of the puzzle. Bock wants Google employees to feel a sense of responsibility and ownership that will make them step in and try to solve any problem. But they also need the humility to embrace the better ideas of others. There needs to be the right mix of confidence and adaptability.  
"They’ll argue like hell. They’ll be zealots about their point of view. But then you say, ‘here’s a new fact,’ and they’ll go, ‘Oh, well, that changes things; you’re right,’” Bock says. "You need a big ego and small ego in the same person at the same time."
Finally, Bock says that Google doesn't care about expertise. Experts will respond to problems with the same solutions they've seen work a million times. A "nonexpert" will mess up occasionally, but usually they'll come up with the same answer. And once in a while they'll come up with something that is completely new. That's how innovation happens. 

Comments

Popular posts from this blog

Testing React loader with React Testing Library

 I have came across this situation so many times where I need to write a unit test for a component pattern I have developed so many times that I can write the code with my eyes closed. BUT what about unit testing! That's something my mind thought is the best candidate to get rid of in order to store more cat memes. Even when these patterns are used almost everywhere and we write the tests for each one of them (I hope you do) but still we (it can't be just me) tend to forget them and get even more confused with those pesky `act` warnings. So I decided to curate a recipe book for some common unit tests which I come across and might be useful for future me. Happy to share the github repo and also would love to see if anyone has more such common unit testing patterns which they can add or suggest. https://github.com/Charchit26/react-testing-library-recipes Now, let's talk about the one I have coded a dozen times and still take half an hour to struggle with its unit tests - Load

Send Anonymous Mails!

Ever thought of a mischievous act like sending a mail with  a fake identity or using someone else's identity?? Sure, if you have that naughty prankster hidden in you! So there are ACTUALLY two common sites which may help you in such pranks.. They are... 1: http://www.sendanonymousemail.net/ Its got a pretty easy and user-friendly interface which makes it so special.. 2:   https://emkei.cz/ It can be considered as the advanced version for sending fake mails.. Its got a good variety of options for "geeks" as well as an html editor for cutomizing the mails! But Do Remember that  these tools would let you   send anonymous emails   free of cost   and let you be  hidden   at the same time, but they Do store your IP addresses, just in case your anonymous email indulges in illegal activities! So, Do NOT even try to send scary threats or spam like messages because you may get caught very easily and can be charged with fraudulent charges and can be pu

Re-usability vs Readability

Recently while developing some features for a client's React app I faced this dilemma: What to prefer over another - Readability or Re-usability. My first reaction to it was what any other great developer in the history of web applications would have done - "Google it out". I found some good articles and blogs around it but still I had my doubts, since at many such places the examples used were heavily dependent on the individual's situation. So, my next move was to consult a peer or another dev from the community whom I trust, and who is better to trust then random people on twitter! I would admit that I did not expect some of those answers but it really taught me one most important thing in software development - "Everything is situational". In other words, I was introduced to "anti-patterns" in real life! Good read for the difference between patterns and anti-patterns . <*Insert a funny gif related to anti-patterns here(if you find one