Tag Archives: Life at Google

Behind the scenes of our first Women of Color Summit

Over the past year, Google has continued to search for new ways to build a culture of belonging virtually. To continue this important work, last week, we hosted our first-ever Women of Color virtual summit. The event brought together thousands of Googlers, representing women of color from every corner of the world and across every part of the company. 

I sat down over Google Meet with April Alvarez, Google’s Head of Women, Latinx and Indigenous Communities and Programs, to learn more about the event, her work and how Google is making space to uplift women of color around the world.

First, can you tell us about what you do at Google?

I’m the Global Head of Women, Latinx and Indigenous Communities on our employee engagement team. My team is dedicated to building a better workplace for all of us. This means listening to our employees and ensuring that they have a voice, as well as providing support to our internal communities by making sure they have access to the resources they need. It also means helping to provide a space for these groups to connect via company-wide events like this one.

So why did you host a global summit?

In the past, we have hosted summits for distinct communities across the organization, such as the State of Black Women and Latinas at Google Summit. This year, after hearing feedback from our employees, we widened our lens to include all women of color across the company in a single gathering to share their experiences, address the unique opportunities and challenges they face and support their personal and professional enrichment. 


Around the world, we continue to reckon with structural and systemic racism. As long-term solutions are developed, we wanted to give light to and honor all of the amazing and talented women of color across the company. Our theme was Transcend, and the day centered around transcending global boundaries, celebrating each other, empathizing with shared challenges we face and giving space to our own stories of triumph and perseverance.

Tell us about the highlights.

The event included a powerful fireside chat with former first lady Michelle Obama and our Chief Diversity Officer, Melonie Parker. In the hour-long session, the two women covered a host of topics, including mentorship, vulnerability and how their childhood experiences shaped them. 

Reflecting on the stories and experiences women of color carry, Mrs. Obama said, "The only way people will know us, and our complexities, is if we share our stories.” In addition to the fireside chat, the virtual gathering featured 25 speakers from inside and outside Google who talked about their own experiences transcending boundaries. Another highlight for me was seeing the incredible feedback we’ve received from the attendees. One attendee said that it was the most inspiring and connection-driven program she ever experienced at Google.

What does this event mean to you?

For me personally, as someone who identifies as a Latina, a Chicana, Latinx, Mexican-American and as a woman of color, I know that when we come together like this, our voices become louder, and together we go further. After this past year, I’ve personally been craving connection with my fellow colleagues, and so for me personally, I was extremely thankful to have the space to be together in sisterhood.

What advice do you have for women of color?

Prioritize community and connection. Right now, so many of us are isolated, going through our work days alone and working from home and others are being pulled in multiple directions, trying to juggle work and family. Take the time to get to know others and create space to really listen and share experiences.


The (digital) road from competitive programming to Google SRE

Welcome to the latest edition of “My Path to Google,” where we talk to Googlers, interns and alumni about 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 Mohamed Yosri Ahmed, a Site Reliability Engineer at our Munich office. Yosri’s passion for coding competitions led him to Google -- and now he supports young programmers as a mentor in Google’s own series of coding competitions!

So first off, what is “competitive programming” and what are the competitions like?

In competitive programming, participants put their skills to the test as they work their way through a series of algorithmic puzzles. Competitions are timed, and oftentimes you’re working together with a group of teammates in order to solve difficult puzzles together. Competitive programming is really fun and challenges those who practice it to grow technically and personally.

 How did you first get involved with competitive programming?

 I was born and raised in Cairo, Egypt. I got my computer science bachelor’s degree from Ain Shams University, which is also when my journey with competitive programming (CP) began. Since then I’ve developed a passion for problem solving and finding solutions to complex challenges and riddles.

Yosri at the International Olympiad of Informatics 2019 in Baku, Azerbaijan. Yosri looks over an arena where participants in yellow and orange shirts sit at tables and work at laptops.

Yosri at the International Olympiad of Informatics 2019 in Baku, Azerbaijan.

What’s your role at Google?

 I am a Site Reliability Engineer at the Production Productivity Engineering team. We focus on helping Google rapidly launch reliable services through applying best practices. We get to engage with many teams working in many different areas; this is challenging yet super exciting.

I also help run the Google's Coding Competitions such as Code Jam and Kick Start.

What inspires you to log in every day?

At Google there are always new learning opportunities and the possibilities to grow are endless. Google really cares about its employees’ growth and happiness at work.

Also the impact of my team’s work and the products we build, that affects so many people's lives in many ways, makes me feel grateful and inspired to do more.

How did the recruitment process go for you?

After graduating from college, I got contacted by a Google recruiter following my performance in Code Jam that year. Relocation at that point was not easy for me so we had to stop the process. A couple of months later, I got contacted again by another Google recruiter to explore opportunities. By then, things were clear for me and we decided to move forward and start the interview process. I actually flew from the International Collegiate Programming Contest World Finals in Portugal to do my onsite interviews in France.

How did you join the Site Reliability Engineering team at Google?

After passing the interviews, I proceeded to the next step: software engineer team matching. My recruiter also asked me about my interest in Site Reliability Engineering (SRE) which I didn’t know much about at the time. A Googler SRE friend suggested I check out one of the free online books Google SREs wrote to share their best practices.

Yosri and three other new Googlers stand in front of a Google sign.

Yosri and three other new Googlers at Noogler Orientation in Zürich.

How did coding competitions prepare you for SRE at Google?

Competitive programming can help participants develop lots of skills that are useful for SRE, like dealing with ambiguity and being able to troubleshoot abstract ideas without necessarily being the expert. 

CP trains us to focus on targets and how to achieve them. The short time limits teaches us to appreciate every moment and to efficiently utilize the resources we have.

Another aspect of similarity is troubleshooting and testing at scale. Both are key skills and responsibilities for SRE in order to be confident about a system and to know why it may or may not work. With tight time constraints to solve different problems and penalties on wrong attempts, CPers develop their testing and troubleshooting skills.

Both CP communities and SRE thrive on communication and collaboration. SREs have huge diversity in their responsibilities and how they approach them. Cross team collaboration during incidents for a common mitigation goal is similar to a CP style where 3 teammates are trying to solve the same problem on a single PC. In this style, coordination of efforts is essential. 

In CP, team members may have different strengths in different algorithmic and data structures topics and they join their skills to solve more complex problems. Along the way, we learn to make use of our different skill sets in order to succeed together. 

Any other tips you’d like to share with aspiring Googlers?

The path to success is not unique. These paths may cross but they may never be the same for everyone. We should identify our skills and put them into practice to sharpen them. We should always keep on learning and aiming for a better future. 

The (digital) road from competitive programming to Google SRE

Welcome to the latest edition of “My Path to Google,” where we talk to Googlers, interns and alumni about 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 Mohamed Yosri Ahmed, a Site Reliability Engineer at our Munich office. Yosri’s passion for coding competitions led him to Google -- and now he supports young programmers as a mentor in Google’s own series of coding competitions!

So first off, what is “competitive programming” and what are the competitions like?

In competitive programming, participants put their skills to the test as they work their way through a series of algorithmic puzzles. Competitions are timed, and oftentimes you’re working together with a group of teammates in order to solve difficult puzzles together. Competitive programming is really fun and challenges those who practice it to grow technically and personally.

 How did you first get involved with competitive programming?

 I was born and raised in Cairo, Egypt. I got my computer science bachelor’s degree from Ain Shams University, which is also when my journey with competitive programming (CP) began. Since then I’ve developed a passion for problem solving and finding solutions to complex challenges and riddles.

Yosri at the International Olympiad of Informatics 2019 in Baku, Azerbaijan. Yosri looks over an arena where participants in yellow and orange shirts sit at tables and work at laptops.

Yosri at the International Olympiad of Informatics 2019 in Baku, Azerbaijan.

What’s your role at Google?

 I am a Site Reliability Engineer at the Production Productivity Engineering team. We focus on helping Google rapidly launch reliable services through applying best practices. We get to engage with many teams working in many different areas; this is challenging yet super exciting.

I also help run the Google's Coding Competitions such as Code Jam and Kick Start.

What inspires you to log in every day?

At Google there are always new learning opportunities and the possibilities to grow are endless. Google really cares about its employees’ growth and happiness at work.

Also the impact of my team’s work and the products we build, that affects so many people's lives in many ways, makes me feel grateful and inspired to do more.

How did the recruitment process go for you?

After graduating from college, I got contacted by a Google recruiter following my performance in Code Jam that year. Relocation at that point was not easy for me so we had to stop the process. A couple of months later, I got contacted again by another Google recruiter to explore opportunities. By then, things were clear for me and we decided to move forward and start the interview process. I actually flew from the International Collegiate Programming Contest World Finals in Portugal to do my onsite interviews in France.

How did you join the Site Reliability Engineering team at Google?

After passing the interviews, I proceeded to the next step: software engineer team matching. My recruiter also asked me about my interest in Site Reliability Engineering (SRE) which I didn’t know much about at the time. A Googler SRE friend suggested I check out one of the free online books Google SREs wrote to share their best practices.

Yosri and three other new Googlers stand in front of a Google sign.

Yosri and three other new Googlers at Noogler Orientation in Zürich.

How did coding competitions prepare you for SRE at Google?

Competitive programming can help participants develop lots of skills that are useful for SRE, like dealing with ambiguity and being able to troubleshoot abstract ideas without necessarily being the expert. 

CP trains us to focus on targets and how to achieve them. The short time limits teaches us to appreciate every moment and to efficiently utilize the resources we have.

Another aspect of similarity is troubleshooting and testing at scale. Both are key skills and responsibilities for SRE in order to be confident about a system and to know why it may or may not work. With tight time constraints to solve different problems and penalties on wrong attempts, CPers develop their testing and troubleshooting skills.

Both CP communities and SRE thrive on communication and collaboration. SREs have huge diversity in their responsibilities and how they approach them. Cross team collaboration during incidents for a common mitigation goal is similar to a CP style where 3 teammates are trying to solve the same problem on a single PC. In this style, coordination of efforts is essential. 

In CP, team members may have different strengths in different algorithmic and data structures topics and they join their skills to solve more complex problems. Along the way, we learn to make use of our different skill sets in order to succeed together. 

Any other tips you’d like to share with aspiring Googlers?

The path to success is not unique. These paths may cross but they may never be the same for everyone. We should identify our skills and put them into practice to sharpen them. We should always keep on learning and aiming for a better future. 

Google Taiwan turns 15 with a new engineering hub

As a Taiwanese and an engineer, it's extremely heartwarming to see how Taiwan has grown to be a critical hub for global innovation and hardware manufacturing. Not everyone knows that Taiwan has contributed to the development of many Google products, including Pixel phones, Nest devices, Chromebooks, and Chromecast. 

We first opened our Taipei 101 office in 2006 with just one employee. Today, we have offices across six cities in Taiwan, and our workforce has grown ten times in the last five years. We plan to keep the momentum going in order to build helpful products for Taiwan and the world. 

Today, on Google’s 15th anniversary in Taiwan, and the third anniversary of bringing in the HTC family (including myself!), I’d like to share the five things I’m excited about as we look to the future of Google in Taiwan. 

1. New spaces for our teams to innovate in:We first shared our plans to build a new engineering hub in New Taipei City, an emerging hub for innovation, in 2019. Today, we’re opening the new campus, with its very own hardware engineering facility—the first and biggest outside the U.S. This facility will enable our teams to collaborate, brainstorm and experiment with hardware prototypes. The space will also be used to develop our hardware products including Next devices, Pixel phones, Chromecast and more. 

2. Continued growth and expansion:We are already working towards our next milestone, where we plan to open another building in the same compound in 2023 to accommodate our future growth. We look forward to sharing more about these plans down the road. 


3. Recruiting the next generation of tech talent:We will provide more opportunities for students interested in a career in tech by offering new internship roles in manufacturing engineering, Google Cloud and Technical Program Management. This is in addition to our current offerings in software and hardware engineering, data centers, sales and business operations and marketing. Interested candidates can find out more through our careers site, or join us at one of our virtual recruitment visits that we’re holding at 50 universities throughout the year.

4. Building a more diverse workforce:We care deeply about making Google a workplace that's inclusive and diverse. In 2019, we launched our Google Taiwan Student Associate program, the first pilot program in the region to provide opportunities for students with disabilities to develop skills and on-the-job experience. We plan to extend this program and increase the number of Google scholarships offered this year. 

5. Offering free technical courses for Taiwanese talent:We plan to introduce free online development courses related to Hardware, Software and Cloud, so potential candidates and interested individuals can gain practical skills and prepare themselves when interviewing for technical roles.

I’m energized about our long-term growth plans here in Taiwan. Together with our expanding teams, we look forward to building more helpful and innovative products for Taiwan and the world. 

An Army veteran’s journey to Google: 5 lessons learned

I've always been interested in technology and how it can connect people to the world. I still remember when I turned on my first computer as a kid and it felt like my entire world had opened up. So when I was getting out of the US Army in 2013, Google’s mission was particularly appealing to me. But as a transitioning military officer, Google and the tech industry felt like completely different worlds from the one I knew as a soldier. 

Turns out my time as a platoon leader and transportation officer in the Army had prepared me to eventually become a product support manager at Google. The Army taught me how to quickly observe and develop processes, and both of those skills helped me quickly ramp up in my role at Google. 

Here are five lessons I learned from my transition from the Army to Google. I also shared my experience in a video Q&A with Google’s Veteran Career Series, which is a great resource for any troop, veteran or military spouse interested in joining Google or exploring a career in technology. 

Veterans have skills that are attractive to tech companies.

My veteran background is a direct contributor to my success here. Veterans bring experience in critical competencies, such as project management, teamwork and leadership. My experience in the Army coordinating with units and allies taught me a lot about effective communication and lateral leadership, both which are essential in my daily work. 

Networking and research are important to transition from military to tech.

The one thing I would’ve changed about my original job search when leaving the military is doing more informational interviews and networking. Use your personal network and resources, like LinkedIn or VetinTech, to connect with tech employees and research companies. This will help you refine the narrative in your resume, learn the lingo and culture of the tech industry and form relationships that will benefit you in the future.

Seek more credentials and certifications, but it’s ultimately about you.

Your passion, critical thinking skills and demonstrated impact will nearly always outweigh your certifications. Many of the jobs at Google rely on the same essential skills. Before you sign up for a technical course or certification, make sure you do the work to understand your interests, skills and aspirations. Once you know your personal brand, you can decide how your technical skills match up with your ideal role. Consider preparing a functional resume if it helps you bring out the skills as listed in the job description.

Service and purpose continue at Google.

Google has employee groups and networks, such as the VetNet, which includes Googlers from all backgrounds and regions. These groups allow us to connect and work together on things we’re passionate about, whether discussing how Army Football is better than Navy or coaching veteran job candidates. Having that shared purpose creates a culture of comradery. It may not feel exactly like the military bond, but it’s familiar to anyone with a service background.

Success at Google means navigating ambiguity.

At Google problems we face have endless options for resolution. Successful Googlers know how to operate in a space will little direction, take calculated risks and learn quickly from their mistakes. This type of environment doesn't appeal to everyone, especially if you're used to an organization with standard procedures and traditions. If you’re interested in a role in tech, reflect on this to make sure it's a role you can approach with passion.

Looking for advice on transitioning from the military to a role in tech? The five-part Career Series is now available to watch online. You’ll learn how veterans are a great match for tech companies, especially Google.

An Army veteran’s journey to Google: 5 lessons learned

I've always been interested in technology and how it can connect people to the world. I still remember when I turned on my first computer as a kid and it felt like my entire world had opened up. So when I was getting out of the US Army in 2013, Google’s mission was particularly appealing to me. But as a transitioning military officer, Google and the tech industry felt like completely different worlds from the one I knew as a soldier. 

Turns out my time as a platoon leader and transportation officer in the Army had prepared me to eventually become a product support manager at Google. The Army taught me how to quickly observe and develop processes, and both of those skills helped me quickly ramp up in my role at Google. 

Here are five lessons I learned from my transition from the Army to Google. I also shared my experience in a video Q&A with Google’s Veteran Career Series, which is a great resource for any troop, veteran or military spouse interested in joining Google or exploring a career in technology. 

Veterans have skills that are attractive to tech companies.

My veteran background is a direct contributor to my success here. Veterans bring experience in critical competencies, such as project management, teamwork and leadership. My experience in the Army coordinating with units and allies taught me a lot about effective communication and lateral leadership, both which are essential in my daily work. 

Networking and research are important to transition from military to tech.

The one thing I would’ve changed about my original job search when leaving the military is doing more informational interviews and networking. Use your personal network and resources, like LinkedIn or VetinTech, to connect with tech employees and research companies. This will help you refine the narrative in your resume, learn the lingo and culture of the tech industry and form relationships that will benefit you in the future.

Seek more credentials and certifications, but it’s ultimately about you.

Your passion, critical thinking skills and demonstrated impact will nearly always outweigh your certifications. Many of the jobs at Google rely on the same essential skills. Before you sign up for a technical course or certification, make sure you do the work to understand your interests, skills and aspirations. Once you know your personal brand, you can decide how your technical skills match up with your ideal role. Consider preparing a functional resume if it helps you bring out the skills as listed in the job description.

Service and purpose continue at Google.

Google has employee groups and networks, such as the VetNet, which includes Googlers from all backgrounds and regions. These groups allow us to connect and work together on things we’re passionate about, whether discussing how Army Football is better than Navy or coaching veteran job candidates. Having that shared purpose creates a culture of comradery. It may not feel exactly like the military bond, but it’s familiar to anyone with a service background.

Success at Google means navigating ambiguity.

At Google problems we face have endless options for resolution. Successful Googlers know how to operate in a space will little direction, take calculated risks and learn quickly from their mistakes. This type of environment doesn't appeal to everyone, especially if you're used to an organization with standard procedures and traditions. If you’re interested in a role in tech, reflect on this to make sure it's a role you can approach with passion.

Looking for advice on transitioning from the military to a role in tech? The five-part Career Series is now available to watch online. You’ll learn how veterans are a great match for tech companies, especially Google.

How Emily Garcia found her dream job in consumer hardware

Welcome to the latest edition of “My Path to Google,” where we talk to Googlers, interns and alumni about 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 Emily Garcia, head of Supply and Demand Management for our Pixel products. Emily shares her experience finding her dream role in Consumer Hardware at Google — a role she didn’t know existed until she applied. 

What’s your role at Google?

I am the head of Supply and Demand Management for our Pixel  products in the Devices and Services Business where I manage an amazing team of global planners. Our job can be super challenging—constantly flexing between dynamic market changes and supply chain obstacles. But there’s nothing more exciting than seeing your product “on shelf.” It’s truly a dream job for me.

What steps did you take that led you to the hardware field?

I grew up in Lima, Peru as the youngest child of three girls. Growing up, I had no clue what I wanted to do, but tech and telecommunications has always been super exciting to me. In college,  I decided to get a degree in Industrial Engineering because I thought it would give me the most options when I started looking for a career.

I moved to the U.S. at 18 to get my Bachelors degree at the University of Michigan — which is where I also experienced what a real winter is like. I was very fortunate to find an amazing support structure in Michigan; I joined student groups such as SHPE (Society of Hispanic Professional Engineers) and SWE (Society of Women Engineers) which gave me access to industry leaders, recruiters, career fairs and student resources. This helped me find internships (six of them!), secure a GEM Fellowship and get my Masters degree entirely funded.

Emily sitting outside with her dog.

Emily and her dog, Milu, working from home.

What inspires you to come in (or log on) every day? 

Working within Devices and Services at Google is an incredible experience. We have tons of opportunities to improve the supply chain, get creative on how to best serve our customers and get to support very innovative products. Coming to work (or logging on) knowing that there will be a new challenge every day is super rewarding. And being surrounded by such ambitious, creative and kind people creates the perfect environment to thrive.


What was the application and interview process like? 

Visiting the Google campus for my onsite interviews was a really enjoyable experience for me—all the interviews felt really comfortable. I gained perspective from every interviewer and I didn’t feel the nervousness or stress that I usually feel at interviews.


By the time offer discussions came in, I was doing a month-long volunteer project in a rather rural part of South Africa. My recruiter and future manager held late night phone calls with me over a spotty phone connection to discuss details and help plan my move.


What's one thing you wish you could go back and tell yourself before applying?

I was super grateful that I was warned in advance how lengthy the process could be, so I took everything in stride. I didn’t have any expectations and was just grateful to continue going through the process.

Emily standing next to a large Android statue with a Noogler hat.

Emily at her 'Noogler' orientation.

What resources did you use to prepare for your interview or role?

Before interviewing, I consulted with current and former Google employees to really understand the culture, values and their experience. I read a lot! Mostly online, reading about how the company positions itself and the various things Google is involved in. 


Preparing for my role was an entirely different process—I was stepping into a role I had done before but with a very different set of circumstances. Here, I met with peers and stakeholders, understanding the current challenges, capabilities and opportunities. I even revisited some of my old textbooks to refresh my core knowledge of this work. 


Do you have any tips you’d like to share with aspiring Googlers?

Your experience, your background and point of view are priceless. Be yourself, ask tons of questions and don’t give up.

Changing the narrative around mental health at work

It can be debilitatingly lonely to live with a mental health disorder. I began my mental health journey in 2013, when I was diagnosed with depression in my final year of college. Soon after, I began publicly writing about my experience. I found that sharing about my mental health helped me and others in so many ways, especially in places where there is still a lot of stigma. People would message me and say, “Thank you, I thought I was the only one going through this.” I’ve been a mental health advocate ever since. Building a sense of shared experience and normalizing these conversations is so important. 

I was reminded of the value of open communication when I first joined Google in Singapore in early 2019. I am currently diagnosed with bipolar disorder and complex post-traumatic stress disorder (cPTSD). Because of my PTSD, situations like one-on-one meetings in enclosed spaces could be panic-inducing. Thankfully, I trusted my manager enough to share this, and she was incredibly supportive. She suggested meeting at our open cafes or taking calls from home, and she shared about mental health resources available at Google. Her compassion, understanding and guidance meant a lot and helped me find my way.  

Through her recommendation, I also became an active member of Blue Dot at Google, our global peer support network that aims to destigmatize mental health conversations. In Singapore, we organize programs like mental health conferences and Blue Dot booths to raise awareness of these issues. I also spoke on an internal panel called “You Can’t Ask That,” aimed at addressing potentially sensitive questions around stigma and mental health. These programs create spaces for community, learning and compassionate listening. 

I’ve learned people just want to have a safe space where they can put down their armor and be vulnerable—yes, even in the workplace. Organizations of all sizes need to place a stronger emphasis on employees’ mental wellbeing, especially during tough times, like the COVID-19 pandemic.

After working at Google for almost two years, seeing how the company approaches mental health has been reaffirming—from employee resource groups and assistance programs that offer confidential counselling to company-wide days off to make sure people aren’t burnt out. I am heartened that we also often see leaders speaking openly about their mental health, encouraging an open, supportive and inclusive work culture. 

Being able to share my experience, and listen to how others are going through their journey has helped me feel less alone and find meaning. Whether in the workplace or outside, I want to tell those who may be struggling in silence: You’re never alone. Help is available, don’t be afraid to ask for it. You’ve got this! 


How one engineer went from startups to Google

Welcome to the latest edition of “My Path to Google,” where we talk to Googlers, interns and alumni about 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 Avital Zipori, a software engineer at our Tel Aviv office. Always lured by the startup world, she first turned down an offer from Google. After filling her startup fix, she now brings the skills she learned at small companies to Google. 

What’s your role at Google?

I'm a senior software engineer and tech lead for Google Research. My team focuses on building engaging, conversational experiences. A cool new feature we recently released is aimed at teaching children more about animals. Try it yourself by saying “Animal of the Day” to Google Assistant.

How did you first get interested in technology?

I grew up in Netanya, Israel. I got my first taste of programming in high school and then again in my analyst role in the army, and couldn't get enough of it. It’s what eventually led me to study Computer Science at the Hebrew University of Jerusalem. 

I'm a co-founder of Extend, an organization focused on opening the tech industry to diverse engineers, and a co-founder of Baot, Israel’s largest community of senior female software engineers.

What made you decide to apply to Google?

Actually, I never thought I would work at Google. I knew it was considered the best place to work but that it was extremely difficult to get in, so it didn't even cross my mind that it would be an option. 

I’d been working at a mid-sized startup since I was a student, and after a few years I decided it was time to look for my next challenge. I had my mind set on joining a new startup. When a Google recruiter reached out to me, I decided to interview for the practice. I figured that there was no chance I would pass, but I expected the interviews would be hard and would prepare me well for other interviews.

Avital speaking next to a podium with a Google logo and a slide with a penguin on it.

Avital gives a talk at the Google Research conference.

What inspires you to come in (or log on) every day?

Above all, it's the amazing people I get to work with! I also love having the power to create something out of absolutely nothing, and think of creative ways to solve challenging problems with significant impact.

How did the application and interview process go for you?

I was so certain I would not pass that I had already chosen a job at a new startup to join when I got the news that I had been accepted to Google.  

This left me with a difficult decision to make: On the one hand it sounded crazy to say no to Google, but on the other hand I was really excited about the startup. I wanted the experience of a small, new startup at some point in my career, and it seemed to make more sense to do it at that stage of my life when I didn't have other time-consuming obligations. 

I decided to join the startup and I had a great time and learned a lot. But as with most startups we eventually ran out of money. The Google recruiter kept in touch with me during this time, so I contacted him and continued the process where we left off. 

What's one thing you wish you could go back and tell yourself before applying?

I didn't know how much freedom engineers at Google had to manage themselves and choose what they work on. 

I also didn't know how simple it was to switch teams, even if you are switching between completely different engineering specialties—like from front-end development to low-level networking). This is incredible because it allows you to keep learning new things and work on a variety of products and technologies.

Avital speaking into a microphone while sitting with other Googlers.

Avital speaking at a panel during a Google recruiting event.

Can you tell us about the resources you used to prepare for your interview or role?

I mostly studied using the book "Cracking the Coding Interview". Nowadays I recommend also using coding websites that test your solutions and doing mock interviews with friends.

Do you have any tips you’d like to share with aspiring Googlers?

My advice for everyone is don’t be afraid of failure and forgive yourself if you do fail. This is generally important in life, but also specifically relevant for starting a process with Google. 

I meet people who are afraid to enter the process and I attempt to convince them that they have nothing to lose. Even if you don’t get the job, it will be a better outcome than not trying at all. So if you are afraid to start a process—please do it anyway!

Dre’ Davis went from college to Google’s data center team

Welcome to the latest edition of “My Path to Google,” where we talk to Googlers, interns and alumni about how they got to Google, what their roles are like and even some tips on how to prepare for interviews.

Today’s story is all about Dre’ Davis and his journey from not quite knowing what he wanted to do with his new mechanical engineering degree to joining Google’s data center team in Loudoun County, Virginia and being part of a new data center site from the ground up.

What’s your role at Google?

I’m currently a facilities technician on the Data Center Infrastructure Operations team. We maintain our data center infrastructure, keeping services like G Suite and YouTube up and running. 

The one thing I love about my role is something that is, by my knowledge, very consistent across Google: the people. My job requires collaboration with the people around me. My job can be challenging at times, but when the people are caring, compassionate and intelligent, it makes your job that much easier.

Red, white and blue airplane-themed Google logo sign at a Google data center.

A Google logo sign at a Google data center.

Can you tell us a bit about yourself?

I grew up in a small town in Virginia called Appomattox. Our town is famously known for being the place where the American Civil War ended. After graduating from high school, I ventured off to Old Dominion University. There I got my bachelors in mechanical engineering technology with a minor in electrical engineering technology. 

The STEM field wasn't an area I would have pictured myself in. None of my family had experience in the industry, I had never worked in it prior to getting to school and it seemed so beyond my reach. On top of all of this, I was also a first-generation college student. It was my goal to be the first and to lead the pack.

Why did you decide to apply to Google?

I was only months away from graduation, and still had no clue what I really wanted to do, so when a Google recruiter reached out on LinkedIn, the timing was impeccable. I had no clue as to whether it would work out or not, but I was willing to put myself out there to see. 

What inspires you to come in every day?

I was able to join the team just as our sites were hitting the ground, so to see the growth of these data centers has been amazing. Virginia has the largest concentration of data centers in the world and I am excited to see how we continue to innovate to stand out among data centers in my home state.

Hard hat with Google logo.

Google-themed safety gear.

How did the application and interview process go for you?

I had several phone interviews with experienced technicians. I was still very new to this technical world and had little experience at this point, so I was a nervous wreck on every call. I was afraid that the person on the other end would hear a quaking kid rather than a student looking to get a foot in the door. 

However, with every call, I got a glimmer of hope when I heard the words, "Congrats, here are the next steps!" This process lasted a couple of months until I was finally presented with my offer and my inner panic finally subsided. 

What's one thing you wish you could go back and tell yourself before applying?

The recruiters are on your side. We sometimes have the perception that the person standing between us and the opportunity wants to hinder us from getting there. Google does truly look for the best candidates, but they also are looking to help you as best they can. 

What  resources did you use to prepare for your interview?

"How We Hire" on Google Careers is a great asset. It gave me so many tips that allowed me to be successful throughout the entire process, from applying to interviewing. Your recruiter will also be a great tool for you. From the time my recruiter messaged me on LinkedIn, they were top notch and made sure that all my needs were met and all questions were answered in a timely manner. 

Do you have any tips you’d like to share with aspiring Googlers?

Sometimes the only thing standing between you and success is fear. Be willing to step out and be courageous. Courage doesn't mean you're not scared; it means you're terrified, but willing to take it on anyway.