By Tanul Mittal4 min read
When a recruiter or engineer screens fresher software resumes, most candidates look the same on paper: B.Tech or BCA, similar CGPA, the same list of languages. What separates them is what they built and whether they can explain it. This post covers how to make your projects, skills and links do that work.
For the full role page with sample sections, see our software engineer resume guide.
Keep it to one page.
Recruiters can tell a tutorial clone from a project you thought through. Choose projects that show at least one of these:
A to-do list or weather app from a course is fine practice, but don't lead with it.
Each project gets a one-line description and two to four bullets. Use this pattern: what you built + how + what changed.
Weak:
Stronger (illustrative):
Numbers help when they are real: users, response time, data size, accuracy, test coverage. If you don't have a measured number, describe the scope ("three user roles", "12 API endpoints") rather than inventing one.
Add the GitHub link and, if there is one, a live demo link on the project's title line.
Group skills so they scan quickly:
Only list what you could answer interview questions on. "Expert" and star ratings invite the toughest questions; plain lists are safer. Core CS subjects (DSA, OOP, DBMS, operating systems, computer networks) can go in a short "Coursework" line, since many fresher interviews test them.
Check every link opens without a login and points to the right place.
A software internship, even a short one, should have bullets in the same "what + how + result" form. Name the stack. If the work was under an NDA, describe it generally ("internal dashboard for the support team") without sharing confidential details.
Merged pull requests to open source projects count as experience. Link them directly.
Mass-recruiting service companies often screen on eligibility (CGPA, backlogs, graduation year) and aptitude tests, so a clean, complete resume matters. Product companies and startups usually look harder at projects, problem-solving and GitHub. Adjust which section comes first accordingly, and always mirror the specific stack from the job description where it is true for you.
Before you apply, check your resume against the job description to see which of its skills you have not mentioned yet.
Two to four. Choose the ones closest to the job's tech stack and the ones where you wrote a meaningful part of the code. Depth beats a long list of tutorial clones.
Yes, as a fresher. Many campus and off-campus drives use a CGPA cut-off. If yours is below a typical cut-off, list it anyway and let strong projects carry the resume.
Add a coding profile link if it shows sustained practice or contest ratings, especially for product companies that test DSA. A profile with a handful of solved problems adds little.
It is strongly recommended. Make sure the linked repositories have a clear README, readable commit history and code you can explain in an interview.
When an Indian recruiter asks a fresher for a CV, they almost always mean a one-page resume. Here is the format section by section, a sample layout, and how to fix an old-style CV template.
Most fresher data analyst resumes list the same tools. The ones that get calls show what you found in real data. Here is how to choose skills, build projects and write bullets.
A fresher teacher's resume is built on qualifications and teaching practice. Here is how to present B.Ed or D.El.Ed, CTET or TET, and your internship so schools see your fit fast.