DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Interviewing with Google? Read this!

Alex Ruiz user avatar by
Alex Ruiz
·
Nov. 26, 12 · Interview
Like (0)
Save
Tweet
Share
15.06K Views

Join the DZone community and get the full member experience.

Join For Free

In response to my post, “My team at Google is hiring,” I got a lot more résumés than I expected. This is absolutely great! Many thanks to all the folks interested in working in my team!

While chatting with a few of the potential candidates, I offered some advice on interviewing with Google. This is advice that was passed to me when I interviewed a couple of years ago. Even though these tips are nothing out of ordinary, they are, however, practical and useful. Since I found myself repeating them over an over, I thought it may be a good idea to write them down.

Here we go.

1. Listen to your best friend: the (Google) recruiter

Is the recruiter’s job to get you an offer from Google. He or she will do everything in their control to help you. As part of their job, they will tell you what you need to study for the interview. It is a lot of material, but it is absolutely worth the effort. Needless to say, Google is awesome.

2. You decide when to interview

It is your decision when to interview. Take all the time you need to prepare and don’t let anybody push you. Knowing when you are ready is difficult though. Studying all the material is pretty much impossible. Instead, you need to set a realistic goal. In my case, since I was terrified by the interview process, my goal was to cover the basic algorithms and data structures, and study until I feel calm and confident.

3. Practice, practice, practice…and get a whiteboard

It does not matter if your solution is wonderful, you are in trouble if the interviewer cannot understand it. While preparing for the interview, solve problems on a whiteboard. Learn how to express your ideas and write code (yes, write code on a whiteboard) in a clear, neat and organized way. You want interviewers to understand your solutions.

4. Let all your friends at Google know that you are interviewing

The more Googlers that can say something good about you, the better. You may be able to skip the phone interview (it is not a promise though.) I personally hate technical phone interviews.

5. $hit can happen

Preparing for the interview does not guarantee you will pass it. There are many factors that can work either in your favor or against you. Plus, there is no such a thing as a perfect interview process. $hit out of your control can happen. Don’t feel too bad if, for whatever reason, you fail the interview. It happens more often than you think. Seriously. Just learn from the experience and apply again in six months. Like I mentioned earlier, working for Google is worth the effort.

That’s pretty much it. Good luck! :)

Google (verb)

Published at DZone with permission of Alex Ruiz, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Bye-Bye, Regular Dev [Comic]
  • Agile Transformation With ChatGPT or McBoston?
  • Mind Map Reuse in Software Groups
  • Utilize OpenAI API to Extract Information From PDF Files

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: