ResumeCrew
Menu

Resume example · Software Engineer · Fresher

Software Engineer resume for freshers: a sample from India

A software engineer fresher is read in seconds for three things: can you build something that runs, can you say what it did for real users, and do your marks clear the screen. Projects and one internship carry the page; marks stay on it, short and visible.

Last reviewed
October 2026
Fictional sample
0 to 1 year of experience

Summary examples for a fresher

Two ways to open the page. Neither is the summary on the sample resume beside it, so you can see more than one approach.

Summary example 1

Summary
B.E. Information Technology student (2026) who built and deployed a Node.js and PostgreSQL booking app used by 150 students. Comfortable with REST APIs, SQL and Git; applying for backend developer roles.Names one deployed project and the role sought. Works when you have a single clear strength and no internship yet.

Summary example 2

Summary
Final-year B.Tech Computer Science student with a 10-week Java internship and 300+ solved DSA problems. Looking for a Software Engineer role in a product or services team.Leads with the internship and a count. Fits a candidate whose projects are course-based but whose internship was real work.

Bullet rewrites, weak to strong

Each pair shows a line people really write and a stronger version of the same fact. The numbers are illustrations. If you have no number, see resume bullets with numbers when you have none.

  1. Before

    Did a project on e-commerce website

    After

    Built a full-stack e-commerce app (React, Node.js, MongoDB) with cart, Razorpay test checkout and JWT auth; deployed on Render and used by 40+ classmates during testing

    Why

    Names the stack, the features and who used it. A deployed link and a user count turn a tutorial clone into evidence.

  2. Before

    Learned DSA

    After

    Solved 450+ problems on LeetCode and GFG in Java; ranked in the top 8% of 2,100 participants in college CodeWar 2025

    Why

    A count and a rank replace the verb 'learned'. The field size (2,100) is what gives the rank meaning.

  3. Before

    Worked on a team project for college

    After

    Led a 4-member team building a seat-booking app in Flutter and Firebase; shipped in 6 weeks and used by the library for one semester

    Why

    Team size, your role, the time and the outcome. 'Worked on' hides all four.

  4. Before

    Responsible for backend work during internship

    After

    Built 5 REST endpoints in Spring Boot for a vendor-invoice tracker used by 300 finance staff, with 28 JUnit tests behind them

    Why

    Opens with what you built, gives the scale of use, and shows the tests. 'Responsible for' only says you were present.

  5. Before

    Used Git and GitHub

    After

    Maintained a public GitHub repo with 120+ commits, CI checks on every pull request and a README that two classmates followed to run the app

    Why

    Turns a tool name into behaviour a reviewer can verify by clicking the link.

  6. Before

    Participated in hackathon

    After

    Reached the final of Smart India Hackathon 2025 (top 10 of 180 teams) with a Flutter app for crop-price alerts in Hindi and Marathi, built in 36 hours

    Why

    Rank and field size, the product and the constraint (36 hours). Participation alone is not an achievement.

Skills to list, grouped

Group skills into three or four lines and keep only those you could discuss for ten minutes. Each should appear in a bullet, a project or a certificate.

  • Languages: Java, Python, JavaScript, SQL
  • Backend and data: Spring Boot, Node.js, REST APIs, PostgreSQL, MongoDB
  • Tools: Git, Docker, Postman, Linux
  • Core: Data Structures, OOP, DBMS

What recruiters for this role tend to look for

  • A link that opens: a GitHub repository or live demo with a README, not a folder of tutorial code.
  • Marks that clear the screen. Service companies often ask for a minimum percentage or CGPA, so keep it near the top where a parser and a person both find it.
  • Evidence for each skill: every language in Skills should appear in a project or internship bullet.
  • A one-page, single-column file with standard headings, so a portal reads Education and Skills into the right fields.
  • Honest scope: team size, your own part, and what was actually deployed.

Mistakes common at this level

  • Listing 25 languages and tools when three appear in a project. Recruiters check the bullets, not the list.
  • Tutorial clones (to-do app, weather app, calculator) with no users, no twist and no deployment.
  • Hiding a CGPA under 7. The application form asks for it later anyway; lead with projects and keep the score honest.

Section order on the sample

The sample uses the Fresher First template, A4 (210 by 297 mm), one column, with the sections in this order: Summary, Education, Projects, Skills, Experience, Certifications. The order follows the level: education and projects lead because there is little job history yet.

Questions people ask

Should a fresher software engineer put school marks on the resume?

For campus drives and IT-services companies, usually yes: one line each for Class X and XII. Product companies and startups care less. If the application form asks for school marks, make the resume agree with it. More in CGPA vs percentage and school marks.

How many projects should I list?

Two to four, most relevant first. One deployed project with real users beats five unfinished ones. If you have an internship, it can sit above the projects, but the projects still need numbers.

Is a GitHub link necessary?

It is not mandatory, but developer recruiters often look for one. Write the URL as visible text, pin your best two repositories and give each a README that explains how to run it.

Next step

Build yours in the chat

Answer a few questions, one at a time. The reviewer drafts each line, asks for the numbers it cannot guess and never adds a fact you did not give. Already have a resume? Check it first and see what a parser reads.