Guides › Career
Fresher Software Engineer Resume: What to Write (and What to Cut)
A one-page resume that gets shortlisted — section order, how to describe projects with impact, the skills section, and the mistakes recruiters reject on sight.
A recruiter spends well under a minute on a fresher resume before deciding whether to read it properly. Your job is to make the important things — skills, projects and proof — visible in that time. Here is how.
The rules that matter most
- One page. As a fresher, nothing justifies two.
- A simple single-column layout. Many companies run resumes through an applicant tracking system (ATS) that struggles with tables, columns, icons and text inside images.
- Readable fonts (Calibri, Arial, Inter, Garamond) at 10–11 pt, with clear section headings.
- Save as PDF and name it properly:
Firstname_Lastname_Resume.pdf. - No photo, date of birth, father's name or full address unless the company explicitly asks. City and state is enough.
Section order for freshers
- Header — name, phone, professional email, city, LinkedIn, GitHub and portfolio links.
- Education — degree, college, year, CGPA (and 12th/10th percentages, which Indian campus drives often check).
- Skills
- Projects — your most important section.
- Experience / internships — move this above projects if you have a real internship.
- Achievements — contest ranks, hackathons, certifications, coding profiles.
Skip the "Objective" section. A one-line summary at the top is optional and only useful if it is specific.
Writing project points that get noticed
Most fresher resumes describe projects like this:
❌ Made an e-commerce website using MERN stack.
That says nothing about you. Use the formula action verb + what you built + how + result:
✅ Built a MERN e-commerce app with JWT login, cart and Razorpay test payments; deployed on Render and Vercel.
✅ Cut product-search time from ~2 s to under 200 ms by adding MongoDB text indexes and paginating results.
✅ Wrote 40+ API tests with Jest, catching 6 bugs before deployment.
For each project, include:
- 2–3 bullet points, each starting with a verb: built, designed, implemented, reduced, automated.
- The tech stack on one line.
- Links to the live demo and the GitHub repository. A deployed project instantly moves you above most applicants.
- Numbers wherever honest: users, response time, test count, data size.
Only list projects you can explain in depth. Interviewers will ask about every line.
The skills section
Group skills so they can be scanned in seconds:
Languages: Java, Python, JavaScript, SQL
Web: React, Node.js, Express, HTML, CSS
Databases: MySQL, MongoDB
Tools: Git, GitHub, Postman, VS Code, Linux
Concepts: Data Structures & Algorithms, OOP, DBMS, Operating Systems
Do not add skill bars or ratings ("Java ★★★★☆") — they mean nothing to a recruiter. And don't list something you used once in a tutorial; "Kubernetes" on a resume invites a Kubernetes question.
Achievements worth listing
- Problems solved and rating on coding platforms (with a link)
- Contest ranks — e.g. "Rank 42 of 1,200 in a weekly coding contest"
- Hackathon results, open-source contributions
- Certificates that show finished work, such as a completed roadmap certificate with a verification link
Common mistakes recruiters reject on sight
- Spelling and grammar errors — run a spell check and ask a friend to read it.
- An unprofessional email address.
- Copying a template's sample text and forgetting to change it.
- Listing every subject from your syllabus under skills.
- Huge paragraphs instead of bullet points.
- Links that don't work — click every one before you send it.
Tailor it for each company
Keep one master resume, then adjust the order of skills and projects for each role. Applying for a frontend role? Put your React project first. Data analyst? Lead with SQL and Python and a dashboard project. Read the job description and make sure the words it uses appear where they honestly apply to you.
Next steps
Not sure your projects are strong enough? See which projects to build for each role — every one has a step-by-step guide on Projects. Then make sure the links on your resume lead somewhere good: a clean GitHub profile and a complete LinkedIn profile. A verifiable roadmap certificate is also worth listing.
With your resume ready, prepare for what comes after the shortlist: 12 DSA patterns for interviews, the Top 50 questions for Java, OOP, DBMS, OS and SQL, and 20 HR interview questions.
More guides
- How to Use Codify: A 7-Day Start Plan — New here? Pick a roadmap, make a study plan, start the DSA sheet, revise with notes, practise for placements and test yourself — one step a day, then a daily routine.
- Infosys Preparation Guide: Online Test, Pseudocode and Interview — Roles (SE, DSE, SP), what each section of the Infosys online test checks, how to crack pseudocode and reasoning, a 4-week plan and the interview.
- Wipro Elite NLTH Preparation: Aptitude, Essay and Coding — The Wipro fresher test round by round — quant, logical and verbal, the written essay, two coding problems — plus a 3-week plan and interview tips.
- Accenture Preparation Guide: Cognitive, Technical, Coding and Communication — Every Accenture round explained — cognitive, MS Office/networking/cloud technical MCQs, pseudocode, coding and the spoken-English test — with a 4-week plan.