Tag Archives: students

These 27 organizations will mentor students in Google Code-in 2018

We’re excited to welcome 27 open source organizations to mentor students as part of Google Code-in 2018. The contest, now in its ninth year, offers 13-17 year old pre-university students from around the world an opportunity to learn and practice their skills while contributing to open source projects–all online!

Google Code-in starts for students on October 23rd. Students are encouraged to learn about the participating organizations ahead of time and can get started by clicking on the links below:
  • AOSSIE: Australian umbrella organization for open source projects.
  • Apertium: rule-based machine translation platform.
  • Catrobat: visual programming for creating mobile games and animations.
  • CCExtractor: open source tools for subtitle generation.
  • CloudCV: building platforms for reproducible AI research.
  • coala: a unified interface for linting and fixing code, regardless of the programming languages used.
  • Copyleft Games Group: develops tools, libraries, and game engines.
  • Digital Impact Alliance: collaborative space for multiple open source projects serving the international development and humanitarian response sectors.
  • Drupal: content management platform.
  • Fedora Project: a free and friendly Linux-based operating system.
  • FOSSASIA: developing communities across all ages and borders to form a better future with Open Technologies and ICT.
  • Haiku: operating system specifically targeting personal computing.
  • JBoss Community: a community of projects around JBoss Middleware.
  • KDE Community: produces FOSS by artists, designers, programmers, translators, writers and other contributors.
  • Liquid Galaxy: an interactive, panoramic and immersive visualization tool.
  • MetaBrainz: builds community maintained databases.
  • MovingBlocks: a Minecraft-inspired open source game.
  • OpenMRS: open source medical records system for the world.
  • OpenWISP: build and manage low cost networks such as public wifi.
  • OSGeo: building open source geospatial tools.
  • PostgreSQL: relational database system.
  • Public Lab: open software to help communities measure and analyze pollution.
  • RTEMS Project: operating system used in satellites, particle accelerators, robots, racing motorcycles, building controls, medical devices.
  • Sugar Labs: learning platform and activities for elementary education.
  • SCoRe: research lab seeking sustainable solutions for problems faced by developing countries.
  • The ns-3 Network Simulator Project: packet-level network simulator for research and education.
  • Wikimedia: non-profit foundation dedicated to bringing free content to the world, operating Wikipedia.
These 27 organizations are hard at work creating thousands of tasks for students to work on, including code, documentation, design, quality assurance, outreach, research and training tasks. The contest starts for students on Tuesday, October 23rd at 9:00am Pacific Time.

You can learn more about Google Code-in on the contest site where you’ll find Frequently Asked Questions, Important Dates and flyers and other helpful information including the Getting Started Guide.

Want to talk with other students, mentors, and organization administrations about the contest? Check out our discussion mailing list. We can’t wait to get started!

By Stephanie Taylor, Google Open Source

Google Code-in 2018 is looking for great open source organizations to apply

We are accepting applications for open source organizations interested in participating in Google Code-in 2018. Google Code-in (GCI) invites pre-university students ages 13-17 to learn by contributing to open source software.

Working with young students is a special responsibility and each year we hear inspiring stories from mentors who participate. To ensure these new, young contributors have a solid support system, we only select organizations that have gained experience in mentoring students by previously taking part in Google Summer of Code.

Organization applications are now open and all interested open source organizations must apply before Monday, September 17 at 16:00 UTC.

In 2017, 25 organizations were accepted – 9 of which were participating in GCI for the first time! Over the last 8 years, 8,108 students from 107 countries have completed more than 40,000 tasks for participating open source projects. Tasks fall into 5 categories:
  • Code: writing or refactoring.
  • Documentation/Training: creating/editing documents and helping others learn more.
  • Outreach/Research: community management, outreach/marketing, or studying problems and recommending solutions.
  • Quality Assurance: testing and ensuring code is of high quality.
  • Design: graphic design or user interface design.
Once an organization is selected for Google Code-in 2018 they will define these tasks and recruit mentors from their communities who are interested in providing online support for students during the seven week contest.

You can find a timeline, FAQ and other information about Google Code-in on our website. If you’re an educator interested in sharing Google Code-in with your students, you can find resources here.

By Stephanie Taylor, Google Open Source

Announcing Google Code-in 2018: nine is just fine!

We are excited to announce the 9th consecutive year of the Google Code-in (GCI) contest! Students ages 13 through 17 from around the world can learn about open source development by working on real open source projects, with mentorship from active developers. GCI begins on Tuesday, October 23, 2018 and runs for seven weeks, ending Wednesday, December 12, 2018.

Google Code-in is unique because, not only do the students choose what they want to work on from the 2,500+ tasks created by open source organizations, but they have mentors available to help answer their questions as they work on each of their tasks.

Getting started in open source software can be a daunting task for a developer of any age. What organization should I work with? How do I get started? Does the organization want my help? Am I too inexperienced?

The beauty of GCI is that participating open source organizations realize teens are often first time contributors, so the volunteer mentors come prepared with the patience and the experience to help these newcomers become part of the open source community.

Open source communities thrive when there is a steady flow of new contributors who bring new perspectives, ideas and enthusiasm. Over the last 8 years, GCI open source organizations have helped 8,108 students from 107 countries make meaningful contributions. Many of these students are still participating in open source communities years later. Dozens have gone on to become Google Summer of Code (GSoC) students and even mentor other students.

The tasks that contest participants will complete vary in skill set and level, including beginner tasks any student can take on, such as “setup your development environment.” With tasks in five different categories, there’s something to fit almost any student’s skills:
  • Code: writing or refactoring
  • Documentation/Training: creating/editing documents and helping others learn more
  • Outreach/Research: community management, marketing, or studying problems and recommending solutions
  • Quality Assurance: testing and ensuring code is of high quality
  • Design: graphic design or user interface design
Open source organizations can apply to participate as mentoring organizations for in Google Code-in starting on Thursday, September 6, 2018. Google Code-in starts for students October 23rd!

Visit the contest site g.co/gci to learn more about the contest and find flyers, slide decks, timelines, and more.

By Stephanie Taylor, Google Open Source

That’s a wrap for Google Summer of Code 2018

We are pleased to announce that 1,072 students from 59 countries have successfully completed the 2018 Google Summer of Code (GSoC). Congratulations to all of our students and mentors who made this our biggest and best Google Summer of Code yet.

Over the past 12 weeks, GSoC students have worked diligently with 212 open source organizations and over 2,100 mentors from all around the world, learning to work with distributed teams and developing complex pieces of code. Student projects are now public – take a closer look at their work.

Open source communities need new ideas to keep projects thriving and evolving; GSoC students bring fresh perspectives while helping organizations enhance, extend, and refine their codebases. This is not the end of the road for GSoC students! Many will go on to become mentors in future years and many more will become long-term committers.

And finally, a big thank you to the mentors and organization administrators who make GSoC possible. Their dedication to welcoming new student contributors into their communities is awesome and inspiring. Thank you all!

By Mary Radomile, Google Open Source

Doodle 4 Google is back! Show the world what inspires you

https://1.bp.blogspot.com/-eUjrFZmzIYA/W20MFSZHIWI/AAAAAAAAAzE/OHiv1hm_mawiTqhrb6DG4zah9fKHKPocQCLcBGAs/s640/D4G_What_Inspires_You.gif
Today we’re kicking off the 2018 Doodle 4 Google contest, where art-loving students from Class 1 to 10 from across India are invited to bring their imagination to life in a doodle of the Google logo. The winning masterpiece will be featured on www.google.co.in for a day on Children’s Day i.e. November 14, 2018, where millions of people will be able to see and appreciate it.





Does art inspire you? Clouds that look like faces? Trees that look like humans? Paper Planes? Discovering new galaxies? Artists have looked to the world around them for centuries to gain inspiration. At Google, we believe that these inspirations power the creativity and imagination that shapes the world. This year, we’re asking them to answer the question “What inspires you?”. From crayons to clay to water colors or graphic design, young artists can utilize any materials to bring their creation to life but like all Google Doodles, each doodle must incorporate the letters G-o-o-g-l-e.


Participating in the contest is fairly simple -- just download the form, let your imagination flow, draw your doodle and submit the same. Please visit ‘How it works’ page on the website for detailed instructions about participation.


Every year, we get thousands of brilliant entries from across the country, which makes picking a winner the hardest part of the contest. Luckily, we have some stellar guest judges to help, including creative mastermind Arun Iyer, famous artist and YouTube Kids Creator, Rob (Harun Robert), India’s leading female YouTube Creator Sejal Kumar and our original doodle team lead, Ryan Germick.


Submissions close on 6th October 2018 at 10:00PM IST. Internal judging and jury votes will be used to identify the top 20 doodles, which will be put up for public voting from October 23rd to November 5th, 2018, where the entire country will be able to vote for their favourite doodle. Winning doodle will be awarded a five lakh rupee college scholarship, along with many other prizes.


Every student between class 1 to 10 is welcome to enter their doodle at doodles.google.co.in/d4g. So for you parents, guardians and teachers out there: encourage your kids and students to participate. We can’t wait to see what inspires today’s generation the most.

By Sapna Chadha, Director of Marketing, Southeast Asia & India

Getting to know a research intern: Nicola Pezzotti

Google Research tackles the most challenging problems in CS and related fields. Being bold and taking risks is essential to what we do, and research teams are embedded throughout Google, allowing our discoveries to affect billions of users each day.

The compelling benefit to researchers is that their innovations can be implemented fast and big. Google’s unique infrastructure facilitates ideas’ speed to market — allowing their ideas to be trialled by millions of users before their papers are even published.

Today we’re talking to PhD Research Intern, Nicola Pezzotti, coming to us from the Google AI team in Zürich. Read on!


So tell us about yourself and your PhD topic …
I’m a PhD student in the Computer Graphics & Visualization group at the Delft University of Technology. My research interest is mainly oriented towards the application of Machine Learning algorithms, in particular Manifold Learning techniques, in a Visual Analytics context.

I’m particularly interested in the extraction of knowledge from large and high-dimensional datasets without an a-priori model of what we can find in the data. This is particularly useful in the context of exploratory data analysis of medical data and for the interpretation of AI models.

How did you get to work in this area?
I remember implementing my first AI, a not-so-intelligent one that played Tic-Tac-Toe, during the first year of high-school and I have always been interested in AI since then.

That being said, during my years at the University of Brescia, I started focusing on general purpose graphics processing unit programming (GPGPU) for Geometry Processing and I left my passion for AI on the side. I really had a lot of fun in implementing general purpose algorithms that make use of graphics hardware, and I continued to do so in my first work in industry in 2011.

Four years ago, I founded a PhD position in the Computer Graphics & Visualization group in Delft. The position was within the ImaGene project and aimed at finding insights that can help address neurodegenerative diseases such as Alzheimer's disease or dementia. I found the possibility to help in this domain very exciting and it gave me the opportunity to combine my knowledge of GPGPU techniques with my passion for AI.

Moreover, the name of the project is VAnPIRe, which gave me the opportunity to make a lot of silly jokes in the office ;)

Why did you apply for an internship at Google and how supportive was your PhD advisor?
GoogIe has top notch AI researchers – I wanted to join Google since the beginning of my PhD. My supervisor, Dr. Anna Vilanova, was very supportive and agreed with me that it would be an amazing opportunity to get in touch with some of these researchers and to make my research more impactful.

Last summer, I felt that I had enough contributions in the field to make my internship at Google a success. Hence, I applied for an internship in research at Google’s Zürich office. The hiring process was extremely fast and well handled and I found a host that was interested in my research topic.

What project was your internship focused on?
My host at Google is Alexander Mordvintsev, the creator of Google DeepDream. You may imagine the excitement that I had when I learned that I was chosen to support him in the development of novel techniques for better interpreting Deep Neural Networks results.

During my four month internship I worked on two different projects. First, I helped Alex in experimenting and getting DeepDream to work on different kinds of media, such as 3D objects and Compositional Pattern-Producing Network. This work focused on the artistic aspect of image parameterizations and is published on Distill.pub, an interactive and online journal. It has been particularly exciting to make the results of these techniques available to a large audience directly in the browser through Distill.pub, and reproducible in Google’s Colab Notebooks.

Then, I focused on developing a new implementation of the tSNE algorithm that scales to very large datasets and runs in the browser! tSNE is a manifold learning technique which is used to visualize high-dimensional feature vectors in 2-dimensional scatterplots while preserving the presence of clusters at different scales.

You may be familiar with its results due to its use for interpreting Deep Neural Network outputs in the TensorFlow Embedding Projector and TensorBoard. However, tSNE does not scale well to large datasets, due to its computational complexity. During my internship I developed a new implementation that scales much better thanks to a GPGPU approach that is implemented in WebGL. This implementation is released in the TensorFlow.js family ad you can try it directly in your browser.

I really liked this work as it shows how lateral thinking using a GPGPU approach can solve otherwise unscalable problems.

Did you publish at Google during your internship?
I did publish two papers, one for each project (ArXiV). I believe that my experience in Google will make my PhD thesis stronger and more impactful. I had the chance to publish on such a novel and creative journal such as Distill.pub, while remotely collaborating with researchers in Mountain View. It has been really a nice way to explore a new medium that brings academic knowledge to a large audience through easy to understand and interactive diagrams.

How closely connected was the work you did during your internship to your PhD topic?
Since I’ve been focusing on the scalability of the tSNE algorithm, in particular, and on Deep Neural Network understanding, in general, my work at Google was very much related to my PhD topic. You can read more about it here.

It has been particularly exciting to release my work as an open source work in the TensorFlow.js family. Bringing openly available algorithms to a larger audience is the icing on the cake for any PhD research.

Did you write your own code?
Writing code is my main driver and I’ve been happy to get in touch with so many exceptional programmers in Google. Releasing open source code has been very easy and I received a lot of support from different Google AI teams in Zürich and Cambridge.

What key skills have you gained from your time at Google?
I had the chance to work with a programming language, Typescript, that was completely new to me. It has also been really eye opening to learn how code is developed in a rigorous and high-quality way at Google.

What impact has this internship experience had on your PhD?
I see my experience at Google as the culmination of my PhD project.

I have been working on the topic of the scalability of manifold-learning algorithms such as tSNE for the last 3 years. Having an open source implementation that can run in the browser for large datasets is really satisfying and I can’t wait to see what other researchers can build using this code. I would not have been able to have had such exposure and impact without this experience.

Looking back on your experiences now: Why should a PhD student apply for an internship at Google? Any advice to offer?
Besides working closely with great researchers and engineers, I have to say that the most striking aspect of my time at Google was how wide the exposure to high quality and open research is.

Every week a number of extremely interesting guests are invited to host talks held in the office. You are free to join, either in person or on a video stream. Some days you really have to choose which one is the best to attend since they are so good and there are so many! If you join Google for an internship you should not miss them, they can help your research in unexpected ways.

Magnificent mentors of Google Summer of Code 2018

Mentors are the heart and soul of the Google Summer of Code (GSoC) program and have been for the last 14 years. Without their hard work and dedication, there would be no Google Summer of Code. These volunteers spend 4+ months guiding their students to create the best quality project possible while welcoming them into their communities – answering questions and providing help at all hours of the day, including weekends and holidays.

Thank you mentors and organization administrators! 

Each year we pore over heaps of data to extract some interesting statistics about the GSoC mentors. Here’s a quick synopsis of our 2018 crew:
  • Registered mentors: 2,819
  • Mentors with assigned student projects: 1,996
  • Mentors who have participated in GSoC for 10 or more years: 46
  • Mentors who have been a part of GSoC for 5 years or more: 272
  • Mentors that are former GSoC students: 627
  • Mentors that have also been involved in the Google Code-in program: 474
  • Percentage of new mentors: 36.5%
GSoC 2018 mentors are from all parts of the world, hailing from 75 countries!

If you want to see the stats for all 75 countries check out this list.


Another fun fact about our 2018 mentors: they range in age from 15-80 years old!
  • Average mentor age: 34
  • Median mentor age: 33
  • Mentors under 18 years old: 26*
GSoC mentors help introduce the next generation to the world of open source software development – for that we are very grateful. To show our appreciation, we invite two mentors from each of the 206 participating organizations to attend our annual mentor summit at the Google campus in Sunnyvale, California. It’s three days of community building, lively debate, learning best practices from one another, working to strengthen open source communities, good food, and lots and lots of chocolate.

Thank you to all of our mentors, organization administrators, and all of the “unofficial” mentors that help in the various open source organization’s communities. Google Summer of Code is a community effort and we appreciate each and every one of you.

Cheers to yet another great year!

By Stephanie Taylor, Google Open Source

* Most of these 26 young GSoC mentors started their journey in Google Code-in, our contest for 13-17 year olds that introduces young students to open source software development.

Google Student Blog 2018-08-02 01:02:00

Welcome to the 30th 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 User Experience (UX) Engineer Intern, Shea Hunter Belsky. Read on!



Can you tell us a bit about yourself?
I recently graduated from Cornell University, where I studied Information Science with a concentration in User Experience. The reason I can intern this summer is because I'm returning there in the Fall to finish a Master's in Information Science as well.

 I try to focus on the union of developers and user experience. I answer questions like: How can developers be meaningfully invested in the product design cycle? Can designers be more informed about technical constraints and limitations, in order to better inform the design cycle? And how can developers and designers support each other in their goals?

In my free time, I love to run, hike, snow-ski in the winter, waterski in the summer, and practice photography all year long. I'm also recently getting into Dungeons and Dragons!

What’s your role at Google?
I'm a User Experience Engineer (UXE) on the sumUX team, focusing on Search and Assistant. I focus on internal prototyping: empowering designers and researchers to answer the big questions they have, and validate (or invalidate) their research. The process of prototyping, and the tools we use to make it happen, promote much more rapid iteration and ideation. Prototyping allows researchers and designers to quickly identify good and bad things in designs, make adjustments, and test them again until they've got it just right. I’m currently working on a tool to optimize this process even further.

Complete the following: "I [choose one: code/create/design/build] for …"
I create for everyone. Though I work mostly with other Googlers, the ramifications of the prototypes I have worked on are very far-reaching – they’re used by millions of people. It may take a long time for my prototype to eventually become the “real thing”, but when it does, I know it won't just be a few people who use Assistant, but rather countless people who use it in their everyday lives.

What inspires you to come in every day?
Right now I've been working on a tool that will allow designers and researchers to create, edit, share, and test their own prototypes, rather than needing myself or another UX Engineer to make one. This makes the process of testing, evaluating, and improving upon designs even faster. Other tools do this to an extent, but the parameters of the prototypes that the designers and researchers need are such that using one of these tools would take more time than is necessary. I’m learning it's not necessary to over-engineer a solution when something simpler can do the exact same thing, but with faster results. This excites me because it empowers members of the design process to become more involved in the creation and ideation of a product.

Can you tell us about your decision to enter the process?
I'd applied to both the Software Engineering and Product Design roles in the past, but I didn't feel I fit strongly into either category. I had a great deal of experience in both areas (writing code and participating in the design process), but I still considered myself to be somewhere in between the two.

I discovered the UX Engineering internship role in early January, my senior year at Cornell, and it was love at first sight. Not only did I meet most of the qualifications, I felt like it was the perfect blend of development experience and design knowledge that I had been accumulating. It was the destination I didn't know I was heading towards until I saw the signs.

How did the recruitment process go for you?
I applied directly to the position on Google's job site (google.com/students). I was super appreciative of how timely, transparent, and thoughtful the recruitment process was. I had a very good idea of what was going to happen at every step of the process, and I didn't feel like I was missing anything during any step.

To finish, what do you wish you’d known when you started the process?
A UX Engineering interview is different from other engineering roles in that there's two different "lenses" to refer to a UXE – the developer-lens and the design-lens.

A developer-lens UXE writes production code, and should be familiar with writing performant and sustainable code for their platform of choice. I'm a web UXE, but there are UXE roles for other languages (I know we at least have Android and iOS UXEs.) Developer-lens UXEs collaborate with and report to software engineers more closely than designers and researchers. That being said, they are still informed in the design process and are familiar with what needs to happen in that regard.

A design-lens UXE focuses more on the design side, working with designers and researchers to help them do their jobs better (through prototyping, internal tooling, and whatever else they need). The obligations of a design UXE tend to vary on project, but focus on tooling and prototyping.

As a function of this, the interview for a UXE can vary from person to person. My interview was part development and part design, testing my general competency with web development and also evaluating my knowledge in UX. This is different from other kinds of interviews that focus on just one area or the other. That is something to be prepared for.

My Path To Google: Robert Maldonado, Engineering Practicum Intern

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

To celebrate the upcoming #NationalInternDay, today’s post is all about one of our Engineering Practicum Interns, Robert Maldonado. Engineering Practicum is a 12-week internship for first and second-year undergraduate students with a passion for computer science. Keep our Engineering Practicum job listing bookmarked for when it re-opens in the Fall and, in the meantime, check out the FAQs. Read on!



Can you tell us a bit about yourself?
I am a rising third year studying software engineering at the University of California, Irvine (UCI). I am very passionate about leadership, personal development, and community outreach. During my sophomore year, I served as Vice President of Outreach for the UCI Chapter of the Society of Hispanic Professional Engineers (SHPE). As a result, I was able to attend Google’s Hispanic Student Leadership Summit two years in a row. This upcoming year, I will be the student head of a planning committee for a regional SHPE conference for hundreds of SHPE members.

For over a year I’ve also been doing research in databases and distributed systems in a software engineering lab at UCI.

As a hobby, I love creating things through various art mediums such as painting, drawing, writing, sewing, and photography. I am always seeking opportunities to create new abstract projects!

What’s your role at Google?
I am an Engineering Practicum Intern for the Node Storage Team, which is a part of Technical Infrastructure. My work is centered around the Linux Operating System Kernel used at all of Google’s Data Centers. I love my work because it is very complex and every day I am learning something new!
Complete the following: "I [choose one: code/create/design/build] for..."
I create for a future where everyone has the opportunity to learn, develop, and prosper.

What inspires you to come in every day?
I love to come to work every day because my work is impactful and my team is amazing! I am very fortunate that my project will be making a real difference at Google. Although I’ll admit my project is a bit intimidating, my hosts and teammates are always more than happy to help. I love talking to my teammates at lunch and around the office, especially because they all embrace my nerdy weirdness!
Can you tell us about your decision to enter the process?
There are a lot of reasons why people would want to work at Google – the complex problems, the benefits, the pay, the work-life balance, the list goes on and on. That being said, I’ve always wanted to become a Googler because of Google’s culture and values, which aim to create positive change in the world.

During my freshman year of college, I found out about Google’s Engineering Practicum Internship (which is specifically for standing 1st and 2nd-year college students) and thought it was a perfect way to start a career as a Googler. Although I found out about the internship too late to apply my freshman year, I knew I wanted to apply during my second year.

I felt confident in my application because I used the prompts to express my passions and because I had developed significant professional/technical skills during my first year of college, however, the thought that thousands of people were applying for the same internship scared me a little.  Nevertheless, throughout the interview process I was determined to show how Googly I am.

I am very grateful to have had the opportunity to interview and especially to receive an offer.

Robert presenting at #HSLS18


How did the recruitment process go for you?
My recruitment process was, unique, to say the least. I was referred to apply by my mentor, the software engineering PhD student who I do research with, and my application process was very smooth. My interview process wasn't as smooth as I expected, which had me pretty worried that I wouldn't make it! My recruiter helped navigate the issues I had, and it all worked out in the end because I was given an offer.

What do you wish you’d known when you started the process?
I wish I would have started preparing for the technical interviews way earlier. In about a month and a half I prepared by learning about algorithms and data structures, doing practice problems on a whiteboard, and participating in mock interviews. Although I was able to cover a lot of content, there were a lot of sleepless nights involved.

In hindsight, I should have used the summer to prepare rather than squeezing it in during the fall quarter.

Can you tell us about the resources you used to prep?
To prepare for the technical interviews I watched a ton of videos. YouTube is a great way to learn about data structures and algorithms and to find practice problems. @GoogleStudents YouTube channel has a number of videos on technical questions that I watched.

To finish, do you have any tips you’d like to share with aspiring Googlers?
In no particular order, here are a few things that I would tell any aspiring Googler :)

1) Stay hungry
Google is looking for people that have a wide variety of skills and experiences, but sometimes gaining  those skills are hard and/or will make you uncomfortable, but only because you haven’t done them enough! Join clubs/programs that interest you, become a leader, build projects, do research, learn a new language – the possibilities are endless you just need to be hungry enough to take them.

2) Google does pretty much everything
Whether you are studying Software Engineering, Business, Mechanical Engineering, Psychology, Teaching, or anything in between/outside there is a pretty good chance that Google needs someone like you!

3) Non desistas, non exieris (never give up, never surrender)
Life is hard, and sometimes things don’t go as planned, but never ever give up on accomplishing your dreams. The most passionate and successful Googlers that I personally know come from tough backgrounds!

4) You miss 100% of the shots you don’t take
The following are all true: Google is a huge company, a ton of people apply, very few people get in, you can do anything you put your mind to, applying to Google can be intimidating but it is far from impossible, you can do it.


2018 Online Marketing Challenge teams up with Google Ad Grants – registration open now!

Don't miss out on your chance to bring marketing theory to life through a practical hands-on learning experience. Over the past few months, we've been listening to your feedback and exploring opportunities to continue to engage, empower and grow students in the digital marketing space. Today, we are excited to announce that the foundation of the Online Marketing Challenge (OMC) will be returning in partnership with nonprofits from the Google Ad Grants program!


What is the Online Marketing Challenge again?

OMC is a unique opportunity for students to get real-world experience creating and executing online marketing campaigns for real nonprofits through the Google Ad Grants program. Ad Grants empowers over 38,000 nonprofit organizations with free in-kind AdWords advertising of up to $10,000 a month. The new OMC will pair student teams with Ad Grants’ nonprofit organizations for students to gain valuable real-world skills through working with nonprofits’ AdWords accounts and drive real social impact. OMC is a great way to increase your depth of experience on your resume and develop your skill set, all while helping nonprofits change the world!


Who can participate?
The Challenge is open to higher education students from undergraduate or graduate programs, regardless of major. Students must form teams of 2-5 members and register under a verified faculty member, lecturer or instructor currently employed by an accredited higher education institute. Google will partner student teams with select nonprofits that are a part of the Ad Grants program and have opted in to participate in the Challenge.


How does it work?
1. Student teams of 2-5 members review Online marketing trainings, build their digital skills and pass the Academy for Ads AdWords Fundamentals Exam.
2. Student teams partner with an Ad Grants nonprofit, meet with the organization to understand their cause, audience and goals, evaluate their existing campaign structure and performance, and develop a comprehensive digital marketing strategy.
3. Using the free Google Ad Grants AdWords advertising budget — up to $10,000 USD per month — student teams develop and execute online advertising campaigns over the course of at least 4 weeks to help drive conversions for their nonprofit partner.
4. At the end of the partnership, student teams complete a Post-Campaign Analysis and deliver future recommendations to their nonprofit partner to help them continue to thrive online.
5. Student teams that demonstrate strong AdWords knowledge, develop a thorough online marketing strategy, execute optimized AdWords campaigns and provide a post-campaign analysis with future recommendations for their nonprofit partner will receive a personalized certificate from Google recognizing their academic achievement and social impact. Top performing teams also have the opportunity to submit their story to be featured in Google’s Social Impact Spotlight Series.

Registration is now open through the official website. Before registering, please familiarize yourself with our guidelines, as well as Ad Grants’ program policies and limitations. For any questions, please first review our FAQs page