Google Code-in
annual programming competition hosted by Google
Google Code-in (GCI) was an international annual programming competition hosted by Google LLC that allowed pre-university students to complete tasks specified by various, partnering open source organizations. The contest was originally the Google Highly Open Participation Contest, but in 2010, the format was modified. Students that completed tasks won certificates and T-shirts. Each organization also selected two grand prize award winners who would earn a free trip to Google's Headquarters located in Mountain View, California. In 2020, Google announced cancellation of the contest.
History
The program began as Google Highly Open Participation Contest during 2007–2008 aimed at high school students. The contest was designed to encourage high school students to participate in open source projects. In 2010, the program was modified into Google Code-in. After the 2014 edition, the Google Melange was replaced by a separate website for Google Code-in. Mauritius, an African country, participated for the first time in 2016, and was noticed for its strong debut and in 2017, produced its first Grand Prize winner.
The public source identifies “Google Code-in” as annual programming competition hosted by Google. This brief keeps that definition visible, then builds a research path around Google, Code-in and annual.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Google Code-in”, the useful work is to connect “annual programming competition hosted by Google” to the records capable of establishing context and consequence.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated May 23, 2026. The linked authority identifier is Q5583820. VIAF identifies the subject as 204144782723459249782. None of the 2 selected statements returned an explicit reference. The first chronological checks are 2010, 2020, 2007 and 2008.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Google Code-in”, its source revision and the description used here.
- Expand the search: follow Google Code-in primary sources, Google Code-in archive and Google research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Google Code-in”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Google Code-in” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.