A first resume has one job: convince a stranger that you can do useful work and are worth fifteen minutes of conversation.
That is a lower bar than most students think, and a higher one than most resumes clear. The problem is rarely a lack of content. It is that the content is arranged to describe a syllabus rather than a person.
Start with the structure
One page. Four sections, in this order: contact, education, projects, skills. Add experience only if you have something real to put there.
| Section | What belongs there |
|---|---|
| Contact | Name, one professional email, phone, GitHub, portfolio or LinkedIn |
| Education | Degree, institution, expected graduation, relevant coursework or CGPA if strong |
| Projects | Two or three projects with a problem, an action and a result |
| Skills | Languages, frameworks, tools — only what you can discuss |
No objective statement. No photograph. No date of birth. No declaration. These take space and tell a reviewer nothing they need.
Write project bullets that survive a follow-up question
The formula is simple: what you built, for whom, with what, and what changed.
A weak bullet:
Made a web application using React and Node.js.
A stronger bullet:
Built a hostel mess feedback app (React, Express, SQLite) used by 60 students to submit and track complaints; added an admin queue that cut duplicate reports.
The second version gives the reviewer three things to ask about. That is the point. If you cannot answer questions about a bullet, remove it.
Choose projects you can defend
Two solid projects beat six tutorial clones. Solid means: you can explain the data model, the hard bug you fixed, and what you would change next.
Project types that read well for a first internship:
- A small tool that solves a problem in your own college or hostel.
- A clone of a simple product, with one feature you added yourself.
- A data or automation script that saves someone real time.
- An open-source contribution with a merged pull request you can link to.
Include the repository link, a live link if it exists, and a two-line README explaining how to run it. A reviewer who cannot start your project in five minutes will not try.
Format for the reader, not for the template
- Use a single-column layout. Two-column resumes confuse parsers and human eyes.
- Use a common, readable font at 10–11pt. Save as PDF unless the listing asks otherwise.
- Keep headings bold and consistent. Do not use tables, text boxes or icons to carry meaning.
- Spell out acronyms once. Write “Amazon Web Services (AWS)” the first time.
- Keep the file name boring:
Firstname_Lastname_Resume.pdf.
Tailor without lying
Read the listing and underline every requirement. For each one, find the closest truthful evidence you have and put that evidence earlier in the resume. If there is no evidence, you have two honest options: learn enough to build some, or accept that this role is a stretch.
Reordering true content is tailoring. Adding skills you cannot discuss is not.
The mistakes that show up again and again
- Listing every language you have ever opened, at “intermediate” level.
- Describing responsibilities instead of outcomes.
- Sending the same generic file to every organisation.
- Using a 12-page “portfolio” when a one-page resume and three links would do.
- Ignoring the email address on the listing and writing to a random employee.
- Forgetting that the GitHub link on the resume is part of the application.
A checklist before you send
- [ ] One page, single column, PDF.
- [ ] Email and phone are correct and checked.
- [ ] Every project link opens without a login.
- [ ] No bullet is longer than two lines.
- [ ] Every number in the resume is one you can defend.
- [ ] The role title in your objective — if you kept one — matches the listing.
- [ ] Someone else has read it aloud and found no typos.
The short version
A student resume works when it is short, specific and checkable. Put your strongest evidence first, describe what changed because of your work, and remove anything you would not want to be asked about in an interview.