GitHub portfolio for freshers
For a fresher, GitHub is often the only place a recruiter can see your work directly. FresherHub reads your public repositories, turns what it finds into evidence for your target role, and lets you publish a simple portfolio page when you are ready.
What a fresher's GitHub should show
These come straight from the requirements of the 11 tech roles FresherHub checks you against:
A README that explains the project in two minutes
What it does, the stack, how to run it, and for an API, the main endpoints. Every role FresherHub checks includes a requirement for GitHub projects that are quick to evaluate.
Steady commit history
Small, regular commits over weeks, not a finished project pushed in one go. Most roles list Git and version control as a requirement.
Tests
Test files and a test runner set up in the repository. For backend, frontend, mobile and QA roles, automated testing is a must-have.
A CI workflow
A GitHub Actions workflow (or similar) that runs your tests or linting on every push. Seven of the eleven roles include CI/CD.
Something deployed or easy to run
A live URL, or clear deploy instructions. For web, backend, ML and GenAI roles, a deployed project is a must-have.
Your own work, not just forks
Forked repositories rarely show what you can do. Original projects, even small ones, do.
How FresherHub analyses your GitHub
- You sign in with GitHub. We can read your public repositories only, never private ones, and nothing is analysed until you start a sync.
- We pick up to five repositories for a closer look, preferring ones that are recently active, relevant to your target role, and your own rather than forks.
- We look at the files in each one, skipping generated folders such as
node_modulesanddist, and check for tests, CI, Docker, a README and the libraries you use. - Where a repository clearly matches a project in your profile, we link them. If the match is unclear, we ask you instead of guessing.
What counts as evidence
A skill on your resume is a claim. The same skill in your code is evidence, and it counts for more in your readiness score. Here is how some GitHub signals are rated:
| What we find | Evidence level |
|---|---|
| Several test files in a repository | Demonstrated |
| A CI workflow under .github/workflows | Demonstrated |
| A language used across two or more of your analysed repositories | Demonstrated |
| A few test files | Observed |
| A Dockerfile | Observed |
| A README with real structure (headings) | Observed |
| A framework or library in your dependency files | Observed |
Every piece of evidence records where it came from and why it counts, so you can check it. The full scale, from missing to strong, is explained on How FresherHub works, and you can see evidence in action in the example report.
Your public portfolio, on your terms
FresherHub can turn your profile and projects into a simple portfolio page at fresherhub.app/your-name. It is built around privacy:
- It starts as a draft that only you can see. Nothing is public until you publish it, and you can unpublish at any time.
- Your email and phone number are hidden by default. So is the option to download your resume.
- Your readiness score, action plan and assessment history are never shown on it.
- You choose which sections appear, such as projects, skills and education.
See what your GitHub proves
Pick your target role, connect your public repositories, and see which requirements your code already proves and which it doesn't.