Fresher resume format for early-career applications

Who this is for

You’re finishing college, in a graduate program, or applying to first roles with internships and projects, not a long full-time history. Recruiters skim fast. Your job is a clear one-page story, not a biography.

Keep it to one page

One page is the default for freshers. Two pages only make sense if you’ve already got substantial internships or published work, and even then, most early-career roles still prefer one. Cut fluff before you stretch length.

A simple section order

• Contact: name, phone, email, city. Optional: LinkedIn or GitHub if they’re real and updated.
• Short summary (optional): 2-3 lines on focus + degree. Skip if you have nothing specific to say.
• Education: degree, school, year, GPA or marks if it helps for that company.
• Internships / experience: even short ones. Role, org, dates, 2-4 bullets.
• Projects: 2-4 strong ones beat a long laundry list.
• Skills: grouped: languages, tools, coursework-related tech you can discuss.
• Extras only if useful: certifications, languages, notable achievements. Don’t invent sections for empty space.

Contact that doesn’t break

Use a professional email. Put the phone number you actually answer. City is enough - full postal address is rarely needed. Avoid tiny icons and multi-column contact bars from Word; they often scramble when someone opens or parses the PDF.

Education: what recruiters look for

Degree, field of study, school name, graduation year. Add GPA if the company asks or if it’s a strength; leave it off if it hurts and the posting doesn’t require it. Coursework lines only help when they match the role (e.g. databases for a backend internship).

Projects and internships beat empty fluff

Lead with the strongest proof you have. For each item: what you built or owned, stack or tools, and one concrete outcome if you have it. “Built a booking page used by 40 classmates during a campus event” beats “passionate team player with excellent communication.”

If two projects say the same thing, keep the better one. Depth beats a crowded list of half-finished repos.

Writing bullets that sound like you

• Start with a verb: built, fixed, analyzed, presented, automated.
• Add a tool or context when it matters (React, Excel, lab equipment).
• Add a number when it’s true (users, %, time saved, team size).
• One idea per bullet. Two short bullets beat one long paragraph.

Skills: be interview-ready

Only list what you can talk about for a few minutes. Group simply (languages, frameworks, tools). Online course certificates are fine as a short line. Don’t turn the whole resume into a certificate wall.

What to skip

• Generic objectives (“seeking a challenging role to utilise my skills”).
• Photos unless a specific employer asks.
• Tables, text boxes, and heavy Word art (fragile in PDFs and parsers).
• Every club membership with no role. Prefer one real responsibility.
• Fake metrics. Interviewers ask.

Tailor lightly for each application

You don’t need a brand-new resume every time. Reorder projects, swap 3-4 bullets, and mirror a few words from the JD when they’re true. Save a base version, then a copy for the role. Sign in so those copies stay in one place.

When they also ask for a cover letter

Some applications and emails want a short letter. Keep it half a page, tied to the role, not a second resume. See the cover letter guide.

Before you send

• Export PDF and open it on your phone.
• Check nothing is cut off at the edges.
• File name like firstname-lastname-resume.pdf, not final_final2.
• Ask one friend to skim for 20 seconds and say what they remember.

In Gaash the preview matches the download. See preview vs PDF. Already have work experience? Read the experienced format guide instead.