Skip to main content
TL;DR — GSoC is a global, paid, remote program where contributors work on real open-source projects under expert mentorship for 10–22 weeks. Google pays the stipend. You don’t need to be a student anymore — self-taught developers and recent grads are eligible too.

​
What is GSoC?

Google Summer of Code connects beginner-to-intermediate developers with open-source organizations. Each year, Google funds contributors to spend their summer (or any 10–22 week window) writing code for a participating org. You get:
  • A real-world codebase to work on — not a toy project
  • A dedicated mentor from the organization
  • A stipend from Google (adjusted by your country)
  • A line on your resume that recruiters actually recognize
Since 2005, GSoC has brought in 19,000+ contributors from 112 countries, producing 43 million+ lines of open-source code.

​
Who Can Apply?

You’re eligible if you are:
  • 18 years or older at the time of registration
  • A new or beginner open-source contributor (no prior GSoC acceptance)
  • Eligible to work in your country of residence
  • Not an organization admin or mentor for the same cycle
Eligible roles include students, self-taught developers, coding bootcamp graduates, recent university graduates (within 6 months), and people returning to tech.
You do not need to be enrolled in a university. GSoC dropped the “student-only” restriction in 2022.

​
Timeline (Typical Annual Cycle)

The exact dates shift each year, but the overall flow stays the same.
PhaseApproximate TimingWhat Happens
Org applicationsJanuaryOrganizations apply to participate
Orgs announcedFebruaryGoogle publishes the list of accepted orgs
Contributor applications openMid-MarchYou submit proposals to orgs
Contributor applications closeEarly AprilDeadline for all proposals
Accepted contributors announcedEarly MayGoogle publishes the results
Community bondingMay (2–3 weeks)Meet your mentor, set up dev environment
Coding periodJune – AugustBuild your project
Midterm evaluationMid-JulyMentor evaluates your progress (triggers 45% stipend)
Final evaluationLate August – SeptemberSubmit final work (triggers remaining 55% stipend)
Always check the official GSoC timeline — dates change every year.

​
Stipends

GSoC uses Purchasing Power Parity (PPP) to adjust stipends by country. Payments are made via Payoneer.
Project SizeHours/WeekDurationStipend Range
Small~90 hours total10–22 weeks750–750 – 1,650
Medium~175 hours total10–22 weeks1,500–1,500 – 3,300
Large~350 hours total10–22 weeks3,000–3,000 – 6,600
Examples (medium project):
  • Pakistan, India, Bangladesh → ~$1,500
  • Turkey, Mexico, Poland → ~1,800–1,800–2,100
  • Germany, UK, France → ~$2,700
  • USA, Canada, Australia → ~$3,300
Payments are split: 45% after midterm evaluation and 55% after final evaluation.

​
Step-by-Step: How to Get Selected

​
Phase 1: Explore Organizations (2–3 months before apps open)

1

Browse the org list

Once organizations are announced (usually February), visit summerofcode.withgoogle.com and browse the list. Filter by technology, topic, or language.
2

Shortlist 3–5 organizations

Pick orgs that match your skills and interest you. Don’t just chase “easy” projects.
3

Read their Ideas Page

Every org publishes a list of project ideas. Read all of them. Note which ones excite you.
4

Join their communication channels

Most orgs use Slack, Discord, IRC, or mailing lists. Introduce yourself, ask questions, and start lurking.

​
Phase 2: Start Contributing (Before Applications Open)

This is the most important phase. Orgs strongly prefer contributors who have already shown up.
1

Set up the development environment

Clone the repo, build the project locally, run the tests. Document any setup issues you encounter — this itself can be a contribution.
2

Pick a 'good first issue'

Most orgs label beginner-friendly issues. Start there. Even fixing a typo in docs counts.
3

Submit a pull request

Get at least 1–2 merged PRs before the application window opens. This shows you can work with their codebase and follow their contribution guidelines.
4

Engage with mentors

Ask thoughtful questions about the project idea you’re targeting. Understand the scope, technical challenges, and what the mentor expects.

​
Phase 3: Write a Killer Proposal

Your proposal is the single most important factor in selection. Here’s the structure that works:

​
Proposal Template

## 1. Contact Information
- Name, email, GitHub, timezone, university (if applicable)

## 2. Synopsis
- 2–3 sentence summary of what you'll build and why it matters

## 3. About Me
- Relevant skills, past projects, open-source experience
- Link to your PRs/contributions to this org

## 4. Project Description
- Detailed technical approach
- What technologies/libraries you'll use
- How your work integrates with the existing codebase

## 5. Timeline & Milestones
- Week-by-week breakdown
- Clear deliverables for midterm and final evaluation
- Buffer time for unexpected issues

## 6. Availability
- Hours per week you'll dedicate
- Any conflicts (exams, travel, other commitments)
- Be honest — mentors appreciate transparency

## 7. Why This Project?
- What draws you to this org and this specific idea
- How it aligns with your goals
Common mistakes that get proposals rejected:
  • Copy-pasting the project idea description without adding your own analysis
  • Unrealistic timelines (too much in too little time)
  • No prior contributions to the organization
  • Vague technical approach (“I will implement the feature”)
  • Applying to 10+ orgs with generic proposals

​
Phase 4: After Acceptance

1

Community bonding (2–3 weeks)

Set up your dev environment, agree on communication cadence with your mentor (daily standups? weekly calls?), define the scope clearly, and create a project board or issue tracker.
2

Coding period

Ship code regularly. Don’t go silent for days. Push small, reviewable PRs. Ask for feedback early.
3

Evaluations

Your mentor evaluates you at midterm and final. Passing triggers stipend payments. Failing midterm means you’re removed from the program.

​
Pro Tips from Past GSoC Contributors

  1. Start early — The best contributors start engaging with orgs in December/January, not March
  2. Quality over quantity — One excellent proposal beats five mediocre ones
  3. Read past accepted proposals — Many orgs publish them. Study the structure and depth
  4. Don’t fear “hard” projects — Less competition, and mentors give more support
  5. Communicate proactively — If you’re stuck, say so. If you’ll miss a deadline, say so early
  6. Document everything — Write blog posts about your progress. It helps you and future contributors

​
Resources

ResourceLink
Official Websitesummerofcode.withgoogle.com
Timelinedevelopers.google.com/open-source/gsoc/timeline
Stipend Referencedevelopers.google.com/open-source/gsoc/help/student-stipends
Student Guidegoogle.github.io/gsocguides/student
Mentor Guidegoogle.github.io/gsocguides/mentor
265+ Accepted Proposals (GSoC, LFX, SoB)github.com/devweekends/open-source-proposals
Finding the Right Projectgoogle.github.io/gsocguides/student/finding-the-right-project

​
Frequently Asked Questions

Yes. Since 2022, GSoC is open to anyone who is new to open source — students, self-taught developers, bootcamp grads, career changers, and recent graduates.
Yes, you can submit up to 3 proposals to different organizations. But quality matters more than quantity.
It depends on the organization. You’ll find projects in Python, JavaScript, C/C++, Rust, Go, Java, Ruby, and many more. Pick orgs that use languages you’re comfortable with.
No. But you need to demonstrate that you can navigate it. Setting up the project locally, reading the architecture docs, and making a small contribution goes a long way.
You’re removed from the program and don’t receive further stipend payments. This is rare if you communicate regularly with your mentor.
Fully remote. You can work from anywhere in the world.