Tag Archives: My Path to Google

My Path to Google – Juan Angustia, Visual Designer

Welcome to the 43rd 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 Juan Angustia. Read on!



Can you tell us a bit about yourself?
I was born and raised in Constanza, a small town surrounded by beautiful mountains in the Dominican Republic. In the year 2004, before I ever dreamed of joining Google, I went to college at the Universidad Autónoma de Santo Domingo (UASD) to study Advertising with a focus on Graphic Design. However, I did not finish my degree because the school did not offer classes that sparked my specific interests. Instead, I decided to continue teaching myself the things that I loved. 

At that time, a career in UI or UX didn’t exist. You either studied Graphic Design or Advertising, which I was never passionate about. I wanted to work on something that people could interact or play with, something more exciting. This is why I started to design websites. 




During and before I started college, Google was my main source of knowledge. I attribute 80% of the knowledge I obtained to the information I found on Google. Back in the day, I remember walking miles from home to the only computer lab in town. This was the only place where I was able to get internet access. Every day after lunch I took my central processing unit (CPU) and walked to the lab. I connected my CPU and my first thought was to open Google.com to search for tutorials on how to use Photoshop or how to create digital designs.

When I’m not working, I love to dance. It is a form of mediation for me, and also a way to express and share my Latino/Caribbean vibes with others. Sometimes at the office, I dance and work at the same time. I also love to travel and work on personal projects. I take photos and make videos like my short film El Camino. These hobbies to me are a way to find inspiration outside of my day to day work. If you want to know more, feel free to check out my Medium and Instagram: @jcagarcia.


As a Dominican I have music on my blood, it is part of our culture. Merengue and Bachata are some of our typical music. This is a tambora (drum), a popular Dominican instrument.

What’s your role at Google?
I’m a Visual Designer on the Google Duo team in our Seattle/Kirkland office. I’m blessed to be part of this team. The culture, the people, and the vibes are the things that I like the most.. A cool project of mine was recently launched, the new Duo precall interface for the web, which you can check out. You can even submit feedback if you have ideas to help improve the experience for our users.


Duo team event in Playa Vista, Los Angeles. My design for the event is on the screen.

What inspires you to come in every day?
I’ve been working at Google for almost a year, and every day is like living a dream. I feel grateful for the opportunity that I have. Working with very talented people with diverse backgrounds (professional and cultural), and with products that touch billions of people's lives around the world is one of the most exciting things that I could mention. In other words, I work with an incredibly diverse group of people who are some of the smartest, most creative, and humble people I've ever met. I learn something new every time I’m in a meeting.
The team at an offsite event.
Can you tell us about your decision to enter the process? 
The first time that I applied I was rejected for lack of qualifications. Four years later, I was contacted again. I still don’t know how to describe the feeling  when I read the subject line in that email,  “Hello from Google.” It was a mixture of excitement and fear. It was a difficult decision to make, because at that time I had a stable position at my former job in Philadelphia. I also had just bought an apartment a year prior that I absolutely loved. 

Also, I didn’t know if I was ready for the job, or to move cross country and leave my mother behind in Philadelphia whom just three years prior I had brought to the U.S. to fulfill her “American Dream.”


Checking out the Android statue garden.
How did the recruitment process go for you? 
After the first initial call, I was able to move on to the second round of calls, which would be with a designer who would evaluate my experience.The interview process was very friendly and comfortable. Another detail that I noticed from the first moment, was the high attention to detail and how important the recruiter made me feel throughout the process. 

The more nerve-racking but also exciting part was the design exercise, where I was to show my design skills and process. To make a long story short, it took me two weeks to plan, idealize, design, and prepare my project 

Much to my relief, a week after I turned in my design I received a call from the recruiter who was working with me during the interview process. They told me that I had passed the exercise and that I would proceed with an in-person interview at the Google headquarters in Mountain View, California. A shoutout to the excellent attention I received from the recruiter who assisted me throughout this entire process.

The whole interview process took me about three months — months filled with mixed emotions. Finally, after spending months of waiting to complete the entire interview process and contemplating whether I should accept the opportunity to join Google, I decided to accept the position of Visual Designer in Seattle with the Google Duo team.



What do you wish you’d known when you started the process? 
I would have liked to know more about Google’s internal environment and culture, something that I learned after joining  the company and by reading “How Google Works” by Eric Schmidt  & Jonathan Rosenberg. I highly recommend reading this book, this helped me immensely to understand Google’s culture, the company’s history and how people manage their projects and time.


At my Noogler orientation, showing how proud I am to have come from the small town of Constanza, Dominican Republic to Google.
Can you tell us about the resources you used to prepare for your interview or role?
I read a lot about Google Material Design, reached out to friends who work at Google, and also watched videos on YouTube about how to prepare for a Google interviews.


Do you have any tips you’d like to share with aspiring Googlers?
I would recommend that they identify what it is that they are good at and focus on the things that they are passionate about. Never stop dreaming. Continue to pursue your dreams and channel your passion by doing the things you truly love. This is undoubtedly what will help you conquer any opportunity.


Me with a little guitar that I made using a vinegar bottle, piece of wood and fishing lines. (1996).


My Path to Google – Caile Collins, Software Engineer

Welcome to the 36th 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.

This special edition comes out just in time for the annual Grace Hopper Celebration of Women in Computing and features Caile Collins, a software engineer who interviewed for her current job at a previous GHC — and will be returning to #GHC19 this year as a Googler.

Today’s post is all about Software Engineer, Caile Collins. Read on!


Can you tell us a bit about yourself?
I grew up in Buffalo, NY, home to Buffalo wings and Niagara Falls. I entered college as an English major, and I came out with a B.A. in Linguistics with minors in Computer Science and Spanish at Cornell University. When I’m not working, you can find me taking yoga and dance classes, walking dogs, embroidering/weaving/sewing (multi-threaded tasks!), and attending lots of musicals, plays, and comedy shows.

What’s your role at Google?
I am a software engineer working in Google Research on an early-stage project to help language learners achieve their goals. I was really eager to get involved with this project because it ties together my Linguistics background with my role as a product/infrastructure engineer.

I had the chance to join the team from its inception, so it’s been really rewarding to watch it develop, and I’ve been able to be very hands-on and have a lot of impact since it started as such a small team. It’s also been interesting to work together with research engineers, user experience researchers, and product managers to figure out the best path for our project; it’s a very dynamic environment, and everyone contributes different perspectives.

Can you tell us about your decision to enter the process?
I originally wanted to be a speech pathologist; though I was taking more and more Computer Science classes (reaching beyond the requirements for the minor), it didn’t occur to me that I would ever pursue a career in that area. A friend of mine from my Natural Language Processing class encouraged me to come to an on-campus panel of female Google interns that she was going to be participating in (it became my introduction to Cornell’s Women in Computing Club). As I recall, the discussion centered around breaking down impostor syndrome; it clearly drove home the point well enough, because I went back to my dorm and applied to a dozen internships on a whim.

Caile, her team, and Seattle’s Fremont Troll at a team offsite.

How did the recruitment process go for you?
I applied directly for my first internship, and then I interviewed in-person at the end of summer in order to come back for another internship the following year. During that summer, I learned I’d be attending the Grace Hopper Celebration of Women in Computing for the first time in October, and my Google recruiter said that I could do my final full-time interviews there. I was extremely anxious about interviewing so I decided to just jump in headfirst and do as many practice interviews as I could – with full-time engineers before my internship ended, with friends at school, and then with real companies at the career fair at school. It gradually became less scary.

When I finally got to Grace Hopper, I showed up to the interview booth extremely early to make sure I’d know where to find it; I kept circling back there, and the recruiters would give me a friendly wave and chuckle because they knew they’d be seeing a lot of me until my interviews finally happened.

Afterwards, it was really great to be able to relax and join in the celebration of Grace Hopper. I love being in female-driven environments, and having that at such a large scale, especially in my newly selected field of work, was pretty amazing. I particularly remember the keynote speeches were really inspiring; I was excited to hear Susan Wojcicki speak since I had met her that summer while interning on a team at YouTube.

Can you tell us about the resources you used to prepare for your interview or role?
Other than my very generous friends’ time and support, my most reliable resource was Programming Interviews Exposed. I’ve read it front-to-back more times than I can count, and I’ve lent it out to others since then. In my experience, working through problems alone in your head is very different from solving them out loud in front of someone, so it’s important to practice in a real interview-like setting, even if it’s just with your peers.

What do you wish you’d known when you started the process?
I wish I had known that software engineering isn’t all about what specific skills you already know, but largely about how much you’re willing to learn and adapt when tackling new challenges. Moreover, software engineering requires patience and communication to build an end-to-end product that’s meant to last. Those are great skills to have in all aspects of life, and they’ll help you on a microscale - debugging! - and a macroscale - launching!

When not writing code, Caile’s hobbies include other multi-threaded tasks like weaving!

What inspires you to come in every day?
I’ve had a lot of inspiring women in my life, from my mom, sister, and aunts, to my teachers and co-workers. In my career, I’ve been lucky to have met women who have shown me that (1) I can dare to be a software engineer, (2) I can do really well in this field by continuously learning and adapting, and (3) I can find community here.

Once I started at Google full-time, I really want to pass that impact forward. I quickly got involved in intern mentoring. Beyond feeling very lucky to work on a project I’m personally interested in and that contributes positively to the world, I’m grateful for the opportunity to act as a mentor, while continuing to feel supported by those in my own life.

Do you have any tips you’d like to share with aspiring Googlers?
You don’t need to have been coding since you were twelve in order to be a great programmer. If you’re already studying it or working in it now, just think how much you’ve learned since you first started. I didn’t know Computer Science existed as a field until I heard that a friend was studying it in college.
Occasionally I’ll look back at early project notes and remember how little I initially knew about something that I’m now very knowledgeable about and comfortable with. Everybody has to start from somewhere, so just be patient with yourself and know that getting stuck is okay; you can always try again.

The 2019 Grace Hopper Celebration of Women in Computing is underway!




My Path to Google: Goodman Lepota, Associate Account Strategist

Welcome to the 35th 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 Goodman Lepota. Read on!



Can you tell us a bit about yourself?
I am originally from a township in the north of Johannesburg, South Africa. I was fortunate to have spent the past five years living and studying in the United States on an academic scholarship awarded by MasterCard. I hold a Bachelor of Science in Business Administration from Marist College in New York. I am also a graduate of the African Leadership Academy.

When I am not working you can find me reading. I was a publisher of three student newspapers from high school, prep school, to college. I am still fascinated by the different forms of creativity writers employ in their storytelling.
(photo credit: Googler Zach Louw)


What’s your role at Google?
I am an Associate Account Strategist in Dublin, Ireland (Google's Europe, Middle East, and Africa headquarters) working with the Sub Saharan African Google Customer Solutions team.

I often say what we do is like getting a free MBA, because you learn so much from different people. My role includes consulting over 120 clients, focusing on digital growth for their businesses, and advertising. We have an unprecedented scope of successful business models across Africa.

My favorite part about the job is that I get to make an impact and help small and medium sized businesses grow. I work with some of the most exceptional and supportive people everyday. Everyone on our team is invested in making sure everyone else succeeds.

Complete the following: "I [choose one: code/create/design/build] for..." 
I build for a more inclusive and prosperous future.

What inspires you to come in every day?
I am excited about Google’s projects in Africa, particularly focusing on internet access such as Google Station and other internet infrastructure projects. Google is a status equalizer. It gives access to the same level of information for someone living in a rural area with less resources as it does for someone in a cosmopolitan urban area. Google creates opportunity.
 Goodman (center right) with teammates Sashin Pillay (Associate Account Strategist), José Alguem (Google Customer Solutions, Africa lead), and Kristin Ransome, (Associate Account Strategist).
(photo credit: Googler Zach Louw)
How did the recruitment process go for you?
I came across the opportunity on LinkedIn and applied directly on the Google Student Careers website. I had five interviews with Google. Although I was in the process of interviewing for other companies, Google’s hiring process was probably one of the best. Here’s why: they paired me up with a recruiter who facilitated and communicated with me as I prepared for all the interviews. The Googlers who interviewed me also influenced my decision because I felt they were invested in me succeeding during the interviews.

Can you tell us about your decision to enter the process?
I was always interested in business marketing, technology, and policy making. I was excited by the idea of taking on a challenging role after graduating from college, but even more so, I wanted to work for an organization with an amazing team. Google was that place.

What do you wish you’d known when you started the process?
There are some myths about interviewing for Google like asking you tricky and unsolvable questions, which I found to be far from reality.
(photo credit: Googler Zach Louw)

Do you have any tips you’d like to share with aspiring Googlers?
I wanted to share my advice to two kinds of students. The first one is to someone who grew up not imagining they could join Google. I can tell you now that Google will make you feel welcome.

The second one is for the students who are studying in a country that is different from their home country and looking for an amazing opportunity. Google has an exceptional team to support you in relocating in the event that you get accepted.

And I always say this to people — you always have to have that strong conviction that your dreams in life are possible.

My Path to Google: Brian Calbeck, Mechanical Manufacturing Engineer

Welcome to the 33rd 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.

My Path to Google: Brian Calbeck, Mechanical Manufacturing Engineer

Welcome to the 33rd 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.

My Path to Google: Reza Khan, Associate Account Strategist

Welcome to the 32nd 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 Associate Account Strategist, Reza Khan. Read on!


Can you tell us a bit about yourself?
I grew up in the suburbs of Chicago. I went to DePaul University and earned a Bachelor of Science in marketing with a concentration in sales leadership. I developed a love for selling and digital marketing through my internships (SWC Technology Partners and Adobe). When I am not working, I love spending time with my family, playing tennis, and watching Bollywood movies!

What’s your role at Google?
I am an Associate Account Strategist on the Google Customer Solutions (GCS) team. As a trusted advisor to small and medium-sized businesses (SMBs), I help them grow using Google's marketing solutions. I own a book of business of 120 SMBs and my ultimate goal is to help them find success with Google and ultimately grow their business. Working with SMBs brings a very unique opportunity because our clients wear many hats. The person doing the marketing, could be the same person doing the finances and running the operation.

My days often fall into two buckets: cold calling to schedule consultations with my clients, and having those consultations with my clients. I usually come in around 8 a.m. and start to plan out the consultations I will have with my clients that day. From around 9 - 11 a.m. I cold call and email my book of 120 clients to get more client consultations on the calendar. After outreach, I’ll spend the other gaps in my day taking those scheduled consultations with advertisers. It seems trivial to break the job up into two buckets, but those two buckets have helped me grow multiple skill sets. Being able to work at such scale and drive growth across so many businesses has been so rewarding.


Complete the following: "I [choose one: code/create/design/build] for …"
I create robust digital marketing strategies for SMBs.

What inspires you to come in every day?
I am extremely humbled by Google and the people who work at this extraordinary company. It is empowering to work for a company that puts its people first. I feel like I can bring my whole self to work due to the focus and effort that Google puts on diversity and inclusion, and there is truly no better feeling.

Can you tell us about your decision to enter the process?
I was a senior at DePaul University looking for opportunities in sales. I was always in awe of Google and never thought it was something I could reach for. I saw on the Google student careers site that they were hiring for the Account Strategist role in Ann Arbor, and the qualifications matched my experience. I felt that if I could show that I was made for this role, then maybe that would be enough for me to land a job at Google. My confidence in myself and abilities overcame my fear and I applied for my first job at Google.


How did the recruitment process go for you?
I was referred by a friend from college who worked in the role I was applying for. As I eagerly waited to hear back from my first screening interview, I couldn't help but think, "Wow. I just interviewed with Google." I felt that was an accomplishment in itself.

Once I heard back and knew I had a second interview, I couldn’t stop thinking about the Google interview myths like getting asked questions about how many golf balls could fit in an airplane!
Once the interviews were underway, I saw my interviewers just wanted to understand was how well I could think about and solve problems related to the role. Overall, I had a very seamless interview process and was well informed all throughout of what next steps looked like.

What do you wish you’d known when you started the process?
During the interviews, one thing I wish I had known better, was myself. At the end of the day, interviews are just you talking about yourself. If you are self-aware and know what you excel in, what you can improve on, what you’re passionate about, and what you don't enjoy doing — then it becomes pretty easy to talk about yourself and what you bring to the table.

One thing that surprised me about the role was how much responsibility Google gives you from day one. You are given a book of business (managing a lot of clients) and it’s up to you to help them remain successful and grow profitably. Not only this, but my clients are seeking my advisement on how they should run their business. Coming into this role straight out of college, I never thought I would have so much influence and responsibility so early on, and I'm so grateful for that opportunity.


Can you tell us about the resources you used to prepare for your interview or role?
The main resource I used to prepare for the role was the job posting itself. What the hiring manager is looking for is RIGHT THERE in the posting. For example, if they’re looking for someone who can "communicate effectively across various levels, including senior marketing leaders,” then I would make sure I had a story for how I have done exactly that. At the end of the day, take what they are looking for and talk about how you can manifest those specific skills.

Do you have any tips you’d like to share with aspiring Googlers?
Never feel like Google is out of reach — Googlers are regular people. Find a role that you are passionate about, understand what qualifications they’re looking for, and work directly on building those skill sets.

My Path to Google: Jesus Lugo, Windows Systems Administrator

Welcome to the 31st 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 Windows Systems Administrator, Jesus Lugo. Read on!
Can you tell us a bit about yourself?
I was born in Ciudad Ojeda, Venezuela and moved to Miami, Florida when I was ten years old. Shortly after high school, I joined the Marine Corps where I served for 4 years as a Hygiene Equipment Operator. I was very fortunate because once my chain of command learned of my technical abilities, I was allowed to use these skills as an unofficial Information Systems Coordinator. In this capacity I helped manage our computers and networking equipment during my two deployments in support of Operation Iraqi Freedom.
After finishing my active duty service, I attended Miami Dade College, where I received my associate’s degree in Business Administration. After two years of working as an on-site customer engineer, I decided to go back to school for my bachelor’s degree in Information Technology from Florida International University.

I am obsessed with new technology and in particular, hardware. When I am not at work, I spend time looking for ways to integrate new technology into my home. I am generally the first to buy and test new tech.

Whenever I get a chance, I enjoy helping Google at student conferences like those run by Student Veterans of America (SVA), Society of Hispanic Professional Engineers (SHPE), National Society of Black Engineers (NSBE). I talk to students about what it is like to work at Google and how to prepare their resumes and their interviewing skills.
Volunteering at one of the numerous student conferences Jesus helps out at.
What’s your role at Google?
I am currently a Windows Systems Administrator. My team, WinOps, develops, maintains, and supports all the Windows OS related infrastructure for use within Google. We are directly responsible for the configuration and health of all Windows clients and we own the infrastructure and build process for all Windows servers. Within my team, I am part of the configuration management group – specifically tasked with ensuring systems are compliant with internal policy configurations.

What I like most about this role is the continuous evolution. We are always looking for ways to innovate and improve our service offerings. As much as possible we collaborate with other platform teams (Linux and Mac) to build cross-platform tools.

I am currently rewriting a Linux specific tool to work on all other platforms, and integrate a Firebase Cloud Messaging listener to receive notifications from a centralized location. This new software will allow us to manage software distribution and enforcement throughout the fleet, and how tech support teams manage software requests and assist users in getting what they need to get their job done.

Complete the following: "I [choose one: code/create/design/build] for …"
I build to provide a good Windows user experience while maintaining platform security.

What inspires you to come in every day?
I am grateful I get to work with an amazing and supportive team, and the projects I get to work on are always challenging and help me grow both personally and professionally.

I am also very excited about the direction we are headed as Google's cloud business continues to grow. We are constantly looking for opportunities to open source our tools so that other systems administrators can have alternate ways of solving problems we've faced.

In my current project, we are migrating our software distribution tools into solutions that are used across all of our platforms, are largely automated, use code review processes to manage changes, and are more scalable.  This results in releases that are easier to track and maintain, saving us countless engineering hours.
Can you tell us about your decision to enter the process?
During my associate’s degree, I did a project about Google and discovered a lot of information about the culture and many of the perks.

On my last semester at FIU I applied to many companies in South Florida, and even after graduation I had not heard from any of them. As I looked through many different career sites, I decided to see if Google had a job opening that matched my skills. I had applied to many different large companies in Silicon Valley, but I hadn’t heard back from any of them and was sure that Google would be the same way.

Since I was working and attending school full-time, I was unable to take any internships in order to gain real-world experience in IT. However, my job as a Customer Engineer required being knowledgeable in over 20 distinct systems, being capable of troubleshooting issues to root cause, and having great customer service skills.

Two weeks after graduation,  I discovered Google’s Information Technology Residency Program and applied for the job. Even though it was a fixed term position, it was an opportunity to work at Google, and see what it was like from the inside.

How did the recruitment process go for you?
It was a smooth, though long process. I applied directly from the careers site job posting on December 23, 2011, and received the first email from a recruiter on January 3rd, 2012. I had my technical phone screen scheduled on January 7th in the afternoon, and two days later I received a call from the recruiter inviting me for on-site interviews in Mountain View, CA.

My on-site interview date was set two months after the phone screen, which allowed me to brush up on many of the topics I felt I could have done better during the phone screen.

I received the results from the interviews the day before my birthday, and I was so excited when I heard the news from the recruiter, that I accepted without waiting to hear the rest of the offer.

What do you wish you’d known when you started the process?
Recruiters often send or mention topics that may be covered during the technical interviews, focus on those during your studying.

Some available positions may have a time constraint, be sure to work with your recruiter or coordinator to ensure you have ample time to study prior to the technical interviews.
Can you tell us about the resources you used to prepare for your interview or role?
I read "The Google Resume" by Gayle Laakmann McDowell. I found it to be an invaluable resource, and it helped me a great deal.

I read a lot of books on basic IT topics, as the job that I applied for was as an IT generalist. It was tough deciding on what was important, so I focused at the time on having a good understanding of how things worked. I used CBT Nuggets, and other video training tools I could get my hands on. Since I used to drive a lot, I used them like audiobooks and kept track of topics that I needed to view later for additional understanding.

Do you have any tips you’d like to share with aspiring Googlers?
Anything on your resume is fair game, ensure that you can talk at length about anything on it. I personally had listed a number of programming languages on my resume without specifying a level of expertise and was asked to solve a programming problem during my initial interviews, even though the role didn't necessarily require coding skills.

It's best to think out loud, ask clarifying questions, and verify your assumptions with the interviewer, to avoid going too far in the wrong direction in an interview. Do your research about the role you’re applying for, and think of questions you want answered by your interviewers. 

My Path to Google: Ginny Clarke, Leadership Staffing Director

Welcome to the 27th 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 Ginny Clarke. She will be speaking at the 52nd Annual Consortium Orientation Program (OP), taking place June 9-13. See our recent blog post about it here. Read on!



Can you tell us a bit about yourself?
I grew up in Riverside, CA. I wanted to be a veterinarian, but ended up with BA degrees in French and Linguistics from the University of California, Davis. I then went to Northwestern (Kellogg) for my MBA. When I am not working, I like to exercise, cook, write, travel, spend time with my son, Julian, and play with my dog, Mika. I wrote a book called Career Mapping: Charting Your Course in the New World of Work in 2011, and hope to write one or two more books.

What’s your role at Google?
My title is Director, Leadership Staffing. Leadership Staffing is Google's internal executive search firm and I am responsible for driving diversity, internal mobility (helping senior Googlers find new internal roles), and leading a team of 20 non-tech recruiters.

Complete the following: "I [choose one: code/create/design/build] for..."
Create processes that help Google hire the most qualified and diverse senior talent in the world.

What inspires you to come in every day?
I am excited about Google's ability to attract talent it hasn't historically attracted or considered. I am working to institutionalize processes and rubrics that help to identify, attract, and hire this talent to help take our company to new levels around the world.

Can you tell us about your decision to enter the process?
Google called me because of my expertise in executive recruiting, in particular, diversity recruiting. I was watching Google and it's tech competitors grapple with diversity at the senior levels and when called, agreed to take on a new role. Within two months of joining I was asked to develop an internal mobility program for senior execs – which I did. Nine months later, I took on leadership of a team of recruiters – I had three jobs within 18 months of joining!

How did the recruitment process go for you?
The recruitment process was a bit bumpy at first because there wasn't exactly an open role when I was first reached out to. Another tech company started pursuing me, but Google stepped up by introducing me to a couple of very senior execs (our Chief Financial Officer and Chief Human Resources Officer) who convinced me to join.

Can you tell us about the resources you used to prepare for your interview or role?
I consider myself to be an expert interviewee given that I've interviewed thousands of people as a recruiter. I did learn as much as I could about the company and the individuals I was interviewing with, and was able to establish good rapport with everyone. I view interviews as an opportunity for a conversation, not just responding to questions. I had my own questions of the interviewers and was interviewing them as much as they were me.

Do you have any tips you’d like to share with aspiring Googlers?
Be clear about what role you want, why you want it, and what makes you distinctively qualified to do it. This helps you not only in the interview, but once you start in the role – it keeps you clear about what you want to achieve. If you don't get the role, move on and don't take it personally – there are plenty of great companies where you can leverage your skills.

My Path to Google: Frances Johnson, Site Reliability Engineer (SRE)

Welcome to the 26th 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 Frances Johnson. Read on!



Can you tell us a bit about yourself?
I grew up in Adelaide, South Australia, and studied at the University of Adelaide. Originally I enrolled in a bachelor of mechatronic engineering program, but after doing an introductory programming course, I added computer science to make it a double degree.

A year before I graduated I did an internship at Google, and it was amazing. I managed to get a full-time offer, so I moved permanently to Sydney after finishing my degrees.

I like playing Pokémon, Tetris, and board games, as well as watching and reading sci-fi, fantasy, and crime dramas. I also enjoy making things, including chainmail (the metal kind, not the email kind). About a year and a half ago, I took up rock climbing to fill my exercise needs.

What’s your role at Google?
I'm a Site Reliability Engineer (SRE). For the last three years I was on the Geo SRE team, which includes a lot of different services (customer-facing like Maps, Earth, and Streetview, and backends which do things such as calculate directions and maintain all the data we have about the world). Specifically I focused on the servers behind desktop and mobile Maps, and the third-party Maps APIs.

One of my coolest projects I worked on was helping to launch the Lite mode of Maps. I've also gotten to work closely with the SRE team for Google Search and make sure our products and features work well together.

Recently I've joined the Spanner SRE team and am really excited to learn about how global-scale storage systems work.

What inspires you to come in every day?
My coworkers. I'm excited to work with so many amazingly smart, dedicated, interesting, and caring people. It's great to see what we can all solve and create together.

Can you tell us about your decision to enter the process?
I never really thought I'd be able to get a job at Google—I didn't even think I'd get an internship. Some uni friends of mine interned the previous summer and convinced me to apply. My internship happened to be with an SRE team, and it was such a great experience that I asked if I could apply for SRE full-time.

How did the recruitment process go for you?
I applied online for my internship. There was a slight delay in getting my interviews scheduled, but from there, it was mostly smooth. I remember anxiously waiting to hear about my application, but my recruiter had just gotten back from visiting family overseas. She called me right before going home for the weekend, so I wouldn't be left in suspense.

What do you wish you’d known when you started the process?
How you approach problems you don't immediately know how to solve is really important, much more so than remembering details you can just look up later, like syntax. At Google, problems that nobody has seen before happen every day. Oh, and I wish the SRE book existed back then!

Can you tell us about the resources you used to prepare for your interview or role?
Cracking the Coding Interview was a really useful book that I went through. I also did a lot of algorithm study (Algorithms Unplugged, Introduction to Algorithms, and Algorithms and Data Structures: The Basic Toolbox). But probably the most helpful thing was convincing my friends to mock interview me a lot.

Do you have any tips you’d like to share with aspiring Googlers?
Impostor syndrome is extremely real, especially at Google. It's easy to think you'll never make it through the interviews, but don't let it stop you from being confident and doing your best.







*Interested in a Site Reliability Engineer role? Apply now, and learn more at Google's SRE site.

My Path to Google: Alex Grant, Partner Operations Manager for Google my Business


Welcome to the 25th 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 Alex Grant. Read on!



Can you tell us a bit about yourself?
I was in the first Information Engineering cohort at West Point and focused on using cognitive psychology and human-computer interaction to create solutions with technology. After five years in the Army I knew I wanted to work in tech. I started at Google in 2015, and now live in Washington and work in the Kirkland office.

What’s your role at Google?
I’m a Partner Operations Manager for Google My Business, which means I supervise the support we offer to agency customers and contribute ideas for improving the product. The leadership skills I developed in the military are vital in my day-to-day work coordinating teams across two cities.

You recently returned to Savannah to help out at a Grow with Google event. What was that experience like?
Yes, I was stationed in Savannah as a transportation officer for five years during my military service.

Helping the Savannah community through the Grow With Google program was so inspiring and gratifying. It’s a dream opportunity and what I care about most. I was so happy to see the growing community of small business owners that will help introduce Savannah to the rest of the world. Working with veterans was particularly satisfying; I devote some of my personal time to aiding transitioning vets, so I really enjoyed the opportunity to support them with Grow with Google.

It’s often assumed that people looking for jobs have the skills needed to navigate the process. Grow with Google invites people to learn the most important skills, gets them started with resources, and gets them used to engaging with people in tech communities. Every time we have an event, someone who thought that tech wasn’t for them might change their perception of what they can do.

What inspires you to come in every day?
When veterans leave the military, one of the big losses they face is the sense of camaraderie that comes with that community. When I started at Google, I got some of that back. I feel like I’m part of something positive and my coworkers make every day count. They are really the difference between Google and everywhere else. There’s a huge amount of pride that comes from people of this caliber relying on you to lead.

How did you decide to apply?
The truth is that there wasn’t a clear pathway to Google when I left the military. I had offers from conventional companies but didn’t want to work in the energy or defense industries. Military recruitment firms typically try to hire officers into supervisor and manufacturing jobs, so at the time I really had to invent a new path.

At first I worked in fulfillment at Amazon and tried to make my way to headquarters. There wasn’t an opportunity to grow so I transferred to a startup and gave myself a deadline — I would either get a job at Google or move back home and supervise a warehouse. I got in touch with recruiters at Google and was connected to Courtney, who was actively reaching out to veterans. She helped me find the right role to apply to and introduced me to Monica, the recruiter who ultimately offered me my job. It was a long journey for me and now I’m passionate about helping others in my position find their way here.

How did you prepare for your interviews?
I was extremely prepared when I finally went in for interviews. A few steps I took to get ready:

  1. I referenced a lot of job descriptions and did informational interviews to learn what my resume should look like and how my military experience could translate in the civilian world.
  2. I prepped for and attended career conferences to practice interviewing, build confidence, and compare offers. During these conferences, I practiced telling my most powerful stories from my Army service.
  3. I read about Google’s culture and hiring practices in Eric Schmidt’s book, “How Google Works” and another called “I’m Feeling Lucky.” Reading about Google helped me create context with my interviewers and show that I was very familiar with Google’s culture. Today, there is a newer book called “Work Rules” that has great content about hiring.

What’s your advice to others applying to Google?
My greatest dream is that someone who is in the same position I was five years ago will read this and use these resources to find a job. When I was getting ready I looked around for anecdotes but they were hard to find. Here are my tips:

  • After you figure out what job you want, take time to learn about similar and related jobs, including lower-level positions that may feed into that specific role.
  • Promote yourself. In the military we are used to giving credit and celebrating success as a team, but it is critically important for you to share your specific impact on the team’s success.
  • Be data-driven. Show results on your resume or cover letter by using real data to show impact, whenever possible.
  • Network! Use all of the help that you can find in your local or alumni network, both for informational interviews, and referrals where appropriate.






Grow with Google offers free tools, trainings and events to help people grow their skills, careers, and businesses.