On MyInternships.in, 21,874 candidates list Python and 10,194 list Git. So fewer than half as many name the tool that developers use to save, share and show their code as name the language itself.
We cannot see from that how many candidates have public work. But it hints at a gap every recruiter recognises: many more people claim a skill than can point to something they made with it. Closing that gap is the most reliable way to improve your chances, and it does not require a job, a famous college or money.
Listing versus showing, in numbers
For context, here are some skills from our candidate profiles on 1 October 2026 where showing is especially easy. As always these are names that candidates typed into their own profiles, counted once per skill, and they say nothing regarding quality.
| Skill listed on profile | All India | Bengaluru | Pune | Delhi |
|---|---|---|---|---|
| Python | 21,874 | 2,458 | 1,778 | 1,162 |
| JavaScript | 11,695 | 1,314 | 988 | 634 |
| Git | 10,194 | 1,200 | 914 | 536 |
| Power BI | 9,275 | 1,022 | 919 | 623 |
| React.js | 5,729 | 623 | 487 | 324 |
| Figma | 1,821 | 152 | 128 | 116 |
| Canva | 1,532 | 130 | 109 | 128 |
| Content Writing | 581 | 25 | 27 | 47 |
Every skill in that table produces something visible: code, a dashboard, a screen, a design, an article. If yours is on the list and your profile has no link, you are leaving your strongest argument unused.
What counts as proof
Proof is anything a stranger can open and judge in two minutes without your help. That rules out "available on request" and it rules out a certificate, which shows you attended.
- For programming: a repository with a README, or better, a working link.
- For data skills: a notebook or dashboard with a written conclusion.
- For design: a portfolio page or a shared file showing the final screens and how you got there.
- For writing: two or three published pieces, even on a personal blog.
- For marketing: a page or account you ran, with what you tried and what happened.
- For core engineering: drawings, photographs of what you built, a short test report.
Choosing a project worth showing
The common mistake is to build what everyone builds. A recruiter who has seen the same calculator, the same to-do list and the same film recommendation notebook many times cannot tell you apart from the tutorial you followed.
A better project has three properties.
- It solves a problem you can name. Your hostel's mess menu, your cricket club's scoring, your mother's tuition fee records, your department's timetable clashes. Small and real beats large and generic.
- Someone used it. Even three friends. "Used by my project group to track tasks" changes how the work is read.
- It is finished. One complete small thing outweighs four abandoned ambitious ones. Finished means it runs, it has instructions, and the obvious errors are handled.
If you are stuck for ideas, take a course project you have already done and change the data or the audience so that it becomes yours.
A GitHub profile a recruiter can read
Most recruiters are not going to read your code line by line. They will glance at the page and form an impression in seconds. Make those seconds count.
- Pin your best two or three repositories. Hide or archive the empty and half-started ones.
- Write a README for each. Four parts are enough: what it does, a screenshot, how to run it, what you would improve.
- Use clear repository names. "hostel-mess-planner" tells a story. "project-final-v2" does not.
- Commit as you go. A history of small commits over days shows how you work. A single upload of everything at once looks like a copy.
- Keep secrets out. Never commit passwords or API keys. Interviewers notice.
If you list Git as a skill, your repository history is the evidence. If you do not list it yet, learning the basics takes a weekend and puts you in a noticeably smaller group than the language alone.
Portfolios for people who do not code
The same thinking applies outside software. A portfolio is simply a tidy collection with context.
For each piece, add three lines: the brief or problem, what you did, and the result or what you learnt. A poster with no explanation is decoration. That poster with "designed for our college blood donation camp; the brief was to make the date and venue readable from across a corridor" is design.
Limit yourself to your best five or six pieces. Order them so the strongest comes first, because many viewers stop after two. Check that every link opens without a login, and view the whole thing on a phone.
Writing the project line on your profile
A link needs a sentence to earn the click. Use a simple pattern: what you built, for whom, with what, and one outcome.
Instead of "Library Management System using Java and MySQL", try "Built a book-issue tracker in Java and MySQL for our department library; replaced a paper register for one semester."
The second version is longer by a few words and far more believable. It names a user and a consequence. Keep outcomes honest; a modest true result is better than an impressive invented one, and you will be asked about it.
Be ready to talk about it
Showing your work invites questions, which is exactly what you want. Before an interview, prepare short answers to four of them.
- Why did you build this?
- What was the hardest part?
- What would you do differently?
- Can you change something small while we watch?
The fourth is increasingly common. If you built the project yourself, it holds no fear. If you copied it, this is where that becomes clear, which is the best argument for doing your own work from the start.
A two-weekend plan
Weekend one: pick one small problem, build the simplest version that works, and commit as you go.
Weekend two: fix the rough edges, write the README, take a screenshot, ask two friends to try it, and note what they said.
Then update your profile. Add the project line and the link, and create a clean CV with the resume builder. Early-stage companies tend to value demonstrated work highly, so have a look at startup internships, and read the blog for more on applications.
With one finished, visible piece of work, you are no longer asking an employer to take your word for it. Find internships that match your project and put the link in the first line of your application.


