GitHub Profile That Gets You Hired

1. Why Your GitHub Profile Matters

When a recruiter or hiring manager receives your resume, the first thing many of them do is check your GitHub link. A strong profile tells them things a resume can't: that you actually write code, that you finish projects, that you think about documentation, and that you're active in your craft.

In India's engineering placement scene, most students have nearly identical resumes — same CGPA ranges, same listed skills, same "mini project" descriptions. A well-maintained GitHub profile is one of the few things that genuinely differentiates you. It's verifiable proof of work, not just claims.

2. The Profile README

GitHub lets you create a special repo with the same name as your username. Add a README.md to it and it becomes your profile's front page — the first thing anyone sees when they visit your profile.

How to Create It

1. Go to GitHub → New Repository
2. Name it exactly the same as your GitHub username (e.g., if your username is athulkumar, name the repo athulkumar)
3. Check "Add a README file" → Create Repository
4. Edit the README.md — it now shows on your profile

What to Put In It

# Hi, I'm [Your Name] 👋

3rd year ECE student at [College Name], Kerala.
Building things at the intersection of embedded systems and AI.

## 🔧 What I Work With
- **Hardware:** Arduino, ESP32, STM32, Raspberry Pi
- **Languages:** Python, C, C++
- **Tools:** Fusion 360, KiCad, Git, VS Code

## 🚀 Current Projects
- Smart irrigation system using ESP32 + MQTT
- Line follower robot with PID control

## 📫 Reach Me
- LinkedIn: [your-link]
- Email: yourname@college.edu.in

Keep it short. Recruiters spend 10–15 seconds on a profile. One clear paragraph, a skills list, and contact info is enough. Avoid walls of text, excessive emoji, or badges that don't mean anything.

3. The Pinned Repositories Strategy

You can pin up to 6 repositories on your profile. These are the first projects anyone sees. Choose them carefully — they should be your best work, not your most recent.

What Makes a Good Pinned Repo

• Clear name — line-follower-robot beats project1 or ECE302_final
• Filled description — one sentence saying what it does (edit in repo settings)
• Topics/tags added — add relevant tags like arduino, python, iot, robotics
• A real README — see next section
• Actual code — not an empty repo or a single file with no context

4. Writing a Project README That Impresses

Every pinned repository must have a good README. This is what a recruiter reads to understand your project without running your code. Here's a template that works for any engineering project:

# Project Name

One sentence: what this project does and why it's useful.

## Demo
[Screenshot or GIF here — drag and drop an image into the GitHub editor]

## Features
- Feature 1
- Feature 2
- Feature 3

## Tech Stack
- Hardware: ESP32, DHT11 sensor, OLED display
- Software: Python, MQTT, Grafana
- Libraries: PubSubClient, Adafruit_GFX

## How to Run
1. Clone the repo: `git clone ...`
2. Install dependencies: `pip install -r requirements.txt`
3. Flash firmware: open `firmware/` in Arduino IDE
4. Configure WiFi in `config.h`

## What I Learned
Briefly mention one or two things you learned building this.
This shows self-awareness and that you reflect on your work.

## License
MIT

5. The Contribution Graph

The green grid of squares on your profile shows daily commit activity. A consistent graph signals discipline and active development — two things every employer values.

How to Stay Consistent Without Burning Out

• Commit every time you make a meaningful change — even if it's just fixing a bug or updating a README
• Work on documentation on days you don't write code — improving a README still counts as a commit
• Keep one "learning" repo where you push small experiments and notes regularly
• Don't save all your commits for a weekend push — daily small commits look better than weekly dumps

6. What Recruiters Actually Look At

Based on how technical hiring works at Indian product companies and startups, here's roughly what gets checked, in order:

1. Pinned repos — do they look real? Are they named properly?
2. README quality — does this student communicate clearly?
3. Commit history on a repo — was it built gradually or committed all at once the night before?
4. Code readability — are variables named properly? Is there any structure?
5. Contribution graph — are they consistently active?

7. Quick Wins to Do This Week

• Create your profile README today — takes 20 minutes
• Rename any repos called "project1", "assignment2", or "test" to descriptive names
• Add a one-sentence description to every public repo
• Add topics/tags to your top 3 repos
• Write a proper README for your best project using the template above
• Pin your 4–6 best repos (not your most recent — your best)