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.

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.

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!

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.

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.

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.

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 Patrick Schilling, a Strategic Deal Manager on the Google Cloud team. In addition to helping big companies use Google technology to get ready for the future, Patrick uses what he’s learned through his experience breaking barriers to advocate for people with disabilities and create a more inclusive society.

What’s your role at Google?

I’m a Strategic Deal Manager on the Google Cloud team. I help our sales and professional services teams manage the largest strategic partnerships that Google Cloud enters with customers in Europe and the Middle East. What´s particularly inspiring about my job is to see our clients, some of whom are the largest, most traditional enterprises in the world, embark on their digital transformations.

How did you begin advocating on behalf of people with disabilities?

I was born and raised in the city of Tuttlingen in Southern Germany. Since birth, I have lived with a physical disability (shortened arms and legs), which posed a variety of challenges to my family in my early years and teens. Overcoming these challenges, continuously growing as a person and sharing my experiences to empower others has become one of the key motivators of my life. 

I became the first person in my family to ever attend university. Along the way, my family and I broke through a variety of challenges and hurdles, such as being the first person with a disability to ever attend my German high school. I experienced both severe societal injustice and an extraordinary commitment aimed at remedying it. After high school, I involved myself in local and state politics in Germany. I founded several organizations that lobbied on behalf of people with disabilities. In that function, I started doing speaking engagements focused on how political and technological progress can create an ever more inclusive society.

What led you to apply to Google?

I pursued a double degree in international management and business administration, which allowed me to study for two years at ESB Business School in Germany, and two years at NC State University. During that time I interned in Germany and the U.S., primarily  for technology and tech consulting companies. It was during one of those internships that I met people from Google. Their drive to challenge the status quo, their desire to not take no as an answer and their commitment to a diverse, equitable and inclusive society inspired me to apply.

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

Seeing how the world´s largest organizations transform and get fit for the digital age is breathtaking. So is seeing how excited our clients get about the seemingly endless capabilities that groundbreaking technologies such as artificial intelligence and machine learning offer to grow their businesses and better serve their customers.

How did the application and interview process go for you?

The recruitment process was both challenging and inspiring at the same time. I was still on the U.S. West Coast at the time, interviewing for a position in Europe. While my recruiters did their best to accommodate for the time zone differences, it still meant waking up at 6 a.m., hastily downing 3 shots of espresso and then getting into interview mode. 

Throughout all my interviews, the people I met reassured me that this is the company I would love to work for. Google has a policy in place that allows you to self-disclose any special needs you may have due to a disability. When I self-disclosed, both the recruiter and the hiring manager made absolutely sure to provide me with all accommodations needed to set me up for success. 

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

The most important thing is to familiarize yourself with the resources available on Google´s career site. This will help you get ready for your role and set you up for success. In addition, I would encourage all applicants to reach out and speak to current Googlers. We are here to help you get ready and it is our pleasure to share our experiences.  

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

Be yourself and bring all of it to your interviews! This is a place where it doesn't matter who you are, or where you come from or what you look like. You can make it here at Google, if you are willing to try.

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 Patrick Schilling, a Strategic Deal Manager on the Google Cloud team. In addition to helping big companies use Google technology to get ready for the future, Patrick uses what he’s learned through his experience breaking barriers to advocate for people with disabilities and create a more inclusive society.

What’s your role at Google?

I’m a Strategic Deal Manager on the Google Cloud team. I help our sales and professional services teams manage the largest strategic partnerships that Google Cloud enters with customers in Europe and the Middle East. What´s particularly inspiring about my job is to see our clients, some of whom are the largest, most traditional enterprises in the world, embark on their digital transformations.

How did you begin advocating on behalf of people with disabilities?

I was born and raised in the city of Tuttlingen in Southern Germany. Since birth, I have lived with a physical disability (shortened arms and legs), which posed a variety of challenges to my family in my early years and teens. Overcoming these challenges, continuously growing as a person and sharing my experiences to empower others has become one of the key motivators of my life. 

I became the first person in my family to ever attend university. Along the way, my family and I broke through a variety of challenges and hurdles, such as being the first person with a disability to ever attend my German high school. I experienced both severe societal injustice and an extraordinary commitment aimed at remedying it. After high school, I involved myself in local and state politics in Germany. I founded several organizations that lobbied on behalf of people with disabilities. In that function, I started doing speaking engagements focused on how political and technological progress can create an ever more inclusive society.

What led you to apply to Google?

I pursued a double degree in international management and business administration, which allowed me to study for two years at ESB Business School in Germany, and two years at NC State University. During that time I interned in Germany and the U.S., primarily  for technology and tech consulting companies. It was during one of those internships that I met people from Google. Their drive to challenge the status quo, their desire to not take no as an answer and their commitment to a diverse, equitable and inclusive society inspired me to apply.

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

Seeing how the world´s largest organizations transform and get fit for the digital age is breathtaking. So is seeing how excited our clients get about the seemingly endless capabilities that groundbreaking technologies such as artificial intelligence and machine learning offer to grow their businesses and better serve their customers.

How did the application and interview process go for you?

The recruitment process was both challenging and inspiring at the same time. I was still on the U.S. West Coast at the time, interviewing for a position in Europe. While my recruiters did their best to accommodate for the time zone differences, it still meant waking up at 6 a.m., hastily downing 3 shots of espresso and then getting into interview mode. 

Throughout all my interviews, the people I met reassured me that this is the company I would love to work for. Google has a policy in place that allows you to self-disclose any special needs you may have due to a disability. When I self-disclosed, both the recruiter and the hiring manager made absolutely sure to provide me with all accommodations needed to set me up for success. 

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

The most important thing is to familiarize yourself with the resources available on Google´s career site. This will help you get ready for your role and set you up for success. In addition, I would encourage all applicants to reach out and speak to current Googlers. We are here to help you get ready and it is our pleasure to share our experiences.  

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

Be yourself and bring all of it to your interviews! This is a place where it doesn't matter who you are, or where you come from or what you look like. You can make it here at Google, if you are willing to try.

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 Priyanka Vergadia, who followed her curiosity and stumbled upon a role that combines her technical and artistic skills: creating technical learning content for Google Cloud developers as a Developer Advocate.

What’s the best thing about being a Developer Advocate at Google? 

This role challenges me with new technologies every day and allows me to think creatively about learning novel concepts and explaining them to a wide range of people. I get to interact with the developer community and create content that can help them learn about Google Cloud. I create tutorials for the Google Cloud Youtube channel, write blogs, codelabs and sample code and speak at conferences. 

Currently I’m working on the concept of visual learning. I created the GCP Sketchnotes series, in which I explain the Google Cloud tools in the form of a sketch. The idea is to be able to print the sketchnote or use it as a desktop or phone wallpaper to learn quickly. You can check them out at the cloudgirl.dev.

What first sparked your interest in technology? 

I am from Indore, a city in central India. My parents are my role models: My dad is an engineer and his work inspired me to be an engineer, and my mom is an artist and her creativity and confidence continues to inspire me in everything I do.  

I studied electronics and telecommunication with a bit of programming during my undergraduate course work. Due to my growing interest in coding, I decided to pursue a masters from University of Pennsylvania in computers and information science. After graduating, I had my eye on becoming a software engineer. 

What eventually led you to becoming a Developer Advocate?

My first job was as a quality engineer, which allowed me to explore the industry a bit more. Customer engineering caught my eye. I took a risk and decided to change course, working with customers and applying my technical skills to solving real business problems. 

That was a turning point for me because I had stumbled on something that I really loved. I was able to combine my creative skills to create compelling presentations, demos and code samples that would help developers learn specific products better. That love of solving problems with technology led me to exploring the Developer Advocate role, and I am absolutely loving it!

What was it like to apply to Google?

I applied right after school and did not make it past the phone interview. After that experience I had imposter syndrome. Then about 4.5 years later a recruiter from Google reached out to me. I was not really looking for a new job at the time. But I went into the process with an open mind because I found that this time the role was right for me and the skills I had acquired over the years aligned perfectly to the position. After the first phone interview my hopes started to grow because I really liked the role. 

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

I wish I knew that Google is not just looking for coding gurus. The search is for people who can think analytically and solve problems. The interview questions are more focused on getting to know your thought process and how you get to a solution. Knowing this would have made me worry much less. 

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

I am inspired by the people I get to collaborate with and the impact I get to make by working on products that touch millions of lives.

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 Priyanka Vergadia, who followed her curiosity and stumbled upon a role that combines her technical and artistic skills: creating technical learning content for Google Cloud developers as a Developer Advocate.

What’s the best thing about being a Developer Advocate at Google? 

This role challenges me with new technologies every day and allows me to think creatively about learning novel concepts and explaining them to a wide range of people. I get to interact with the developer community and create content that can help them learn about Google Cloud. I create tutorials for the Google Cloud Youtube channel, write blogs, codelabs and sample code and speak at conferences. 

Currently I’m working on the concept of visual learning. I created the GCP Sketchnotes series, in which I explain the Google Cloud tools in the form of a sketch. The idea is to be able to print the sketchnote or use it as a desktop or phone wallpaper to learn quickly. You can check them out at the cloudgirl.dev.

What first sparked your interest in technology? 

I am from Indore, a city in central India. My parents are my role models: My dad is an engineer and his work inspired me to be an engineer, and my mom is an artist and her creativity and confidence continues to inspire me in everything I do.  

I studied electronics and telecommunication with a bit of programming during my undergraduate course work. Due to my growing interest in coding, I decided to pursue a masters from University of Pennsylvania in computers and information science. After graduating, I had my eye on becoming a software engineer. 

What eventually led you to becoming a Developer Advocate?

My first job was as a quality engineer, which allowed me to explore the industry a bit more. Customer engineering caught my eye. I took a risk and decided to change course, working with customers and applying my technical skills to solving real business problems. 

That was a turning point for me because I had stumbled on something that I really loved. I was able to combine my creative skills to create compelling presentations, demos and code samples that would help developers learn specific products better. That love of solving problems with technology led me to exploring the Developer Advocate role, and I am absolutely loving it!

What was it like to apply to Google?

I applied right after school and did not make it past the phone interview. After that experience I had imposter syndrome. Then about 4.5 years later a recruiter from Google reached out to me. I was not really looking for a new job at the time. But I went into the process with an open mind because I found that this time the role was right for me and the skills I had acquired over the years aligned perfectly to the position. After the first phone interview my hopes started to grow because I really liked the role. 

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

I wish I knew that Google is not just looking for coding gurus. The search is for people who can think analytically and solve problems. The interview questions are more focused on getting to know your thought process and how you get to a solution. Knowing this would have made me worry much less. 

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

I am inspired by the people I get to collaborate with and the impact I get to make by working on products that touch millions of lives.

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 Tony Rodriguez, a Technical Solutions Engineer in Austin who started at Google in our Cloud Technical Residency (CTR), a one-year rotational program for recent college graduates. (If you’re interested in applying, the CTR program is now accepting applications for 2021.)

Can you tell us more about your roles at Google?

As of July 2020, I am officially now a Technical Solutions Engineer (TSE) in Google Cloud. Prior to becoming a TSE, I was a part of the Cloud Technical Residency Program, a rotational program aimed to provide students who have recently graduated with both technical and client facing skills. The program is 12 months long, with three months of training and rotations in three separate Google Cloud organizations.

Throughout each rotation I increased my technical knowledge of Google Cloud products. First, as a Technical Account Manager I managed relationships and major projects for Google Cloud Platform (GCP) customers, then, as a Strategic Cloud Engineer I helped architect/build solutions for customers, and finally, as a Technical Solutions Engineer, I supported our products and worked with product teams on improving them.

Coming straight out of college and not being certain of what I wanted to do, this program was incredible. I got to explore three amazing roles and get a taste of what the day to day looked like for each. The fact that I went through it with a cohort of 25 amazing individuals, also helped make it a smooth transition out of college. 

Have you always been interested in tech?

I was born in San Luis Potosi, Mexico but grew up in the Atlanta area. Growing up, I always had a passion for technology and knew I wanted to pursue something in the tech field. I thank my parents for teaching me that hard work and determination pays off but also for being understanding everytime I broke the computer! I’m the first person in my family to graduate from college; I studied computer science at the University of Georgia. (Go Dawgs!)

You applied to Google twice. Can you tell us about that experience?

The idea of applying to Google was initially scary, because I feared rejection. I got denied the first time when I applied for a software engineering internship my junior year of college, but I received helpful constructive feedback and worked hard that year towards preparing for a second shot if given the opportunity. 

I applied again a year later for a software engineering role and at the beginning of the process, I told my recruiter that the past year had opened my eyes. I learned there are more positions in tech than just software engineering. Because of that conversation, I was informed about a new program that Google had started the past year and how it was a great opportunity for new college graduates to explore other roles available in tech. 

I decided to give it a go and from that point forward I was in the process for applying to become a CTR. The process overall was super smooth and consisted of both technical interviews and interviews focused on non-technical skills like problem solving, project management and leadership.

I’ll never forget the day when my recruiter, Suzie, told me I got the job. I was hesitant about moving to a new city where I didn’t know anyone, but I can say that by far, it’s one of the best decisions I’ve made and has helped me grow as a person.

Anything you wish you’d known before your interviews?

I remember being super nervous the first time and feared asking questions. But every interviewer I talked to told me they do not expect you to give the most optimal solution from the beginning; instead, they want to hear your thought process. They encourage you to ask questions to clear up any misunderstandings, because that helps you move towards a final solution. 

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

I reviewed the materials my recruiters provided me multiple times (a new helpful resource is the CTR Careers on Air series). I also reached out to my professors to help me refresh my knowledge of web technologies and fundamental computing concepts. If you’re not familiar with the cloud like I was and want to see how enterprise companies are using it today, I recommend checking out the Google Cloud Blog.

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

Never give up! I never thought I'd be working at Google and I wish I gave myself more credit to begin with. Don't be intimidated to apply and put yourself out there.