Google Summer of Code

closedOfficial website

Write real code for open-source orgs, mentored full-time over the summer.

StipendedMentoredRemotePortfolio-gradeGoogle-backed

About the program

Google Summer of Code is the program that turned open-source contributing into a summer rite of passage. Since 2005 Google has paid thousands of contributors per year to ship real features into hundreds of open projects, with a mentor from the host organization guiding the work from proposal to final evaluation.

You do not apply to Google - you apply directly to an organization like Kubernetes, PyTorch, or the Linux Foundation with a written proposal. Accepted contributors work full or part time across the summer in three evaluation phases, and the stipend scales with the difficulty band the organization assigns.

Primary stack

C++PythonGoJavaScriptJavaKotlinRustTensorFlow

Technical focus

AI/ML infraDeveloper toolsCloud-nativeCompilersWeb frameworksScience software

The path

01
Organizations apply (Feb)
Projects submit their org application to Google; only approved orgs can host contributors this cycle.
02
Community bonding (Apr - May)
Introduce yourself on the org's channels, claim a practice task, and start the mentor conversation before the proposal window slams shut.
03
Proposal window (late Mar - early Apr)
Write a weekly-timeline proposal for one of the org's published ideas. This document is the entire audition - clear scope beats clever scope.
04
Coding period (Jun - Aug)
Three evaluations gate the stipend: micro/mid-term check-ins and a final wrap-up. Mentors can extend once for a slipping project.
05
Bonding buffer (Aug - Sep)
Contributors keep opening PRs after evaluations end; a large share of GSoC alumni stay on as regular maintainers.

Who it's for

Developers who can commit 30-40 focused hours a week to one codebase
Anyone with a mergeable PR or two already - the proposal lands far better with proof of participation
Contributors targeting a flagship repo they want on their resume