Early internships go to students who can show one or two working projects, apply before the summer season opens and reach out directly. Target startups, smaller companies, university programmes and open source programmes rather than only big names, and treat a first internship as practice, not a verdict on your future.
What people tell me
I am in my first or second year of a computer science degree. Most internship listings seem to want final-year students, and I only know one programming language and what we covered in class. Seniors tell me to wait until third year, but I see classmates already getting internships. I do not know where to look, what to put on my resume or whether anyone will take someone this early.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- You compete on evidence, not year of study. One or two working projects put you ahead of most early applicants.
- Apply early. Many summer internship programmes open applications months before summer starts.
- Startups, small companies, labs and open source programmes are more open to early students.
- Direct messages to founders and engineers often work better than listings at this stage.
- A first internship at a small place is a win. It makes the next one much easier.
Why early internships are possible
Companies do not hire interns for what they already know. They hire for signs that you can learn fast and finish things. A first or second-year student with a small working project, a clean GitHub and a sensible message often beats a final-year student with nothing outside class.
You will not get every internship. You do not need to. You need one.
Where early students actually get in
| Option | Why it works early | How to find it |
|---|---|---|
| Startups and small product companies | Less formal hiring, need extra hands | Company pages, founders on LinkedIn, local tech communities |
| University labs and professors | Research or tooling help, often flexible | Ask professors whose courses you did well in |
| Open source programmes | Judge your contributions, not your year | Google Summer of Code, MLH Fellowship, Outreachy |
| Company internship programmes | Some reserve places for early years | Sefism internships and company careers pages |
| Small freelance or local business work | Real users and real deadlines | People you know, local shops, student societies |
In Pakistan and many other countries, a lot of companies run summer internship programmes around June to August, and applications often open in spring. Some close before exams end. Put the dates on your calendar at the start of the spring semester, not when summer begins.
What you need before applying
You do not need a long list. You need:
- One or two small, working projects. Deployed or runnable, with a README that explains what it does and how to run it.
- A one-page resume. Education, projects (with what you built and what you learned), skills you actually used, any society or hackathon work.
- A GitHub profile that is not empty. Pin your best two repositories. The GitHub profile README guide takes an evening.
- A short message you can adapt. See below.
A message that works
Hi, I am a second-year CS student. I built a small expense tracker with Python and a simple web interface (link). I am looking for a summer internship where I can learn from real code, and I am happy to start with testing, bug fixes or small features. Do you have space for an intern this summer, or could you point me to the right person?
Short, specific, with a link. Send it to founders and engineers at small companies, not only HR inboxes.
A 6-week plan leading into internship season
| Week | Focus | Output |
|---|---|---|
| 1 | Pick and scope one project | A clear idea you can finish in 3 weeks |
| 2 | Build the core | The main feature works |
| 3 | Finish and polish | README, screenshots, deployed or easy to run |
| 4 | Resume and GitHub | One-page resume, pinned repositories, LinkedIn updated |
| 5 | Apply and reach out | 15 applications, 15 direct messages |
| 6 | Follow up and keep building | Follow-ups sent, start the second project |
If you have more time before the season, add a second project or a few small open source contributions.
Interviews for early interns
Expect simpler rounds: basic programming questions, a walk-through of your project, maybe a small take-home task. Prepare by:
- Explaining your project out loud in two minutes: what, why, how, what you would improve.
- Practising basic problems on arrays, strings and loops.
- Being honest about what you do not know and how you would find out.
"I have not used that yet, but in my project I learned X by reading the docs and trying small examples" is a good answer.
If you get nothing this year
It happens, and it is not a sign you are behind. Use the summer to build, join a hackathon or contribute to open source, then apply earlier and with stronger projects next year. What should I do in the summer after first year? has a plan for exactly that case.
How to build a target list
Do not apply randomly. Spend one evening building a list of 30 places:
- Ten small product companies or startups in your city or working remotely in your region. The companies page is a starting point.
- Ten companies with formal internship programmes, with their usual application months noted.
- Five professors, labs or university departments.
- Five open source projects or programmes you could contribute to.
Put them in a spreadsheet with columns for contact, date sent, reply and next step. Follow up once after a week if you hear nothing. A single polite follow-up often gets the reply the first message did not.
Common mistakes
- Waiting until final year because seniors said so.
- Applying only to the three most famous companies.
- Resumes that list twenty technologies from course names.
- Messages that ask "any opportunity?" with no link or context.
- Turning down unpaid or low-paid short internships at good small teams without thinking about what you will learn.
If you are still stuck
Read Everyone around me has internships and projects and I have almost nothing. The University to job-ready roadmap lays out what to build each year. To get specific help with your resume or target list, join Sefism, it is free to learn and you start with credits, then ask your own question.
Was this answer helpful?
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open: sign up and your account is active shortly after. Prefer to talk? A free call works too.