GitHub portfolio and LinkedIn profile: how developers get noticed

Before an interview, many recruiters and engineers will search for you. Your GitHub, LinkedIn and a small portfolio site are often the first evidence of what you can do. The goal is not to look busy. It is to make good work easy to find and understand.

What employers look for

In a quick look they ask:

• Can this person build and finish things?
• Is the code readable, and are the projects explained?
• Do they communicate clearly?
• Are they active and learning?
• Is the information consistent with the resume?

Quality beats quantity. Three good projects are better than thirty abandoned repositories.

Part 1: your GitHub profile

Profile basics

• Use a real photo or a clean avatar, your name, a short bio (role and interests), location (city or country is enough) and a link to your portfolio or LinkedIn.
• Choose a professional username. Avoid names you will regret.
• Create a profile README by making a repository named exactly like your username. Keep it short: who you are, what you are learning, your best projects with links, and how to contact you. Skip walls of badges.

Pin your best 4 to 6 repositories

Pin projects that are complete, working and well explained. Hide or archive old experiments and tutorial copies, or keep them out of the pins.

Write a great README

The README is the front page of every project. Include:

1. What it is in one or two sentences, and why you built it.
2. A screenshot or demo GIF, plus a live link if deployed.
3. Features and the tech stack.
4. How to run it: prerequisites, install and start commands, environment variables (with an example file, never real secrets).
5. How to test it.
6. Notes on design decisions or challenges you solved (this shows thinking).
7. License and contact (optional).

Show good engineering

• Meaningful commit messages and a commit history that tells a story.
• Tests and a CI badge (GitHub Actions) where reasonable.
• A clear folder structure and sensible naming.
• A .gitignore, and no committed secrets (API keys, passwords, .env). Check your history. Leaked keys on a public profile look careless and can be abused.
• Issues or a simple roadmap, and use of branches and pull requests in bigger projects.

What makes a strong project

Pick projects that solve a real problem, even a small one: a tool you use, a local community need, a dashboard for public data. Add the parts real software has: authentication, a database, validation, error handling, tests and deployment.

Avoid portfolios made only of tutorial clones (to-do list, weather app, calculator) with no changes. If you build one, extend it with your own features.

Contribute and stay active

• Small open source contributions (documentation fixes, bug fixes, tests) show you can work with other people's code and review.
• Regular activity helps, but do not fake it. Do not game the contribution graph.

Part 2: a simple portfolio site

A personal site is optional but useful, especially for front-end roles.

• Keep it fast, simple and mobile friendly. Content matters more than effects.
• Sections: short intro, projects (screenshot, description, tech, links), skills, resume download and contact.
• Host it free on GitHub Pages, Netlify, Vercel or Cloudflare Pages. A custom domain looks professional.
• Make sure every link works and the site loads quickly.
• Add a short case study for one or two projects: the problem, your approach, what went wrong, the result.

Part 3: your LinkedIn profile

LinkedIn is where recruiters search by keywords.

• Photo: clear, friendly, professional background.
• Headline: more than a job title. Example: "Backend developer | Node.js, PostgreSQL, Docker | Open to junior roles". Include keywords you want to be found for.
• About: three or four short paragraphs: who you are, what you build, your strengths, and what you are looking for. Write in first person, plainly.
• Experience and projects: use the same achievement-style bullets as your resume, with links to work.
• Skills: list relevant ones, and ask colleagues or classmates for endorsements and short recommendations.
• Education, certificates and volunteering.
• Set a custom profile URL and turn on the setting that signals you are open to work (choose who can see it).
• Keep it consistent with your resume and GitHub. Mismatched dates or claims raise doubts.

Use LinkedIn actively

• Connect with classmates, colleagues, engineers and recruiters, with a short personal note.
• Share what you learn: a project write-up, a short lesson, a useful article with your own view. Quality and consistency matter more than volume.
• Comment helpfully on others' posts.
• Follow companies you like and watch for their job posts and referrals.

Part 4: write and share

Writing helps you learn and gets you noticed. Publish short posts on a blog, DEV, Medium or LinkedIn: how you built something, a bug you solved, a comparison you researched. Link them from your profiles.

Safety and privacy

• Do not publish private company code, customer data or secrets, and respect NDAs and licences.
• Be careful sharing personal details (home address, phone number). Use a professional contact email.
• Beware of scams: fake recruiters asking for money, passwords or sensitive documents. Legitimate employers do not charge for interviews.
• Keep accounts safe with strong passwords and two-factor authentication.

Checklist

1. GitHub: photo, bio, profile README, 4 to 6 pinned projects.
2. Each project: clear README, screenshots, live link, how to run, tests.
3. No secrets in repositories or history.
4. Optional portfolio site with project case studies.
5. LinkedIn: keyword headline, strong About, projects, skills, custom URL.
6. All profiles match your resume.
7. A few posts or write-ups showing how you think.

Takeaway: a few polished, well-explained projects, a tidy GitHub, a keyword-rich LinkedIn and some writing make you easy to find and easy to trust.

---

Career series, Part 1 (getting hired): 2 of 5. Previous: How to write a developer resume that gets interviews.