Job search
Outreachy Application Guide: Eligibility, Contribution Period, and Paid Internship Commitments
A current cohort audit and original contribution journal distinguish application approval, public work, final submission, selection and the paid internship.
An Outreachy contribution period is a selection stage, not an invitation for anyone to enter that round late or a promise of paid work. Check your initial-application status, the exact cohort calendar and the full internship commitment before planning contributions. The USD 7,000 figure describes the selected internship. It is not a payment commitment to everyone who spends time applying or contributing during selection.
On October 20, 2026, Outreachy's public project page said initial applications for the December 2026 cohort were closed. It still displayed a contribution period and final-application deadline for that round. We inspected the public guides and rendered project page without logging in, submitting an application, contacting mentors or contributing to a repository.

Keep recent roles on LandOffer.ai alongside a program investigation if you also need employment options. A stipend-funded open-source internship serves a different purpose from an employer vacancy, and the time available to pursue either may be limited.
Identify the cohort and your application state first
Outreachy's program overview describes remote, three-month open-source internships with a USD 7,000 total stipend. Projects can involve programming and other disciplines. It also states that internships are not linked to employment opportunities at supporting organizations. A sponsor logo therefore does not supply a future job offer.
The broad homepage used approximate end-of-year dates during our check. For the current round, the project-selection page supplied specific dates and a prominent closed-initial-applications notice. The rendered cohort page and its specific deadline table supplied the calendar used below. The homepage's approximate dates did not override that record.
That distinction matters before you choose a project. Someone who missed the initial deadline is in a different position from an applicant already approved to contribute. A public project title or an upcoming final deadline does not remove an earlier admission gate. Check the appropriate account status yourself through the official route; we did not inspect anyone's private application.
There is still useful preparation for a future round: learn the project's tools, understand its contribution instructions and assess your time realistically. Keep ordinary public volunteering separate from an Outreachy application. Do not describe voluntary work as an internship or assume it reserves a later selection place.
Worked calendar audit: what October 20 actually permits
We completed this public calendar audit against the December 2026–March 2027 project page. It records program stages, not an individual eligibility ruling. Times are UTC as published; convert them to your local clock before relying on an application cutoff.
| Published stage | Dated public record | Completed interpretation on October 20 |
|---|---|---|
| Initial application | August 24–31, 2026; deadline 4 p.m. UTC | Closed; a new reader cannot assume the later final deadline allows an initial application |
| Initial results | October 12, 2026, 4 p.m. UTC | A private result must establish the applicant's own state; this review did not check one |
| Contributions and final application | October 12–November 9; final cutoff November 9 at 4 p.m. UTC | The contribution window is underway; participation still depends on the earlier approval |
| Intern selection announcement | November 30, 2026, 4 p.m. UTC | A contribution or final application is earlier than an acceptance announcement |
| Internship period | December 7, 2026–March 8, 2027 | Plan the whole period, subject to current program rules and any individually approved arrangement |
For a first-time visitor with no approved initial application, the next step is preparation for a future intake. November 9 is not a fresh initial-application deadline. An already approved applicant should verify their own project instructions and remaining submission steps. Neither can count acceptance merely because the calendar still contains future dates.
The same public page listed project titles and skill fields while marking fuller descriptions hidden in the signed-out view. We did not bypass that access boundary, inspect a private mentor task or establish a complete project scope from a visible skill label. “Python” or “Git” is too broad to tell you what a specific project expects.
Eligibility is more than being interested in open source
The eligibility page describes Outreachy's mission around underrepresentation, systemic bias and discrimination in the technology industry where an applicant lives. It does not offer a fixed exhaustive list of eligible identities. We make no judgment about a reader's background or personal experience; organizers review the application.
For this dated round, the rules require age 18 by the start, availability for 30 hours weekly, and no previous Outreachy, Outreach Program for Women or Google Summer of Code internship. They exclude another concurrent internship, including an unpaid one, and full-time employment or contracting during Outreachy; leave from a full-time job is also excluded. Part-time work needs organizer approval.
Student rules add a 42-consecutive-day academic break and hemisphere-based cohort restrictions; individual course load or arranging a term off does not replace the institutional calendar. Read the complete current rules, including authorization conditions, instead of using this abbreviated summary as an admissions decision. Dates and circumstances need to be evaluated together.
Put the relevant facts in a private preparation record before applying: institutional calendars, current work commitments and the period you can protect. Do not publish identity documents, immigration records or personal discrimination narratives in a public issue tracker to prove eligibility. The appropriate application channel and public project discussion have different purposes.
If a rule conflicts with your current arrangements, keep that conflict visible. An optimistic calendar is not evidence of approval. A prospective applicant also should not give up employment because a review describes a possible internship; a personal decision needs the actual selection result, terms and practical circumstances.
Contributions, records and the final application are separate work
The application overview describes choosing one or two projects, making contributions, recording them and submitting a final application for each project pursued. Its instructions require at least one recorded contribution before the final-application option appears. A contribution can be recorded before it is merged or accepted.
That last distinction is useful: record the work's actual state. A proposed change, a review request, a revision and a merged change tell different stories. A concise record should explain the problem, your contribution and what remains unresolved. Counting links alone tells a mentor little about whether you understand the work.
The published process favors steady, meaningful interaction over a large last-minute submission. That does not mean sending repeated messages or expanding scope without agreement. Read the project's contribution guide, keep questions specific and make the next reviewable change small enough to explain. We did not test mentor responsiveness or review speed.
Reserve time for submission work as well as technical changes. Keep a short remaining-steps list beside your contribution notes, so a finished patch does not obscure an unfinished application. A person may finish a patch but forget its record or the final application. Conversely, a polished final form cannot replace the required contribution. Preserve a clear distinction between work done locally, work shared publicly and work entered into the official application system.
Worked contribution journal: honest states beat an inflated count
Consider fictional Ari, who already has initial approval for an illustrative round. Ari chooses one documentation-oriented project and keeps the following private preparation journal. These entries are invented examples of recording work state, not real Outreachy contributions, mentor messages or an application to a named project. They provide no personal eligibility claim or initial-application essay.
| Illustrative record | Work Ari can describe | State recorded and completed next action |
|---|---|---|
| Environment setup | Followed the documented setup, noted dependency versions and reproduced the local documentation build | Local preparation only; not counted as an accepted contribution |
| Broken example investigation | Isolated a sample command that fails with a missing option and saved the error plus environment | Reproduction note prepared; check existing issues before reporting a duplicate |
| Proposed documentation correction | Drafted a small wording change explaining the required option and tested the documented command locally | Proposed change, not merged; preserve the exact tested version and limitations |
| Review follow-up | Revised an explanation after an illustrative reviewer question about supported versions | Revision state; do not describe feedback as approval or the change as selected internship work |
| Application administration | Recorded the contribution's actual state and reserved time for a project-specific final application | Separate submission task remains; a journal alone is not an official final application |
Ari's completed summary is: “One bounded documentation correction is proposed; its reproduction and local verification are documented. Review and selection remain unresolved.” The five rows describe preparation, investigation, a proposed change, revision and administration around one piece of work. Ari therefore does not report them as five accepted contributions.
The journal also supplies a stopping rule. Ari does not start a second unrelated project merely to increase the count when the first correction still needs an explanation they can defend. If a reviewer asks about a version Ari has not tested, the record says untested. Ari keeps the failing command, dependency versions and local result together, rather than describing a successful build on one setup as a cross-platform test. It does not invent compatibility across every supported environment.
Nothing in this example creates a submission to copy into a live project. The actual issue, contribution format, testing expectations and AI policy must come from that community. Its value is the separation of evidence states: what was reproduced, what was changed, what was checked and what another person has actually accepted.

Protect authorship and follow the project's AI policy
The applicant guide prohibits generative AI from creating or editing initial-application essays. It explains that those accounts should reflect the applicant's own lived experience. Do not use a generated personal story or polish those essays through an AI tool. This guide is general program research and supplies no essay answer.
Project contributions have a separate boundary. The guides say mentors set project-specific AI rules, with discussion required before uncertain uses. Applicants need to understand, verify and disclose permitted generated work; unedited material they cannot explain or correct can prevent selection. Check the actual policy rather than transfer permission from another repository.
For an applicant, the practical test is whether you can explain your own contribution without relying on a tool's confident wording. Identify the behavior you changed, the evidence supporting it and a case you have not tested. A mentor reviewing a small accurate change can assess those statements; a large unexplained patch creates more uncertainty.
Budget the internship commitment separately from application time
The internship guide expects 30 weekly project hours for at least 12 weeks of a 13-week period, with approved extensions under specified conditions. Do not treat an extension as permission to stop and restart at will or shorten the program. Keep foreseeable commitments and any approved changes with the actual agreement.
Its current payment section divides the USD 7,000 stipend into USD 3,000 and USD 4,000 installments, conditioned on successful mentor feedback and payment paperwork. For this round it lists January 20 and March 2, 2027, as issue dates. An issue date is separate from receipt in a bank account. These dates do not establish payment at application or on the internship's first day, and missing paperwork or unsuccessful feedback can affect the stated arrangement. We did not test payments or determine anyone's tax treatment.
For a simple planning exercise, twelve weeks at thirty hours is 360 project hours. That arithmetic does not turn the stipend into an employment wage or include the work of applying. A time plan also needs communication, review and documentation within the program's expectations; do not spend every available hour on new code while leaving no time to respond to feedback.
An internship can produce learning and collaboration evidence without a job at the sponsor. Preserve that distinction when evaluating other opportunities through LandOffer.ai or direct employers. Check the current cohort, make an honest application-state record and pursue only the next step your actual status supports.


