What to Include
| Element | Why It Matters |
|---|
| 3-5 Featured Projects | Recruiters spend ~90 seconds on portfolios — make those count |
| Case Studies | Problem → solution → impact with metrics. Shows thinking, not just output |
| GitHub Profile | Pinned repos, clean READMEs, contribution activity |
| Personal Site | Custom domain shows initiative; keep it simple and fast |
Case Study Framework
| Section | Content |
|---|
| Problem | What was broken? 1-2 sentences with context |
| My Role | What did YOU specifically do? Be precise — not "we built" |
| Solution | Architecture decisions, tradeoffs made, technologies chosen and why |
| Impact | Metrics: "reduced latency 40%, saved $50K/year, handled 10x traffic" |
| Lessons | 1-2 things you would do differently — shows growth mindset |
Platform Checklist
| Platform | Must-Haves |
|---|
| GitHub | Profile README, pinned repos with descriptions, clean commit history |
| LinkedIn | Featured section with projects, consistent with portfolio |
| Personal Site | Custom domain, mobile responsive, fast load, clear navigation |
Common Mistakes
| Mistake | Fix |
|---|
| Too many projects | Curate to 3-5 best — remove anything weak |
| No metrics | Every case study needs at least one number |
| Vague role claims | Specify exactly what you built, designed, or led |
Pro Tip: Quality over quantity — 3 deep case studies beat 15 screenshots. For each project, answer: what was the problem, what did YOU do, what was the impact?