Getting everything ready for you…

Loading courses, problems and your progress. This takes just a moment.

0s

Guides › Career

GitHub Profile for Freshers: Make Recruiters Notice Your Projects

Profile README, pinned repos, project READMEs with live demos, clean commit habits, your first open-source contribution and what to build.

For a fresher, your GitHub is the proof behind your resume. A recruiter or interviewer who opens it should understand in 30 seconds what you can build. This guide shows how to set up the profile, present your projects and make your repos look professional.

1. The basics

New to Git itself? Start with Git and GitHub Essentials and the Git docs.

2. A profile README

Create a repository with the same name as your username (e.g. rahulsharma/rahulsharma) and add a README.md. It appears at the top of your profile.

Keep it short:

## Hi, I'm Rahul 👋
Final-year CSE student who likes building web apps and solving DSA problems.

**Currently:** learning Spring Boot and system design
**Looking for:** SDE internships / full-time roles (2026)

### Projects
- **[Chat App](link)** — real-time chat with rooms and typing indicators (React, Node.js, Socket.IO)
- **[Expense Splitter](link)** — split group expenses and settle up in the fewest payments (MERN)

### Skills
Java · JavaScript · React · Node.js · MongoDB · SQL · Git

📫 rahul@email.com · [LinkedIn](link)

Skip giant stats widgets, animated banners and long badge walls — they slow the page and say little.

3. Pin your best 4–6 repositories

On your profile, click Customize your pins and choose real projects, not tutorial copies or "hello-world". Order them by how impressive they are for the role you want.

4. Every pinned repo needs a good README

This matters more than anything else. A README should answer, in order:

  1. What is it? One or two lines + a screenshot or GIF.
  2. Live demo link (Vercel, Netlify, Render…). A working link is the strongest signal you can give.
  3. Features — 4–6 bullet points.
  4. Tech stack.
  5. How to run it locally — the exact commands.
  6. What I learned / challenges — 2–3 lines (interviewers love this).

Template:

# SplitEasy — group expense splitter
Track shared expenses and see who owes whom, settled in the fewest payments.
**Live:** https://spliteasy.vercel.app

![screenshot](docs/screenshot.png)

## Features
- Groups with members and expenses
- Equal, exact and percentage splits
- "Settle up" with the minimum number of payments (greedy algorithm)
- JWT login, responsive UI

## Tech
React, Node.js, Express, MongoDB, JWT

## Run locally
git clone … && cd spliteasy
npm install && npm run dev

## What I learned
Designing the settle-up algorithm and keeping balances consistent when expenses are edited.

5. Clean code habits that show

6. The contribution graph

The green squares show regular activity. Don't fake them with empty commits — interviewers can tell. Instead:

7. Your first open-source contribution

  1. Find a project you use and look for issues labelled good first issue or documentation.
  2. Read CONTRIBUTING.md, comment on the issue to ask if you can take it.
  3. Fork, create a branch, make a small focused change, open a pull request with a clear description.
  4. Respond politely to review comments.

Fixing a typo in docs is a valid start; one merged PR in a known project is a great resume line.

8. What to build

If your repos are mostly tutorials, build 2–3 original projects. Ideas with step-by-step guides: Projects. Choose them by the role you want: Projects for your resume by role.

Checklist

Link your GitHub on your resume and LinkedIn.

More guides