Summer internships are won in winter

The summer run-up, month by month

• December–JanuaryReconnaissance. Shortlist two or three organisations or teams whose stack you already know, and start reading their code and their issue tracker.
• January–FebruaryContribute. Small pull requests, documentation fixes, a reproduced bug. The goal is that someone there recognises your handle before the form opens.
• February–MarchApplications and proposals. Draft with a mentor's input rather than in isolation — a proposal shaped by someone inside the project is a different document.
• April–MayResults and onboarding. Rejections arrive here too, which is why applying to a couple of parallel options matters more than perfecting one.
• June–SeptemberThe work itself, usually ten to twelve weeks, with a midpoint evaluation on most structured programmes.

Why the form is not where selection happens

Structured summer programmes ask organisations to rank applicants, and organisations rank people they have already interacted with above strangers with better-written proposals. This is not favouritism — a maintainer choosing who to spend three months mentoring is making a risk judgement, and a stranger is simply riskier than someone whose pull requests they have already reviewed.

The practical consequence is that the application window is a formality that confirms a decision the preceding two months made. If you are reading this in autumn, you are early, which is the only genuinely good position to be in.

How a 2nd-year competes against final-year applicants

Not on credentials, which they will lose. On specificity. A final-year student with a broad CV and a generic proposal is beatable by a 2nd-year who has read the codebase and can name the exact thing they want to improve and why it matters to that project.

Year of study is also less decisive than most students assume. Selection on the well-run programmes is based on contribution quality and proposal fit, and 2nd-year students from IITs, NITs and IIITs are selected every cycle. The disadvantage is real but it is a disadvantage of experience, not of eligibility — and experience is the one thing an early start actually buys.

What an unpaid summer training is worth

Less than the certificate implies. A programme that charges you a fee, assigns pre-recorded material, and issues a completion certificate produces a line on a CV that experienced reviewers have learned to skip, because thousands of identical lines arrive every year.

The distinction that matters is whether anyone depended on your output. Work that shipped, was reviewed by someone who cared whether it was correct, and remains in use, reads completely differently from work that was graded. If you are choosing between a paid role doing real work and an unpaid programme with a recognisable brand on the certificate, the paid real work is usually the better investment.

There is a simple test before you commit a summer to something. Ask what specifically you will have built by the end that did not exist before, and who will be using it. If the honest answer is a certificate and a set of exercises that thousands of other students completed identically, the programme is selling you reassurance rather than experience — and reassurance is the one thing that stops being useful the moment someone asks a follow-up question.

Programmes whose selection starts months early

See every curated opportunity →