First Job Resume: Samples, Examples & How to Make One

What to put on a resume for your first job (and what to skip)

A recruiter spends roughly 6–8 seconds on the first pass. For a fresher, they are scanning for four things: your degree, your skills, one or two projects, and whether the file is clean enough to open. Everything else is optional.

Keep it to a single page. As a fresher you have not earned a second page yet, and stretching to fill one screams padding. Cut the photo, the date of birth, the marital status, the full home address, and the "Declaration: I hereby declare…" line — none of it helps you and all of it wastes space Indian recruiters have stopped expecting.

• Header: name, city, phone, professional email, LinkedIn/GitHub link
• One-line summary or a sharp career objective
• Education (with CGPA/percentage if it's decent)
• Skills (grouped, honest)
• Projects (your strongest section as a fresher)
• Internships / training / certifications, if any
• Achievements or positions of responsibility (optional but powerful)

How to make a first job resume, step by step

If you have never written a resume before, don't overthink the design — follow this order and you'll have a complete, ATS-friendly first job resume in under an hour. Every step below maps to a section a recruiter actually scans, and you can do all of it free on our free resume builder for freshers.

• Step 1 — Header: put your name, city, phone, a professional email, and a LinkedIn or GitHub link on one line. Skip photo, age, and full address.
• Step 2 — Summary: write 2 lines naming your degree, your top 2–3 skills, and the role you want.
• Step 3 — Skills: group them into 3–4 honest categories (languages, tools, databases, soft skills).
• Step 4 — Projects: add your best 2, each with what you built, the tech you used, and a result or number.
• Step 5 — Education: degree, college, year, and CGPA/percentage if it's 70% or above.
• Step 6 — Extras: internships, certifications, or achievements — only if they're relevant.
• Step 7 — Export: save as a single-page, text-based PDF and run it through a free ATS checker before you apply.

First job resume sample 1: B.Tech CSE fresher (no experience)

Here's a full first job resume sample for a computer-science graduate with no formal work experience. Notice how the projects and skills carry the weight where a work-experience section would normally sit.

First job resume sample 2: B.Com fresher (accounts / finance)

A first job resume sample for a commerce graduate targeting an accounts or finance-analyst role. Certifications and a capstone project stand in for work history.

First job resume sample 3: student with no internship

If you have no internship and no certifications yet, you still have coursework, one project, and college activities. Here's how a first job resume looks when you're truly starting from zero — every honest detail earns its place.

First job resume tips for India (freshers)

Most resume advice online is written for the US or UK job market. Indian recruiters and campus-placement teams expect a few things differently — get these right and your first job resume instantly looks more relevant for roles at Indian companies and on portals like Naukri.

• Lead with your CGPA or percentage — Indian placement cells actively filter on it. Include it if it's 70% / 7.0 CGPA or above.
• Write your degree the Indian way — B.Tech, B.Com, BBA, MCA, B.Sc — with your college/university name and year of passing.
• For campus placements, mirror the exact skills in the company's eligibility criteria (e.g. "Java, DBMS, Aptitude") so you clear the first shortlist.
• Drop the photo, date of birth, father's name, marital status, and the "I hereby declare" line — modern Indian recruiters no longer expect them and they waste a fresher's limited space.
• Use a professional email like firstname.lastname@gmail.com — not a college ID that expires or a nickname address.
• Keep it to one page and export a text-based PDF — big Indian IT firms (TCS, Infosys, Wipro, Accenture) screen resumes through an ATS first, so run yours through a free ATS checker before applying.

A quick before/after: suppose you're Ananya, a B.Com fresher

Suppose Ananya just finished B.Com and wants a finance-analyst role, but her draft resume opens with "Hardworking and dedicated individual seeking a good opportunity," followed by her school marks from Class 10. Nothing on the page tells a recruiter she can actually do finance work, so it gets skipped in seconds.

Now imagine she reshapes it: the summary becomes "B.Com graduate (72%) skilled in Excel, Tally and financial statement analysis; completed a 6-week accounting internship and a capstone project modelling a small business's cash flow." She drops the school marks, adds a Projects section describing her cash-flow model with real numbers, and lists an Advanced Excel certificate. Same person, same experience level — but now the page proves capability instead of just claiming enthusiasm. That reshuffle, not new experience, is what usually turns a fresher resume from ignored to shortlisted.

The summary line: your 10-second pitch

The top of the page is prime real estate, so don't waste it on a generic objective. Instead of "Seeking a challenging role in a reputed organisation to utilise my skills," say who you are and what you can do.

Compare these two openers for a B.Tech CSE fresher:

Before: "Seeking a challenging position in a growth-oriented company where I can enhance my skills and contribute to organisational success."

After: "Computer Science graduate (CGPA 8.1) who has built 3 full-stack projects in React and Node. Comfortable with Git, REST APIs and SQL. Looking for a junior developer role to ship real features."

The second version names your degree, your stack, and a specific goal. If you're still deciding between a summary and an objective, our guide on the career objective for freshers breaks down when each one works better.

Projects: the section that replaces experience

This is where first-job resumes are won or lost. With no jobs to list, your projects prove you can actually do the work. But most freshers write them as a to-do list — "Made a website using HTML, CSS, JS" — which tells a recruiter nothing.

Write each project like a mini-achievement: what you built, the tech you used, and the result or scale. Numbers make it real.

Before: "Weather App — Created a weather application using JavaScript and an API."

After: "Weather App (React, OpenWeather API) — Built a responsive app that fetches live forecasts for any city, with search history stored in localStorage. Handles API errors gracefully; ~500 lines, deployed on Netlify."

Two strong projects beat five weak ones. If you're unsure how to phrase them, we wrote a full walkthrough on how to write a project description in a resume with more before/after examples.

Skills and education: honest, grouped, scannable

Group your skills so a recruiter can scan them, and be honest — if you list "Python (Advanced)" you will be tested on it in the interview. A clean split looks like: Languages, Frameworks/Tools, Databases, Soft skills.

For education, lead with your highest qualification. Include CGPA or percentage if it's 7.0/70% or above; if it's lower, keep it but let your projects and skills do the heavy lifting. Mention relevant coursework only if it maps directly to the role (e.g. "DBMS, Operating Systems, Data Structures" for a developer role).

One more thing that trips freshers up: formatting. Fancy templates with columns and tables often break in Applicant Tracking Systems. Run your draft through a free ATS checker before you apply so you know it parses cleanly.

A copy-ready first job resume skeleton

Here's the order that works for almost every fresher role. Fill it top to bottom and you have a complete first-job resume.

• Name + city + phone + email + LinkedIn/GitHub (one line)
• Summary: degree + top 2 skills + the role you want
• Skills: grouped into 3–4 clean categories
• Projects: your best 2, each with tech + result
• Education: degree, college, year, CGPA
• Internships/Certifications: only if relevant
• Achievements: hackathon, topper, club lead, volunteering

Tailor it — one resume does not fit every job

The single fastest way to look like a serious candidate is to mirror the job description. If the posting asks for "React, REST APIs, and testing," those exact words should appear in your skills and projects (assuming they're true). ATS software ranks resumes partly on keyword match, and recruiters notice when your resume speaks their language.

You don't rewrite the whole thing each time — you swap the summary line and reorder your skills to put the most relevant ones first. For a deeper dive on layout and keywords, the ATS resume format for freshers guide is a good next read.

No experience? One project changed everything

Karthik finished his degree with no internship and felt he had nothing to put down. Instead of a thin, half-empty page, he wrote up one college hackathon project and a self-taught Python certificate in real detail — what he built, the tools he used, and the result. That single well-described project was enough to land his first interview.

A first-job resume isn't weak because you lack experience — it's weak when you undersell what you already have. Describe one real project properly and you're ahead of most freshers.

FAQs