Interview
Google Summer of Code 2027: Dates, Timeline, Stipend & How to Get Selected
Google Summer of Code 2027 dates are not announced. See the official 2026 timeline, stipend by country, eligibility and a Nov-to-March plan.

Practise the rounds for Google Summer of Code
Short answer: Google has not announced GSoC 2027 dates. The official 2026 cycle had organisation applications from 19 January to 3 February, contributor proposals from 16 to 31 March, and results on 30 April. If 2027 follows the same shape (an inference, not an announcement), you have until roughly early March 2027 to find an organisation, make a first contribution and draft a proposal. Starting in November is early enough to do it properly.
Google Summer of Code is the rare student programme where the selection process is mostly visible work. Nobody is grading how you answer a trick question. Mentors read your proposal, look at your pull requests and judge whether you will finish the project. That makes it very preparable, and it also means the people who start in March usually lose to the people who started in November.
This guide covers what is officially published (eligibility, stipend, project sizes, the 2026 timeline), a clearly labelled guess at 2027, and a month-by-month plan. For the wider contest landscape, see the hackathon calendar 2026-27.
GSoC 2027: Key Dates (last checked 13 Nov 2026)
| Milestone | 2026 (official) | 2027 |
|---|---|---|
| Organisations begin applying | 19 Jan | Not announced. Expected mid-to-late January (inferred from 2026) |
| Organisation application deadline | 3 Feb | Not announced. Expected early February (inferred) |
| Accepted organisations published | 19 Feb | Not announced. Expected mid-to-late February (inferred) |
| Discuss ideas with organisations | 19 Feb to 15 Mar | Expected the same few weeks after the list drops (inferred) |
| Contributor applications open | 16 Mar | Not announced. Expected mid-March (inferred) |
| Contributor application deadline | 31 Mar | Not announced. Expected late March (inferred) |
| Accepted projects announced | 30 Apr | Not announced. Expected end of April (inferred) |
| Community bonding | 1 to 24 May | Expected May (inferred) |
| Coding begins | 25 May | Expected late May (inferred) |
| Midterm evaluation | 6 to 10 Jul | Expected early July (inferred) |
| Final week (standard projects) | 17 to 24 Aug | Expected mid-to-late August (inferred) |
| Extended projects end | 2 Nov | Not announced |
The 2026 column comes from the official GSoC timeline, where all times are 18:00 UTC. Every cell in the 2027 column is our inference from that pattern. Google can and does shift things, so treat the table as a planning aid and check the official site once the 2027 timeline appears. As of 13 Nov 2026 the official timeline page still shows the 2026 cycle only and carries no 2027 announcement, and the page's own note says dates can shift a little each year.
Registration is not one date. There are two windows: one for organisations, and later one for contributors (you). The "GSoC 2027 registration last date" you care about is the contributor proposal deadline, which in 2026 was 31 March.
What GSoC Is (Officially)
GSoC pairs people who are new to open source with mentors from participating organisations for a programming project of 12 weeks or more. The programme site says it has worked with more than 1,000 organisations and over 21,000 newcomers since 2005. Organisations range from Linux-adjacent infrastructure to scientific libraries, compilers, web frameworks, AI tooling and education projects.
You do not apply to Google for a project. You apply to an organisation with a proposal for a project, usually one drawn from the organisation's own ideas list or a variation you negotiate with a mentor.
GSoC Eligibility
From the official FAQ:
- You must be at least 18 at registration
- You must be eligible to work in your country of residence
- You must be a student or an open source beginner. Regular contributors to an open source project are not treated as beginners
- You cannot have been accepted into GSoC more than once before
- You cannot reside in a US-embargoed country. The FAQ names Russia, Belarus and the DNR/LNR regions as ineligible
- Proposals must come from individuals, not groups
- You can submit up to three proposals, but only one can be accepted
- Check each organisation's AI policy before you apply. The FAQ warns that using AI to write your proposal may lead to rejection, so write it yourself and use tools only where the organisation allows
There is no requirement to be enrolled in a particular degree or year. That said, a first-year student with a clean, finished project beats a final-year student with a vague proposal.
GSoC Stipend: How Much You Are Paid
The stipend depends on project size and your country of residence. Google's stipend page lists amounts in USD in tiers. Examples from that page:
| Tier | Small | Medium | Large | Example countries |
|---|---|---|---|---|
| Base | $750 | $1,500 | $3,000 | India, Brazil, Mexico, Nigeria |
| 2 | $900 | $1,800 | $3,600 | China, Chile, Greece, Singapore |
| 3 | $1,050 | $2,100 | $4,200 | Portugal, South Korea, Spain |
| 5 | $1,350 | $2,700 | $5,400 | France, Germany, Japan, Ireland |
| 6 | $1,500 | $3,000 | $6,000 | Canada, UK, US, Sweden |
| 7 | $1,650 | $3,300 | $6,600 | Australia, Norway, Switzerland |
(Tier 4 also exists; see the page for the full country list.) Three details matter:
- GSoC stipend in India falls in the base tier: $750, $1,500 or $3,000 depending on whether your project is small, medium or large.
- For a standard 12-week project, the page describes 45% paid after the first evaluation (11 July in the year it was checked) and 55% after the final evaluation (1 September). Longer projects have different dates; your dashboard shows yours.
- Countries not in the table are not eligible for payment because of the payment provider. For the other side of the table: the FAQ says mentoring organisations receive a small stipend per accepted contributor (not Google-led or government-affiliated ones), and it does not mention a separate stipend for individual mentors. Payment depends on passing evaluations, not on whether your code is eventually merged, and you must provide tax forms and proof of residency.
We read this table in October 2026. Google reviews amounts periodically, so confirm on the page after 2027 is announced.
Project sizes
Per the FAQ: small is about 90 hours, medium about 175 hours, large about 350 hours. Scope can be adjusted with your mentor, and end dates can stretch to 22 weeks in total if you both agree. The programme guidance says roughly 75% of projects are the standard 12 weeks.
How to Get Selected in GSoC
Selection is competitive, and the programme does not publish an acceptance rate we can rely on, so ignore any number you see quoted without a source. What the official guidance does say is useful on its own: contact organisations early and talk to the community before submitting. In practice, selected proposals share a few traits.
1. You are already known to the mentors
Mentors rank proposals from people they recognise. A contributor who has had two small pull requests merged and has asked sensible questions in the project's chat is a lower risk than a stranger with a better-written PDF. Contributions are the strongest signal you can produce.
2. Your proposal is specific
Weak proposals say "I will improve the testing framework." Strong ones name modules, list what you will change in week 1 versus week 6, say how you will know it works, and acknowledge what could go wrong. A mentor should be able to picture the pull requests.
3. The scope fits the hours
Over-scoping is the most common reason a good candidate is ranked down. A medium project that you can finish and test properly beats a large one you might abandon at midterm.
4. You show you can work independently
GSoC mentors volunteer their time. Proposals that demonstrate you can read unfamiliar code, run the test suite, and unblock yourself get ranked higher.
5. You communicate in public
Ask questions in the organisation's chat or mailing list instead of private messages, and write them well: what you tried, what you expected, what happened.
Nov to Mar: A Month-by-Month Plan
This assumes proposals close in late March, as they did in 2026. If dates move, the order still holds.
November: build the base
- Pick one language and one domain you can stay with for six months (for example Python plus scientific computing, or TypeScript plus developer tooling)
- Learn Git properly: fork, branch, rebase, resolve conflicts, write a clear commit message and pull-request description
- Read previous years' organisations on the GSoC archive and note which ones return every year. Returning organisations are the safest bet while the 2027 list is unknown
- Fix your fundamentals: if data structures are shaky, the DSA Patterns Sheet covers them in an order that also helps later interviews
December: shortlist and lurk
- Shortlist 5 to 8 returning organisations that match your stack
- For each: read the contributing guide, join the chat or mailing list, and just read for a week
- Build each project locally and run its tests. Getting the dev environment working is a real milestone; write down every snag, because documentation fixes for those snags are legitimate first contributions
- Read last year's accepted projects for your shortlist to see what scope looked like
January: first contributions
- Pick good-first-issue or documentation tickets and open your first pull requests. Aim for 2 to 3 merged contributions across your top 2 or 3 organisations by the end of the month
- Follow review comments carefully. How you respond to feedback is itself evaluated
- Watch for organisation applications opening (mid-to-late January in 2026). Do not wait for the list to start contributing; contributions made now carry over when your organisation is accepted
February: the list arrives
- When accepted organisations are published (19 Feb in 2026), cut your shortlist to the 2 or 3 that were accepted and have ideas you can handle
- Read every idea on the list, then message the mentor with a short, specific note: what you understand so far, what you have contributed, one or two questions
- Pick one primary idea. You may submit up to three proposals, but focus beats breadth
Early March: draft the proposal
- Write the proposal and share the draft with your mentor early, ideally two weeks before the deadline
- Include: a summary, why you, a technical plan, a week-by-week timeline, deliverables, risks, your availability and any other commitments (exams, internships)
- Cite your merged pull requests and links to prior work
- Revise twice based on mentor feedback
Late March: submit
- Submit at least two days before the deadline. Systems get busy and the deadline is firm
- Proof-read for scope against the hour count (90, 175 or 350)
- If you submit extra proposals, make each one as good as the first
April and after
- Results are announced about a month after the window closes (30 April in 2026)
- If you are not selected, keep contributing. Many accepted contributors applied twice, and your merged work is permanent. Remember the rule that you cannot be accepted more than once before, so one early success uses up your first slot
What a Strong Proposal Looks Like (Sample Outline)
Here is an original, generic skeleton. Do not copy it; adapt it to your organisation's ideas list.
- Title and one-paragraph summary: what changes for users when this is done
- About me: relevant experience, links to merged pull requests, time zone, weekly hours
- Problem: what is broken or missing today, with links to the issue tracker
- Approach: components you will change, with reasons, and the alternatives you rejected
- Timeline: bonding period tasks, then weeks 1 to 12 with a deliverable each, with a buffer week before midterm
- Testing and documentation: how you will prove it works and how others will learn it
- Risks: what could slip and your fallback
Common Mistakes
- Applying with no contributions. The programme guidance specifically says to engage with the community first
- Generic emails to every mentor. Mentors can tell
- Copying an idea description as a proposal. Show your own thinking
- Choosing the organisation with the most fame rather than the best fit. Popular organisations get far more applicants per slot
- Treating contributions as a checkbox. One thoughtful, well-tested change is worth more than ten typo fixes
- Overlapping commitments. Mentors worry if your proposal period collides with exams or a full-time internship
How GSoC Helps Your Interview Prospects
GSoC is a genuine resume line, but only if you can discuss it. Interviewers will ask what you built, what was hard, and what you would do differently. Practise that story out loud with an AI mock interview and keep your coding sharp with timed OA-style practice and the DSA Patterns Sheet, since open-source work does not replace interview fundamentals.
FAQs
What is the GSoC 2027 timeline?
Not announced as of 13 Nov 2026. The official 2026 timeline ran: organisation applications 19 Jan to 3 Feb, accepted organisations 19 Feb, contributor applications 16 to 31 March, results 30 April, coding from 25 May, midterm 6 to 10 July and final week 17 to 24 August. We expect a similar shape in 2027 but that is inference.
What is the last date to apply for GSoC 2027?
Not announced. The date you need is the contributor application deadline, which was 31 March in 2026 (18:00 UTC). Do not wait for it: contributions in the months before are what mentors rank.
Is GSoC an internship, and who can join?
Google calls it a mentored programme, not an internship, though people list it as one on resumes. You must be 18 or older and a student or an open source beginner. Details are in the eligibility section above.
Do mentors get a stipend?
The official FAQ says mentoring organisations receive a small stipend per accepted contributor, unless they are Google-led or government-affiliated. It does not mention a separate stipend for individual mentors.
What is the GSoC 2027 registration date?
Not announced. In 2026 contributor proposals ran from 16 to 31 March; organisations applied from 19 January to 3 February. If 2027 follows that pattern, expect proposals in March (inferred). Check the official timeline.
Is GSoC 2027 happening?
Nothing official on the site says otherwise, but there is no 2027 announcement yet either. The programme has run annually since 2005 according to its own site.
How much is the GSoC stipend in India?
The stipend page places India in its base tier: $750 (small), $1,500 (medium) or $3,000 (large), paid in two instalments for standard projects after passing evaluations.
Do I need to be a student?
No. The FAQ says you must be a student or an open source beginner, aged 18 or over.
How many proposals can I submit?
Up to three, but only one can be accepted.
How many hours is a GSoC project?
About 90 (small), 175 (medium) or 350 (large), with timelines up to 22 weeks if agreed with your mentor.
Can I apply if I already contributed to open source?
Yes if you are still a beginner. Regular contributors to an open source project are not counted as beginners. A few merged pull requests while you prepare is expected and fine.
When should I start preparing?
Now. Organisations are published in February and proposals close in March, so contributions made in November to January are what mentors see when they rank you.
Is this the same as Google Solution Challenge or Google Girl Hackathon?
No. If your search was "Google Solution Challenge 2027", that is a different programme. GSoC is a mentored open source programme. The Google Solution Challenge is a team hackathon, and the Google Girl Hackathon is a hiring-linked coding challenge.
Final Thoughts
GSoC rewards steady, visible effort over a short sprint. Pick your stack in November, lurk in December, merge your first pull requests in January, talk to mentors in February, and submit a scoped, specific proposal in March. Then check the official timeline as soon as Google publishes it, because that is the only source that matters for dates.
Related reading: Hackathon calendar 2026-27 · How to win a hackathon · Google Solution Challenge 2027 · Google Girl Hackathon
Topics
Related on Thita
Your next step
Practise the rounds for Google Summer of Code
Most selection rounds open with a timed coding test. Work through the DSA patterns they draw on, run your code in the browser, then rehearse the interview out loud with an AI interviewer.