How to Present GitHub on Your CV: Technical Projects That Get Read

## How to list GitHub so humans actually click Direct answer: Never paste a bare github.com/username link in the header. Add a dedicated "Technical Projects" section, hyperlink project titles, and write short bullets using What + How + Impact. ## Format each project like a micro-job For each project include: - A hyperlinked title (Project Name → https://github.com/you/project) - Two-to-three bullets using the What + How + Impact formula (focus on architecture and metrics, not features) - A single-line tech stack and a link to a hosted demo Example bullet: "Built a serverless invoice processor (What) using AWS Lambda and Node.js (How), reducing manual invoicing errors by 86% and cutting processing time from 4 hours to 30 minutes (Impact)." Recruiters and engineers scan differently; this structure shows both the implementation and the value. ## Make the profile README work like a cover letter Your profile README is dynamic real estate. Use it to: - Explain your engineering philosophy in one paragraph - Surface your 3–6 pinned projects with one-line hooks - Link a demo video and short case study for the headline repo - Use GitHub Actions for small automations (e.g., update a live blog feed) to show CI familiarity A readable README often converts curiosity into an interview question. ## Silent competence: automation and maintenance signals Enable Dependabot or automated security updates on pinned repos. Merged Dependabot PRs show active maintenance and security awareness without you having to state it. Small signals like tidy commit messages, CI badges, and passing tests in the README indicate professional standards. ```copy Technical Projects section template to copy: - Project Name (hyperlink to repo) — Tech: Node.js, Express, PostgreSQL | Demo: hosted.example.com • Built invoice-processor microservice to normalise vendor data (What) using Lambda and SQS (How), reducing manual corrections by 86% (Impact). • Implemented automated integration tests and CI pipeline; coverage 78%. - DataViz Dashboard (link) — Tech: React, D3 | Demo: dashboard.example.com • Architected modular charting components (What) to support dynamic datasets (How), improving analyst time-to-insight by ~50% (Impact). ``` - [ ] Replace naked GitHub URL in the header with a Technical Projects section - [ ] Hyperlink project titles, include tech stack and demo links - [ ] Write bullets with What + How + Impact focusing on architecture - [ ] Add a short, purposeful profile README and a demo video for the main repo - [ ] Enable Dependabot and display CI/test badges where appropriate *For more on CV formatting, explore our [Format & Layout](/format-and-layout) insights.*