My Path to Google: Brian Calbeck, Mechanical Manufacturing Engineer
Welcome to the latest installment of our blog series “My Path to Google.” These are real stories from Googlers, interns, and alumni highlighting how they got to Google, what their roles are like, and even some tips on how to prepare for interviews.
Today’s post is all about Mechanical Manufacturing Engineer, Brian Calbeck. Read on!
Can you tell us a bit about yourself?
I’m from the Bay Area and grew up in Walnut Creek, CA. I received both my Mechanical Engineering undergraduate degree and a Masters in Engineering from California Polytechnic State University (Cal Poly). I interned at Apple during grad school and joined Google upon graduating. I enjoy road and mountain cycling, traveling, and spending time with my wife and two daughters.
What’s your role at Google?
I’m a Mechanical Manufacturing Engineer working on Google’s Data Center Infrastructure. My team figures out how and where to build the hardware that runs Google’s software. I love the challenge of working on cutting edge technology at a scale that you can’t find anywhere else. I’m currently working on building tensor processing unit (TPU) hardware to power our machine learning technology.
Complete the following: "I [choose one: code/create/design/build] for..."
I help build the hardware that runs Google.
What inspires you to come in every day?
I’m inspired by the scale and complexity of the work we do. It’s rare to work on products that will touch billions of people. I remember the first time I saw a demo of Google Photos and was amazed by the app’s ability to understand the content of my photos. Machine Learning is enabling amazing advancements in almost every industry and I love that I get to be at the forefront of that.
Can you tell us about your decision to enter the process?
I was really excited to apply to Google. I had always admired Google’s culture, but I never thought I would find a role as a Mechanical Engineer until I ran across the posting for my current role. I was skeptical that I’d get an interview since I was a new college grad and the role called for someone with more experience, but my dad encouraged me to take a chance so I applied.
What do you wish you’d known when you started the process?
It’s easy to get frustrated with a hiring process when you don’t see everything that’s going on behind the scenes, but know that if you’re being considered for a role you’ve already made it past the hardest part. My recruiter did a great job of talking me through the process and helped me provide an honest and accurate picture of what I could bring to the job.
Can you tell us about the resources you used to prepare for your interview or role?
I prepared by reviewing the details of some technical projects I spearheaded in college and put together a portfolio with visual aides. I wanted to make sure I could clearly recall the details of the projects I worked on and communicate them to my interviewers. Interviewers at Google want to know how you think through multi-faceted problems, so having examples fresh in your mind will help when communicating your skills.
Do you have any tips you’d like to share with aspiring Googlers?
Be honest about your experience, skills, and passions and be sure to communicate how these could strengthen your prospective team. When you’re early on in your college career, look for unique jobs and experiences that interest you and relate to your course of study. Your first internship probably won’t be your dream one. I spent two summers working in a machine shop. I started out sweeping the floors but worked my way up to running the machines. That job not only gave me great hands-on experience but helped me stand out when I went to apply for opportunities later on in my college career.
