You are hiring one Open Source intern. The gap between a listing that fills in a week and one that sits open for two months is almost never the stipend — it is whether the brief names the actual open source work.
Open Source Intern is a well-defined brief, which helps at screening time: the skills below are specific enough that twenty minutes of questions will separate someone who has done the work from someone who has read about it.
Worth separating from Open Source Internship: same skills, different commitment. Open Source Intern is a hire you scope around one deliverable, whereas open source internship is framed as a programme with a mentor and a fixed duration. Pick the framing that matches what you can actually offer, because candidates read the difference.
What follows is the brief we would write if we were hiring this role ourselves — skills, deliverables, stipend band, screening questions, and the mistakes that cost people the good candidates.
What one Open Source intern actually does in the first 90 days
Read these as candidates will: as evidence that somebody has thought about what the term is for. A listing without one of them reads as headcount rather than a job.
- Land one merged pull request in a project the company depends on
- Write the contributing guide for our own public repository
- Triage the open issue backlog and close what is stale
Open Source skills worth screening for
Treat this as a screening list, not a wish list. Someone with three of these deeply is a better intern than someone with all eight superficially.
- 1Reading a large unfamiliar codebase
- 2Issue triage and reproduction
- 3Contribution guidelines and PR etiquette
- 4Writing documentation for strangers
- 5Licence awareness
- 6Semantic versioning
- 7Community communication
A candidate who can walk you through one Open Source problem they solved — including what they tried that did not work — is worth more than a résumé carrying every tool on it.
Screening questions for open source intern
Ask the same ones of everybody. The point is comparison, and comparison needs a constant.
Show me a pull request you had reviewed by a stranger.
What a good answer shows: Real collaborative experience
How do you check a dependency licence is safe to use?
What a good answer shows: Commercial awareness
Leave silence after the follow-up. The most useful part of these answers usually arrives after the candidate thinks they have finished.
Where the Open Source candidates come from
The registered pool spans India’s premium institutes — IIT, IIM, BITS, NIT, Symbiosis — and the strong regional colleges that produce most of the country’s working engineers and analysts. Employers are verified before publishing, so candidates treat these listings as real.
- Skill tags — filter directly on Git and GitHub, Issue trackers, Markdown and the rest of the Open Source stack
- Graduation year and current semester, so you only see candidates free when you need them
- City and willingness to relocate, or remote-only if the role is remote
- Degree and branch, for the roles where the coursework genuinely matters
- Portfolio and project evidence attached to the profile, rather than a résumé alone
Rather than filtering manually, describe the Open Source role in one sentence and let the matcher rank the pool: it maps your requirement to real skill tags and project evidence.
What to pay one Open Source intern in 2026
Expect ₹12,000–₹30,000 a month. Metro product companies sit at the top of that band; smaller cities and services firms at the bottom.
Six-month commitments generally command more per month than six-week ones, because the candidate is giving up other options. Price the commitment, not just the hours.
Listings that state a stipend get noticeably more qualified applications than "as per industry standards", which candidates read as low or undecided.
Bengaluru, Hyderabad, Pune, Mumbai, Gurugram and Noida sit at the top of the band. Tier-2 cities typically run 25–40% lower for the same skills and the same output.
The saving is a few thousand rupees; the cost is a candidate who starts feeling undervalued and treats the term as temporary. Decide the number, publish it, honour it.
Scoping a single Open Source intern properly
One intern, one owner, one project that matters. Single hires fail for a boring reason: the work was never scoped, so the intern spent the term on whatever was in front of whoever was free that day.
Pick one item from the Open Source list above and make it the term’s goal. If nobody can name the deliverable, the role is not ready to post.
One person who reviews the work weekly and answers questions daily. Shared ownership at this level means nobody owns it.
Access, environment, a first small task and a person to sit with. The first week decides whether you get twelve productive weeks or eight.
A halfway review lets you change scope while it still matters and gives feedback while the intern can still act on it.
How to post open source intern on MyInternships.in
You do not need a prepared job description. Answer a few questions in the chat and the assistant drafts the listing, title and skill tags for you.
Describe the role the way you would to a colleague: what the open source work is, how long for, and what you can pay. The assistant asks the rest.
It drafts the description, suggests the title and tags the Open Source skills so the right candidates see it. You edit anything before it publishes.
One-time company verification protects the pool from fake listings, which is why response rates here hold up on roles that would be ignored elsewhere.
First applications typically land the same day. Contact details and résumés are available on any paid plan; the free plan shows you the applications.
Free plan: one listing, live after verification. Starter ₹499: five listings a month, published instantly, full applicant contact and résumé access. Growth ₹999: fifteen listings with AI candidate matching.
Mistakes that cost you the good Open Source candidates
Four failures we see repeatedly on this kind of role, in rough order of what they cost.
A Open Source listing with fourteen required tools reads as a company that does not know what it needs. Strong candidates self-select out; the ones who apply anyway have inflated their CVs to match.
Campus communities are small and they talk. A two-line rejection costs you nothing now and protects your applications next intake.
If nobody can name the problem this intern solves, the term will be filled with whatever is urgent that week, and the assessment at the end will be about attitude rather than output.
Definition questions test revision, not ability. Ask about something they built and follow their answer — the depth appears within two follow-ups.
Open Source Intern — frequently asked questions
How much Open Source experience should we expect?+
None professionally, and that is the point. What you should expect is evidence: something built, run or fixed involving Git and GitHub or Issue trackers, that they can talk about in depth. Screen on reading a large unfamiliar codebase and issue triage and reproduction; treat everything else on the list as trainable during the term.
What can open source intern realistically deliver?+
Land one merged pull request in a project the company depends on. That is sized for eight to twelve weeks of supervised work by someone with the fundamentals and no production experience. A second, smaller piece — write the contributing guide for our own public repository — usually fits alongside it. Anything requiring independent production judgement should stay with the reviewer.
Is ₹12,000 a month enough for open source intern?+
It is the bottom of the working band, and appropriate for a smaller city or a shorter commitment. In Bengaluru, Hyderabad, Pune, Mumbai or the NCR, expect to be closer to ₹30,000 for the same skills — you are competing with every other employer for the same few candidates. Decide where in the ₹12,000–₹30,000 band you sit before the first interview rather than during the offer call.
Can we screen open source intern without a technical interviewer?+
For a first pass, yes. Ask "Show me a pull request you had reviewed by a stranger." and judge whether the answer is specific and consistent — you are checking for real collaborative experience, which does not require you to know the subject. A Open Source practitioner should still take the second round, because at that point you are assessing depth rather than authenticity.
What should a Open Source intern deliver by the end of the term?+
One finished, reviewed piece of work that someone on the team would otherwise have done — not a side project nobody adopts. The deliverables above are sized for eight to twelve weeks of supervised work by a student with the fundamentals but no production experience. If they can demo it and the team keeps using it after they leave, the hire paid for itself.
Should the listing state the duration and start date?+
Always. Students plan around semester dates, and a listing without a start date and duration is filtered out by exactly the organised candidates you want. For Open Source roles, stating "three months, starting June" typically produces more applications than an open-ended listing at a higher stipend.
Can we hire open source intern remotely, or in a specific city?+
Both. The pool covers every major hiring city and hundreds of tier-2 and tier-3 towns, and the role can be posted as remote, hybrid or on-site. For Open Source work specifically, remote widens the pool considerably — filter on skill and availability rather than pin code unless the work genuinely requires presence.
Can we convert open source intern into a full-time hire?+
Yes, and it is usually the cheapest senior-quality hire available to you: no agency fee, no technical ramp on your stack, and an assessment based on months of work rather than two interviews. Say so in the listing if conversion is genuinely possible — it widens the applicant pool measurably and costs nothing.
Related roles employers hire alongside open source intern
Tools and pages for your hiring
Hire open source intern — post in about two minutes
Answer a few questions and our AI writes the description, suggests the title and tags the Open Source skills. Your company is verified, the listing goes live, and applications start arriving.