"No experience" almost never means no evidence. A hiring manager reading a fresher's résumé is asking one question: can this person learn the job quickly and do it reliably? Your résumé's task is to give them proof, using what you have actually done.
Start with the structure
For a first résumé, one page is the right length. Use this order:
- Name and contact details
- A two-line summary
- Projects
- Education
- Skills
- Internships, certifications, activities (as relevant)
Put Projects above Education if the role is technical or practical and your projects are strong. Put Education first if you studied something directly tied to the role and have little else.
The summary: two lines, specific
Skip "Seeking a challenging position in a reputed organisation." Say who you are and what you offer.
- Example: "Final-year computer science student with two full-stack projects and a summer internship in QA testing. Looking for a junior software role working on web applications."
It tells the reader your level, your evidence and your target in one breath.
Projects: your main evidence
A project shows that you can finish something. Aim for two or three good ones rather than eight weak ones. For each, write two or three bullets covering:
- What it does and who it is for
- What you built and how: tools, languages, key decisions
- A result or a detail that shows depth: users, accuracy, speed, a problem you solved
Example:
- Built a campus event-listing web app with React and Node.js, used by 150+ students in two semesters.
- Added search and category filters, cutting the time to find an event from scrolling a chat group to under ten seconds.
- Deployed on a free cloud tier with automatic backups; code and demo linked below.
Always add a link to the code repository or a live demo. A recruiter who can click and see your work trusts it more than a description.
If you are not in tech, the same logic applies. A marketing student can show a campaign plan or a social page they grew. A commerce student can show a financial model or a case competition. A design student can show a small portfolio.
Education: keep it short
Include your degree, college, year of graduation and score if it is strong. Add relevant coursework only if it relates to the role. Honours, rankings and scholarships go here too.
Skills: only what you can discuss
List tools and languages you could talk about for five minutes in an interview. Group them, for example "Languages: Python, JavaScript. Tools: Git, Figma, Excel." Do not use rating bars, and do not list skills you only watched a video about. If it is on your résumé, you may be asked about it.
Turning non-work activities into evidence
You may have more experience than you think. These all count when written well:
- Internships and training, even short or unpaid
- Hackathons and competitions: name the event, what you built, any placement
- Club or society roles: "Organised a two-day workshop for 120 attendees" shows planning and teamwork
- Open-source or freelance work: even small contributions
- Part-time jobs: customer-facing work shows communication and reliability
- Certifications: useful when they are relevant and recent, but weaker than real projects
Describe each with an action verb and an outcome, as you did for projects.
Mistakes freshers often make
- Listing duties instead of results. "Helped with marketing" says nothing. "Wrote 12 blog posts that brought in 900 visits in a month" says a lot.
- Padding. A long résumé with filler is worse than a short one with substance.
- Typos and inconsistent formatting. For a fresher these suggest carelessness, so read it aloud and ask a friend to check it.
- A casual email address. Use a simple one based on your name.
- Sending the same résumé everywhere. Adjust the top third for each role. Move the most relevant project up and mirror the posting's key terms where they are true.
Before you send
- Is it one page?
- Does each project have a link?
- Does every bullet say what you did and what happened?
- Does it read cleanly when pasted into a plain text editor? (See our guide to ATS-friendly résumés.)
- Have two other people read it?
You are closer than you think
Employers hiring freshers do not expect a long history. They expect potential, shown through effort and a few real things you built or ran. Pick your two best pieces of evidence, present them clearly, and apply. Then improve the résumé with each response you get.
