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
- Username: short and professional —
rahulsharma,rahul-dev. It goes on your resume. - Photo and name: the same photo as LinkedIn helps people recognise you.
- Bio: one line — "Final-year CSE student · Java & MERN · building things that work".
- Location, email, LinkedIn link in the profile fields.
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:
- What is it? One or two lines + a screenshot or GIF.
- Live demo link (Vercel, Netlify, Render…). A working link is the strongest signal you can give.
- Features — 4–6 bullet points.
- Tech stack.
- How to run it locally — the exact commands.
- 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

## 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
- A proper
.gitignore— never commitnode_modules, build folders or.envfiles. - Never commit secrets (API keys, passwords). If you did, rotate the key; deleting the file doesn't remove it from history.
- Meaningful commit messages: "Add JWT login and protect expense routes", not "update" or "final final 2".
- Commit as you work, not one giant commit at the end — the history shows how you built it.
- A sensible folder structure and consistent formatting (Prettier/ESLint).
6. The contribution graph
The green squares show regular activity. Don't fake them with empty commits — interviewers can tell. Instead:
- Work on a project a little each week.
- Push your DSA solutions to a repo (one folder per topic) as you practise on the Codify DSA Sheet.
- Contribute small fixes to open-source projects you use.
7. Your first open-source contribution
- Find a project you use and look for issues labelled good first issue or documentation.
- Read
CONTRIBUTING.md, comment on the issue to ask if you can take it. - Fork, create a branch, make a small focused change, open a pull request with a clear description.
- 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
- Professional username, photo, bio
- Profile README (short)
- 4–6 pinned real projects
- Each with README, screenshot and live demo
- No secrets or
node_modulescommitted - Clear commit history
Link your GitHub on your resume and LinkedIn.
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.