GitHub & Projects
Your GitHub Profile README Is Your First Impression — Make It Count
Recruiters decide in seconds from your profile README and pinned repos. What to put above the fold, how to pin, and why honesty beats hype.
When someone checks out your work online, the first thing they usually see is not your best project. It is your GitHub profile. And if you have a profile README — that pinned introduction at the top of your profile — it is your first impression, delivered in about ten seconds. Most students either leave it empty or fill it with a wall of badges and buzzwords. Both are wasted opportunities. A good profile README does one job: it makes a stranger want to look at your actual work.
Think about who reads it. A recruiter scanning profiles, a senior developer deciding whether to answer your message, a potential collaborator sizing you up. None of them will read your code first. They will read your README, glance at your pinned repositories, and decide in seconds whether you are worth a second look. Everything below the fold is a bonus. Everything above it is the pitch.
Above the fold: the five things that matter
Above the fold means what is visible without scrolling: your first lines and the top of your README. Put these five things there, in this order:
- Who you are, in one line. Name, what you study or do, and what you build. Not a job title you do not hold. A CS student building AI tools is a stronger line than an inflated title nobody believes.
- What you are working on now. One current project, with a link. Current work signals that you are active, not archived.
- Your best proof, linked. One or two projects you are proud of, with one line each on what they do. Not a list of everything. Your best two.
- How to reach you. An email or a LinkedIn link. A profile with no contact path is a dead end for the exact people you want to hear from.
- What you are looking for, if anything. Internships, collaborators, open-source contributions. One line is enough, and it tells the reader what to do next.
Everything else — skills, stats, long tool lists — belongs below the fold. The fold is for identity and proof. The rest is reference material for people who are already interested.
Pinning: your six best, not your six latest
GitHub lets you pin repositories to your profile, and most students pin whatever they touched most recently. Pin strategically instead. Your pinned repos should be the ones that best represent the developer you want to be hired as. A good pin set has variety: different kinds of problems, different stacks, at least one project with a real README and a working demo.
And audit the pins honestly. Click each pinned repo as a stranger would. Does the README explain what it is in thirty seconds? Does it say how to run it? Is there a screenshot or demo link? A pinned repo with an empty README actively hurts you — it tells the visitor that your best work has no explanation. Either write the README or unpin the repo. There is no third option that helps you.
Honesty over hype, always
The temptation with profile READMEs is to inflate: exotic titles, vague claims about scale, skills you touched once. Resist it, because the people reading your profile are good at detecting it, and the cost of being caught is higher than the benefit of the claim. A profile that says you built a finance app used by your class is believable and interesting. A profile that implies a startup-scale product with no evidence is a red flag.
The same rule applies to stats widgets and contribution graphs. They are fine as decoration, but they are not proof. Nobody has ever been hired because of a badge wall. People get hired because a reviewer opened a repo, understood the project in a minute, and thought: this person can build. Your README should serve that moment, not distract from it.
What to leave out
- Skill lists longer than your experience. Ten technologies you used once invite ten interview questions you cannot answer.
- Generic motivational quotes. They take up fold space and say nothing about you.
- Every course and certificate. Pick the ones that matter for the roles you want. The rest belong on your resume, not your profile.
- Jokes only you understand. Personality is good. Inside jokes that confuse strangers are not.
- Outdated claims. A line saying you are looking for summer internships, left up in winter, signals that nothing here is maintained.
A structure you can copy
If you are staring at a blank README, here is a structure that works. Keep it short — a good profile README is under a screen and a half:
- One-line introduction: who you are and what you build.
- Currently working on: one project, one link, one sentence.
- Featured projects: two or three, each with a link and a one-line problem statement.
- Skills, grouped: languages, frameworks, tools — only the ones you can defend in conversation.
- Contact: email and LinkedIn, plainly visible.
Write it in your own voice. A README that sounds like you is more memorable than one assembled from templates, and it sets up the rest of your profile to feel like a real person built it. Then maintain it: revisit the README whenever you finish something meaningful, swap in your new best project, and remove claims that are no longer true. A profile README is not a document you write once. It is a living introduction, and it should grow as you do.
Your profile README does not need to impress everyone. It needs to make the right person curious enough to open one repository.
Once the profile reads well, make sure the repositories behind it do too. A strong README on a repo with no explanation is the same mistake one level down — write the project README, add a demo link, and let the profile and the projects tell the same story. For turning those repositories into a full portfolio page, see How to Turn GitHub Repos Into Portfolio Case Studies and ZEVQYN's AI Portfolio Builder.
Before you publish: a five-minute audit
Before you share your profile link anywhere, run a five-minute audit as a stranger. Open your profile in a private browser window, where you are logged out, and read it the way a recruiter would. Does the first screen tell you who this person is and what they build? Do the pinned repositories have READMEs that explain them? Does every link work? This audit catches the most common embarrassments: dead links, stale claims, and pinned repos that looked good from the inside but say nothing from the outside. Small, regular audits beat one big rewrite, because a profile that improves steadily looks alive.
- Links: Click every link on your profile. A dead demo link or a 404 on your portfolio costs more trust than a missing project.
- Freshness: Remove anything tied to a date that has passed, like an old internship search or a completed semester goal.
- Consistency: Your profile, your resume, and your portfolio should agree on who you are. Contradictions make reviewers doubt all three.
- One improvement: Each audit, fix the single weakest pinned repo — usually by writing its README — instead of trying to overhaul everything at once.