Fresher Resume Format India 2026: One-Page Template With Examples

For freshers (0–1 year experience), one page is the rule. A two-page fresher resume signals poor judgement about what matters: recruiters spend 7–10 seconds on initial review.

Section order (top to bottom):

``` [NAME: large, bold] [Phone] | [Email] | [LinkedIn URL] | [GitHub URL if technical] [City, State]: optional if not relevant to role

EDUCATION [Degree], [Branch/Major]: [College Name], [City] [Year of Graduation] CGPA: X.X / 10 OR Percentage: XX% [12th Standard]: [School Name], [Board] [Year] [Marks/Percentage] [10th Standard]: [School Name], [Board] [Year] [Marks/Percentage]

SKILLS Programming Languages: [Java, Python, C++, JavaScript] Frameworks/Libraries: [React, Spring Boot, Django] Databases: [MySQL, PostgreSQL, MongoDB] Tools: [Git, Docker, VS Code, Postman] Other: [relevant: e.g., 'Machine Learning basics', 'AWS EC2']

PROJECTS ← most important section for freshers [Project Name] | [Tech Stack Used] [Month Year]

• [What the project does in one sentence]
• [Your specific contribution/role]
• [One measurable outcome if possible]

INTERNSHIPS / EXPERIENCE (if any) [Role] | [Company] [Month Year – Month Year]

• [What you did]
• [Impact/output]

CERTIFICATIONS (if relevant)

• [Certificate Name], [Issuing Body], [Year]

ACHIEVEMENTS / EXTRACURRICULARS (optional, keep brief) - [Rank in competitive exam, hackathon win, position of responsibility] ```

What NOT to include:

• Objective/Summary for freshers (cliché, wastes space: everyone says 'seeking a challenging role')
• Photo (not required, and can trigger bias; most large companies explicitly request no photo)
• Date of birth, gender, religion, marital status (illegal to ask in most contexts, doesn't help)
• References (outdated: 'available on request' wastes a line)
• Hobbies unless genuinely relevant or distinctive (reading, cricket, music are filler)

For a fresher with no work experience, the Projects section is your portfolio. It's what differentiates you from 300 other candidates with similar CGPA from similar colleges.

How to write a strong project entry:

Weak (what most freshers write): ``` Online Shopping Website (2023) - Developed an e-commerce website using HTML, CSS, JavaScript, and PHP - Implemented login, product listing, and cart features - Used MySQL database ```

Strong (what gets interviews): ``` ShopEasy: E-Commerce Platform | React, Node.js, MongoDB, Express Jan–Mar 2024 - Built a full-stack e-commerce app with JWT authentication, product search/filter, and Razorpay payment integration; deployed on AWS EC2 - Reduced page load time by 40% by implementing Redis caching for product listings - GitHub: github.com/yourname/shopeasy | Live: shopeasy.vercel.app ```

What makes the strong version better:

• Specific tech stack named (not 'web technologies')
• Dates included (shows recent, not 2-year-old project)
• One measurable outcome (40% load time reduction)
• Links to GitHub and live demo: recruiters can verify
• Action verbs: 'Built', 'Reduced', 'Deployed': not 'helped build' or 'involved in'

How to add quantifiable outcomes when you don't have metrics: You don't need production traffic data. You can measure:

• Lines of code, number of features
• Test coverage percentage
• API response time before/after optimisation
• Number of users in a college pilot (even 50 is a number)
• 'Reduced manual process from 3 hours to 5 minutes' (if it automated something)

Minimum 2, maximum 3 projects on a fresher resume. If you only have one project, add a second one: build a small one specifically for the resume. A weekend project that solves a real problem is better than listing 'Participated in XYZ hackathon' with no project.

Most large Indian companies (TCS, Infosys, Accenture, Wipro, and all major product companies) use Applicant Tracking Systems (ATS) to filter resumes before a human sees them. Your skills section is the primary ATS filter.

How ATS screening works: The recruiter or hiring manager sets up keyword requirements (e.g., 'Java OR Python', 'SQL', 'REST API'). The ATS scores your resume based on keyword matches. Resumes below the threshold are never seen by a human.

What this means for your resume:

1. Use the exact keyword from the job description: if the JD says 'REST APIs', don't just say 'web services'
2. Include both the full name and acronym: 'Natural Language Processing (NLP)', 'Structured Query Language (SQL)'
3. Avoid graphics, tables, or columns in the skills section: some ATS systems can't parse them
4. Put skills in plain text, not in a visual meter ('Python ████░░ 70%'): ATS reads text, not graphics

Skills to include based on target role:

For software engineering (IT services): Java / Python / C++, Data Structures and Algorithms, SQL / MySQL, OOP concepts, Git, REST APIs, Linux basics

For full-stack / product company roles: JavaScript, React or Angular or Vue, Node.js, Python or Java (backend), SQL + one NoSQL (MongoDB/Redis), Git, Docker basics, REST/GraphQL APIs, AWS or GCP basics

For data science / analyst roles: Python, NumPy, Pandas, Matplotlib/Seaborn, SQL, Machine Learning (scikit-learn), Statistics, Tableau or Power BI, Excel, Jupyter Notebook

What NOT to list in Skills: MS Office, Google Docs, Canva: not technical skills for engineering roles (unless explicitly required by the JD) Basic HTML/CSS: if applying for a frontend role, list the specific frameworks; standalone HTML/CSS is filler for most roles

Standard format: ``` Bachelor of Technology (B.Tech), Computer Science and Engineering XYZ Engineering College, Bengaluru: VTU 2020–2024 CGPA: 7.8 / 10

XII (PCM + CS), CBSE: ABC Public School, Hyderabad 2020 87.6%

X, CBSE: ABC Public School, Hyderabad 2018 91.4% ```

CGPA vs percentage: when to show which:

• Most Indian companies accept both; show what's higher
• If CGPA is low (below 6.5) but percentage is decent (above 60%), you may choose to show percentage
• Some companies (Infosys, TCS) have minimum CGPA requirements (typically 6.0 or 60%): check before applying
• If your CGPA improves significantly after 3rd year: show 'CGPA (last 2 semesters): 8.4 / 10' alongside overall CGPA

How to handle a low CGPA: A CGPA below 6.0 is a filter issue at large IT services companies: be direct about it with yourself. Strategies:

1. Focus on product companies and startups: many explicitly say 'no CGPA bar' or set it at 6.0
2. Compensate with strong projects, internships, and certifications: these carry more weight at product companies
3. Target off-campus applications rather than campus drives: off-campus often has more flexibility
4. Explain in cover letter if the low CGPA has a specific reason (health, family, changed branch)

Backlogs: Do NOT list backlogs on the resume: they will surface in background verification. Most companies ask explicitly during the HR round; answer honestly then. A resolved backlog (cleared in later semester) is much better than an active one.

Formatting that helps ATS and human readers:

• Font: Calibri, Garamond, or Georgia at 10–11pt for body; 14–16pt for name
• Margins: 0.5 to 1 inch on all sides: maximise content space
• Section headers: bold and slightly larger than body text
• Dates: consistent format throughout: 'Jan 2024' or 'January 2024', not mixed
• File format: PDF is safest for formatting preservation; some companies specifically request .docx
• File name: YourNameResume.pdf: not 'ResumeFinal_v3.pdf' or 'myresume123.pdf'

Most common fresher resume mistakes:

1. Generic objective statement: 'Seeking a challenging opportunity to utilise my skills': says nothing; delete
2. Responsibilities instead of achievements: 'Responsible for developing X' → 'Developed X, resulting in Y'
3. Passive language: 'Was involved in', 'Helped with', 'Assisted in': shows minimal ownership; use 'Built', 'Developed', 'Led', 'Implemented'
4. Including every course from the degree: DBMS, Data Structures, OOP: these are expected; list them only if you have strong project work in them
5. College projects with no GitHub link: if the project exists and the code is presentable, always add a GitHub link
6. Too many bullet points per section: 3–4 bullets per project/experience is the maximum; prioritise impact over comprehensiveness
7. Inconsistent formatting: some dates right-aligned, some not; some bullets ending with periods, some not; recruiters notice
8. Font size too small to fit everything: if you're at 8pt to make it fit one page, cut content instead

The 7-second test: Before submitting, ask someone who doesn't know your background to glance at your resume for 7 seconds and tell you: (1) what role you're targeting, (2) what your strongest project is, (3) what your tech stack is. If they can't answer all three, your resume needs restructuring.