How to write a resume with no work experience: a student's guide

Writing a first resume feels impossible: you've got no job history, and every template seems built for someone with a career. But employers hiring students and freshers know that. They're not looking for years of experience. They're looking for evidence that you can learn, build things and finish them. Your resume's job is to show that on one page.

What a first resume is for

A resume doesn't get you a job. It gets you a conversation. A recruiter may spend under a minute on it, so it needs to answer three questions fast: what can you do, what have you done, and why should we talk to you?

The structure

For a student, one page is the norm. A clear order that works almost everywhere:

1. Header: your name, phone, email, and a link to your LinkedIn, GitHub or portfolio if you have a good one.
2. Summary (optional, two lines): who you are and what you're looking for.
3. Education: your course, institution, and expected graduation date. Add your marks or CGPA if they're strong.
4. Projects: the strongest section for most students (see below).
5. Experience: internships, part-time work, volunteering, club roles.
6. Skills: tools, languages and technologies you can actually use.
7. Achievements: competitions, scholarships, certifications that matter.

If you're early in your degree, lead with Education. If your projects are your best material, move Projects above Experience.

Turn projects and coursework into experience

Projects are how students show what they can do. For each one, write two or three lines that answer: what did you build, with what, and what happened?

• Weak: “Made a website for college fest.”
• Better: “Built a registration website for a college fest using React and Firebase; handled sign-ups for 400 participants.” (Use real numbers only.)
• Weak: “Worked on a machine learning project.”
• Better: “Trained a classifier on a public dataset of plant diseases and compared three models; the best reached 91% accuracy on a held-out test set.” (Again, only your own real results.)

The pattern is action verb + what you did + how + result. Start each line with a strong verb like built, designed, analysed, led, organised, wrote, improved, automated.

Describe achievements with numbers, where you have them

Numbers make claims concrete: how many people, how much time saved, how much improvement. If you don't have a number, describe the outcome plainly: what got finished, what changed, who used it. Never invent a figure; interviewers ask about them.

Skills: be honest and specific

• List tools and technologies you've actually used in a project or at work.
• Group them: Languages: Python, Java. Tools: Git, Excel. Soft skills only if you can back them with an example.
• Don't pad. “Proficient in everything” isn't a skill, and an interviewer will test the first one they see.

Formatting that gets read

• One page, with clear headings and consistent spacing.
• A plain, readable font at a normal size. Skip photos, icons, skill bars and multi-column layouts. Many companies use software that scans resumes, and simple formatting parses most reliably.
• Reverse chronological order within each section: most recent first.
• Save as PDF, named sensibly: YourName-Resume.pdf.
• Personal details: unless the employer asks for them, you don't need a photo, date of birth or other personal details.

Mistakes to avoid

• Typos. One is enough to lose a first impression. Read it aloud, and ask a friend to check it.
• Generic objectives. “Seeking a challenging position to utilise my skills” says nothing. Cut it or make it specific.
• Listing duties instead of results. “Responsible for social media” vs “Grew the club's Instagram following from 300 to 1,200 (example figures; use your own).”
• Exaggerating. Everything on your resume is fair game for interview questions. Only claim what you can explain.
• One resume for everything. Tweak the top third for each role: reorder projects and skills to match what the job asks for.

Using AI to help, without making things up

AI is useful for the stuck parts: turning rough notes into clear bullet points, suggesting stronger verbs, checking grammar, or tailoring your wording to a job description. It's not useful for inventing experience, and any draft is only as honest as the facts you give it.

Here are my notes about a project: [paste]. Rewrite them as three resume bullet points starting with strong verbs. Don't add any facts or numbers I haven't given you.

Learnsable's Career Advisor builds a resume and cover letter from your background, prepares interview questions and sketches a skill roadmap for a role. Edit everything in your own words, and make sure every line is true.

A simple template to copy

• Name · phone · email · LinkedIn/GitHub
• Education: B.Tech, [Branch], [College], expected [Year] · CGPA [x.x]
• Projects: [Project name]: one line on what it is; two bullets on what you did and the result
• Experience: [Role], [Organisation], [Dates]: two bullets with outcomes
• Skills: Languages · Tools · Frameworks
• Achievements: one line each, with the year