Friday, December 27, 2019

Interview Googleyness



https://www.paysa.com/blog/5-questions-to-study-for-your-google-interview/
They want to see you have “Googleyness”: a combination of work ethic, creative thinking and appetite for learning that shows you have what it takes to thrive in the fast-paced, highly analytical environment at Google

https://www.fastcompany.com/40458298/6-ex-googlers-share-how-they-landed-the-job
Googleyness is a reflection of your personality and has a number of elements, Miller says. “How easy are you to get along with? With the Google recruiting process, one question that you have to pass is every person who interviews you is asked, Would you want to work with this person every single day? Would you be happy if you sat next to this person every single day? Would you be able to do good work, and would you enjoy their company?” he says.
Look out for the phrase “Tell me a time when…” during your interview, Miller says. Interviewers use this phrase to ask questions like “‘Tell me a time when you overcame adversity’ to get you to talk about subject matters. For example, if you worked in marketing previously and talked about how you failed to get organic traffic to the website, they would ask about what you did when your boss came down on you.”

https://www.businessinsider.com/what-google-looks-for-in-employees-2015-4

Google want people with high "cognitive ability."

"If you hire someone who is bright, and curious, and can learn, they're more likely to come up with a new solution that the world hasn't seen before," Bock explained in a Google+ Q&A. "This looking for cognitive ability stems from wanting people who are going to reinvent the way their jobs are going to work rather than somebody who's going to come in and do what everybody else does. We recruit for aptitude, for the ability to learn new things and incorporate them." 

Labels

Review (572) System Design (334) System Design - Review (198) Java (189) Coding (75) Interview-System Design (65) Interview (63) Book Notes (59) Coding - Review (59) to-do (45) Linux (43) Knowledge (39) Interview-Java (35) Knowledge - Review (32) Database (31) Design Patterns (31) Big Data (29) Product Architecture (28) MultiThread (27) Soft Skills (27) Concurrency (26) Cracking Code Interview (26) Miscs (25) Distributed (24) OOD Design (24) Google (23) Career (22) Interview - Review (21) Java - Code (21) Operating System (21) Interview Q&A (20) System Design - Practice (20) Tips (19) Algorithm (17) Company - Facebook (17) Security (17) How to Ace Interview (16) Brain Teaser (14) Linux - Shell (14) Redis (14) Testing (14) Tools (14) Code Quality (13) Search (13) Spark (13) Spring (13) Company - LinkedIn (12) How to (12) Interview-Database (12) Interview-Operating System (12) Solr (12) Architecture Principles (11) Resource (10) Amazon (9) Cache (9) Git (9) Interview - MultiThread (9) Scalability (9) Trouble Shooting (9) Web Dev (9) Architecture Model (8) Better Programmer (8) Cassandra (8) Company - Uber (8) Java67 (8) Math (8) OO Design principles (8) SOLID (8) Design (7) Interview Corner (7) JVM (7) Java Basics (7) Kafka (7) Mac (7) Machine Learning (7) NoSQL (7) C++ (6) Chrome (6) File System (6) Highscalability (6) How to Better (6) Network (6) Restful (6) CareerCup (5) Code Review (5) Hash (5) How to Interview (5) JDK Source Code (5) JavaScript (5) Leetcode (5) Must Known (5) Python (5)

Popular Posts