# How to write a resume with no experience

> A step-by-step guide for students and freshers: what to put on a one-page resume, how to describe projects, and bullet examples you can adapt.

Canonical: https://hiremast.in/blog/resume-with-no-experience
Last updated: 2026-11-06

Every job post seems to ask for experience, and you can't get experience without a job. The good news is that recruiters hiring freshers know this. They aren't looking for years at a company. They're looking for **evidence that you can do the work**: things you built, problems you solved, and skills you can explain. This guide shows you how to put that evidence on one page.

## You have more experience than you think

“Experience” on a fresher's resume means anything where you did real work and can show what happened. That includes:

- Projects: course projects, your final-year project, personal projects, hackathon entries.
- Internships, including short, unpaid or remote ones.
- Freelance or part-time work, even a single paid job for a local business.
- Roles in college clubs, fests, technical societies or sports teams.
- Teaching or mentoring: tutoring, being a teaching assistant, running a workshop.
- Open-source contributions, competitive programming, research with a professor.

The skill is in describing these the way a recruiter thinks: what was the problem, what did you do, and what was the result.

## The one-page structure that works

For a fresher, this order puts your strongest evidence where recruiters look first:

1. **Header:** name and contact details.
2. **Summary** (optional): two sentences, no clichés.
3. **Education:** first, because it's your most recent and relevant credential.
4. **Projects:** your main section. Two to four projects.
5. **Experience:** internships, freelance work, part-time jobs.
6. **Skills:** grouped and specific.
7. **Achievements:** hackathons, ranks, scholarships, leadership roles.

If an internship is more relevant than your projects, put Experience before Projects. Use one column, clear headings and a normal font. Fancy multi-column templates can confuse some applicant tracking systems and make the page harder to skim. See [how ATS software actually works](https://hiremast.in/blog/how-ats-software-works) for why.

## The header: what to include and what to leave out

| Include | Leave out |
| --- | --- |
| Full name | Photo, unless the employer or country asks for one |
| Phone number and a professional email | Date of birth, age, gender, marital status |
| City (not your full address) | Father's name, religion, caste, nationality |
| LinkedIn, GitHub or portfolio links that work | A "Declaration" and signature at the bottom |

Personal details were common on older Indian resumes, but most private-sector employers don't need them, and leaving them out frees space and avoids bias. Follow the employer's instructions if a government job or an overseas application asks for something specific.

## Education, CGPA and coursework

Write your degree, college, years and score. Keep school marks only if a company asks for them, or if they're strong and you have little else.

- **CGPA:** include it, especially for campus placements, where companies often use cutoffs. Write it the way your college reports it, such as `7.8/10`.
- **Coursework:** list three to five courses only if they match the job, such as Operating Systems and DBMS for a backend role.
- **Final-year project:** move it to Projects, where you have room to explain it.

## Projects: the most important section

For most freshers, projects decide whether you get an interview. Pick two to four that are **relevant to the job** and**finished**. For each one, write a title line with the tools you used and a link, then two or three bullets:

1. What you built and why it was needed.
2. The hardest technical part and how you handled it.
3. The result: who used it, how fast it is, what it improved.

- Before: Made an e-commerce website using React and Node.js.
- After: Built a store for a local bakery with React and Node.js, with online orders and UPI payments; it took 140 orders in its first month.
- Why: The rewrite says who it was for, what it does and what happened. Every part of it is checkable.

Add a link to the code or a live demo wherever you can. A recruiter who opens your GitHub and finds a clear README, sensible commits and a working deploy learns more than any bullet can say.

## Writing bullets with results, without a job

Strong bullets follow a simple pattern: **action verb + what you did + how + result**. You don't need business revenue to have results. Use the numbers you actually have:

- People: users, members, attendees, students taught.
- Scale: rows of data, requests per second, pages, files processed.
- Speed: load time, response time, time saved per task.
- Quality: model accuracy, bugs fixed, test coverage.
- Rank or selection: hackathon placing, out of how many teams.

- Before: Worked on a machine learning project for predicting crop prices.
- After: Trained a gradient-boosting model on 6 years of mandi price data to predict weekly onion prices, cutting error by 23% against a moving-average baseline.

> **Never invent a number**
>
> If you don't know a figure, leave it out, or measure it now. Interviewers ask about every number on a fresher's resume, and a number you can't explain does more damage than no number at all.

## Internships, clubs and everything else

Describe an internship like a job: your role, the team, what you shipped and what changed because of it. For other activities, focus on responsibility and results:

- Before: Member of the technical club.
- After: Led a team of 6 to run the college's 24-hour hackathon for 300 participants; built the registration site and handled judging logistics.

Short or unpaid work counts. Write the real dates and the real scope, and let the work speak for itself. Don't stretch a two-week internship into a role it wasn't.

## Skills you can defend in an interview

Group skills so a recruiter can scan them in seconds:

- **Languages:** Python, Java, SQL
- **Frameworks:** React, Spring Boot
- **Tools:** Git, Docker, PostgreSQL, AWS (EC2, S3)

Only list a skill if you can answer basic questions about it and point to where you used it. Skip rating bars and percentages, which mean nothing to a recruiter, and drop basics like “MS Word” for technical roles.

## Tailor it to each job

One generic resume sent to fifty companies does worse than ten resumes adjusted to ten jobs. Read the job post, note the skills and tools it repeats, and make sure the projects and bullets that prove those skills come first, using the same words the post uses**wherever they truthfully describe your work**. If the post says “REST APIs” and you built one, say “REST API”, not just “backend”.

Never add a skill you don't have just because the post mentions it. If something important is missing, that's a signal to build it, not to claim it.

## Mistakes that cost freshers interviews

- Two or three pages, padded with school details and hobbies.
- A generic objective: “Seeking a challenging role in a reputed organisation”.
- Listing technologies without showing where you used them.
- Broken GitHub links, or links to empty repositories.
- Typos and inconsistent dates or formatting.
- Graphics-heavy templates, tables and text in images.
- An email address like `coolguy99@...`.
- Claims you can't explain in an interview.

## A final checklist

- It fits on one page, in one column, with clear headings.
- Your contact details are correct and every link opens.
- Your strongest, most relevant project is near the top.
- Every bullet starts with an action and ends with a result you can explain.
- Every skill appears somewhere in your projects or experience.
- The words match the job post, where they're true for you.
- A friend has read it for typos.
- It's saved as a text-based PDF, named like Firstname-Lastname-Resume.pdf.

## Frequently asked questions

### Should I put my CGPA on my resume?

Usually yes, especially for campus placements, where many companies screen by a CGPA cutoff and a missing CGPA can look like you're hiding it. Write it exactly as your college reports it, for example 7.8/10. Once you have a year or two of work experience, it matters much less.

### Is a one-page resume enough for a fresher?

Yes. With no full-time experience, one page is almost always right. Recruiters skim the first screen in seconds, so a tight page with your best two or three projects beats two pages of padding.

### Can I list online courses and certificates?

List the ones that relate to the job, in a short Certifications line, with the provider and year. They help most when they back up a skill you also show in a project. A long list of unrelated certificates adds little.

### What if I have no projects at all?

Build one small, complete project in a few weekends that solves a real problem, and write it up well. Until then, use coursework assignments, a final-year project, hackathon entries, or a tool you built for a club or a family business. Something small that works and is explained clearly beats an unfinished big idea.

### Should I write a career objective?

Skip the generic objective. If you want a line at the top, write a two-sentence summary that says what you do and what role you want, with one specific fact, such as: Final-year CSE student who builds backend services in Go; built a payments simulator handling 1,000 requests a second.

## Related

- [How ATS software actually works (and what it means for your resume)](https://hiremast.in/blog/how-ats-software-works)