LinkedIn - lesson 5 | HackIndia Skills

Key point

One rule

Your skills and experience should point to one target role. If you want frontend roles, React, JavaScript, CSS, Git, and API integration belong above random tools you tried once.

Only list what you can explain in an interview or prove with a project, repo, certificate, or role.

Skills are signals

LinkedIn skills are not a trophy shelf. They help a recruiter or builder quickly understand what you can do.

Choose 10 to 15 strong skills first. Put your best 3 to 5 near the top. These should match your profile goal from lesson 1 and your projects from lesson 4.

Your to-do

Choose your skills

Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.

Write your target role, like frontend developer, backend developer, UI designer, or data analyst.
List tools used in your real projects, internships, assignments, or hackathons.
Keep skills you can prove with a link, screenshot, certificate, or clear story.
Move role-matching skills higher than general skills like communication or teamwork.
Remove skills you only watched in a tutorial and never used.

0 of 5 done

Common mistake

Avoid padding

Do not add every buzzword you know. A long list with weak proof reduces trust.

If your profile says AWS, Docker, MongoDB, React, Python, Java, ML, Figma, and Solidity, but your projects show only one HTML page, it feels padded. Start honest. Grow the list as your work grows.

Experience is broader

Experience is not only paid work. As a student, you can add internships, volunteering, open-source work, campus roles, hackathons, club work, freelance work, and strong academic projects.

The test is simple. Did you do real work for a team, user, event, project, or public repo? If yes, it may belong in experience.

Example

Good entry format

Use action, tool, and proof. Keep each bullet specific. Numbers help when they are real, but do not invent them.

Role: Frontend Developer, College Hackathon Project
Organisation: HackIndia Hackathon
Dates: Jan 2026

- Built a React dashboard for tracking hostel maintenance requests.
- Connected forms to a Firebase database and showed request status to users.
- Worked with 3 teammates and shipped a public GitHub repo before submission.
- Added demo link and repository link in the project section.

Tip

Use honest labels

If it was a hackathon, call it a hackathon project. If it was unpaid open-source work, call it open-source contributor. If it was a campus club role, say the club name and your responsibility.

Clear labels protect your credibility. Recruiters understand student profiles when the work is explained well.