Internship Resume With No Experience: What Goes on It?

Nobody expects a second-year student to have work experience. That is the point of an internship. What the reader wants to know is simpler: can this student do the small, real tasks in this posting, and is there proof?

So an internship resume is not a job resume with an empty "Experience" section. It is a page of evidence. Your coursework, projects, hackathons, club roles and certificates are that evidence. The job is to pick the right pieces and describe them plainly.

The short answer

For a 1st to 3rd-year student in India, the page usually holds five things:

1. Education, with your CGPA and its scale, and your 12th and 10th scores.
2. Projects, two or three, each saying what you built and with what.
3. Skills, limited to what you can show or explain.
4. Positions of responsibility and activities, such as clubs, fests and hackathons, kept short.
5. Certifications, only the ones that back up a skill on the page.

Add a two-line objective at the top only if it says something specific, like the kind of internship and the months you are free. "Seeking a challenging role to grow my skills" tells the reader nothing, so leave it out.

What goes on the page, in order

Education first. At this stage it is your strongest and most checked section. Write the degree, branch, college, expected year and CGPA with its scale, for example "CGPA 8.12/10 (up to Semester 4)". Write the number exactly as your grade card shows it. Do not round 7.96 up to 8. Some colleges state this outright. The IIT Madras internship resume guidelines for 2025-26 prohibit rounding and say CGPAs are cross-checked with the academic section. Add 12th and 10th with board, year and percentage. The marks and CGPA guide covers the details.

Relevant coursework, briefly. One line of four to six courses that match the posting is enough. For a data internship, "DBMS, Probability and Statistics, Python Programming" helps. A list of every subject you have taken does not.

Projects next. This is where a student with no experience wins or loses. See the next section.

Skills after projects. Group them: languages, tools, and domain skills. Each skill should appear somewhere in your projects or activities too. A skill with no proof anywhere on the page is easy to question in an interview.

Activities and certifications last. They support the rest. They rarely carry the page on their own.

Turn coursework and projects into evidence

A good project entry answers four questions in one or two lines: what problem, what you did yourself, what tools, and what came out of it.

Label the type of project honestly. A lab or semester project is a course project. Work guided by a professor outside a course is a faculty project. Something you built on your own time is a personal project. Readers value all three, and a clear label saves you an awkward question later.

If you worked in a team, say which part was yours. "Built the login and payment screens" is stronger than "Developed an e-commerce app", because it is specific and you can defend it. Add a GitHub or report link where you can, and check it opens for someone who is not logged in to your account.

Only give a number if it is real and you can explain how you measured it. "Reduced load time by 40%" invites the question "measured how?". If the answer is "I guessed", drop the number.

Clubs, fests, hackathons and certificates

These are useful when they prove something the posting asks for. They are clutter when they are listed only because they exist.

• Hackathons. Name the event, the year, your role, and what your team built. "Participant" alone says little. "Built the backend API for a campus lost-and-found app in a 24-hour team hackathon" says a lot.
• Club and fest roles. Give the club, your position and one concrete thing you did, such as "Managed registrations for 3 workshops". Use real figures only.
• NPTEL and other online courses. Treat these as proof of a skill, not as a list to lengthen the page. An NPTEL certificate is awarded only after a proctored exam and weekly assignments, and it can be verified online (NPTEL). That makes it a reasonable way to show a subject your syllabus does not cover. Write the course, the year and the score shown on the certificate. Mark a course you are still doing as "ongoing". Skip certificates that have nothing to do with the internship.

Fit it on one page

For a student, one A4 page is the norm, and it is a helpful limit. It forces you to choose.

If you are over one page, cut in this order:

1. Remove the generic objective.
2. Trim coursework to the courses that match the posting.
3. Drop certificates that do not support a listed skill.
4. Shorten each activity to one line.
5. Keep the two or three strongest projects and drop the rest.

Do not solve it by shrinking the font or the margins until the text is hard to read. A crowded page is harder to skim than a shorter one.

If your college placement cell prescribes a format for on-campus internships, use that format there. Keep your own version for off-campus applications.

Tailor it to each posting

Whether the listing is on your campus portal or on an internship site such as Internshala or Unstop, read it the same way. Note three things: the tools it names, the tasks it describes, and any eligibility line, such as branch, year or availability.

Then change the page, not your facts:

• Move the most relevant project to the top of the Projects section.
• Reword the project line to use the posting's words for things you really did. If it says "REST APIs" and you built one, say "REST API".
• Reorder skills so the ones the posting names come first.
• Put your available months near the top if the posting states dates.

Save each version with a clear name, such as "Aanya-Sharma-DataIntern-CompanyName.pdf", so you know which one you sent. If a site also asks you to fill in a profile form, make sure the facts in the form match the file.

Illustrative example (fictional student). Aanya is a second-year B.Tech student applying for a data analysis internship.

Before:

Made a project on sales data using Python. Learnt many things.

After:

Sales dashboard (course project, Data Analysis Lab), 2026. Cleaned a 12,000-row public retail dataset in Python (pandas) and built 4 charts in Power BI showing monthly sales by region. Wrote the cleaning scripts myself. Code: github.com/aanya-s/sales-dashboard

The "after" line names the tools the posting asked for, says what she did herself, and gives a link the reader can check. It claims nothing she cannot explain.

A check before you apply

• CGPA written exactly as on the grade card, with "/10" and the semester it covers.
• Each project says what you did yourself, with tools and a link where possible.
• Every skill on the page has proof somewhere else on the page.
• Certificates support a listed skill, and ongoing ones are marked as ongoing.
• The page fits on one A4 page at a readable size.
• The project and skills order matches this posting.
• The file name tells you which posting it was for.
• Contact details are correct, unless your college's format says to leave them out.

If you want to see how software reads your file, Guul's resume checker explains each finding in plain words. The Guul builder can also tailor your resume to an internship description, uses A4 by default for India, and exports PDF or Word.

Start with education and your two best projects, then build out from there. A short, honest page that the reader can check will do more for you than a long one they have to question. For the rest of your fresher years, the BTech fresher resume guide picks up where this one ends.