What you will learn
- Assemble a complete "candidate package" — resume, GitHub, LinkedIn, and portfolio — into a consistent, recruiter-ready state
- Cross-reference every item across all platforms for consistency
- Build a personal landing page or Notion portfolio (optional but high-impact)
Why this matters
A recruiter who likes your resume will check your GitHub in the next 30 seconds. If your GitHub profile tells a different story — different projects, missing repos, no README — you lose credibility. The "candidate package" is the full set of materials that a recruiter sees across platforms. Consistency between them is what separates candidates who seem professional from candidates who seem scattered.
What is a candidate package?
It is the complete set of materials a recruiter or hiring manager encounters:
- Resume (PDF) — the entry point
- GitHub profile — where they verify your projects
- LinkedIn profile — where they find you or verify your identity
- Portfolio site or Notion page (optional) — a polished showcase
- Cover letter template (optional) — for companies that request one
This capstone ties together everything from the previous lessons and produces a final, consistent package.
Step 1: The consistency audit (15 minutes)
Open your resume, GitHub, and LinkedIn side by side. Check:
| Check | Resume | GitHub | |
|---|---|---|---|
| Name spelled identically | [ ] | [ ] | [ ] |
| Same graduation year | [ ] | [ ] | [ ] |
| Same 3 featured projects | [ ] | [ ] | [ ] |
| Project names match exactly | [ ] | [ ] | [ ] |
| Tech stacks listed match | [ ] | [ ] | [ ] |
| Internship titles/dates match | [ ] | [ ] | [ ] |
| Contact email is the same | [ ] | [ ] | [ ] |
| GitHub link on resume works | [ ] | N/A | [ ] |
| LinkedIn URL is customized | [ ] | [ ] | [ ] |
Fix every mismatch before moving on.
Step 2: Resume final pass (15 minutes)
Using what you learned in Lessons 1, 5, and 6:
- Header: Name, city, email, phone, GitHub link, LinkedIn link — all on one line
- Projects section: Your top 3 projects with 2-3 bullets each, following Action-Architecture-Outcome
- Experience section: Internships/freelance with outcome-driven bullets
- Education: College, degree, CGPA (if above 8.0), graduation year
- Skills: 8-10 skills you can defend in an interview
Final checks:
- PDF is exactly one page
- File is named
FirstName_LastName_Resume_2026.pdf - No typos (run it through Grammarly or ask a friend)
- Links are clickable in the PDF
- Printed version is readable (no text smaller than 10pt)
Step 3: GitHub final pass (10 minutes)
Using what you learned in Lesson 2:
- Profile photo is a clear headshot
- Bio is one line with your role, stack, and college
- Profile README is concise (no badge walls)
- Top 3 projects are pinned
- Each pinned repo has a complete README with:
- One-sentence description
- How to run locally
- Key technical decisions
- Screenshot or demo link
- Recent commit activity (at least one commit in the last 30 days)
Step 4: LinkedIn final pass (10 minutes)
Using what you learned in Lesson 3:
- Headline uses the formula:
[Role] | [Skills] | [College] '[Year] - About section leads with what you build, links to GitHub
- Experience entries have 2-3 bullet points each
- Skills section has 10 relevant technical skills
- Featured section pins your best project and GitHub profile
- Custom URL:
linkedin.com/in/firstname-lastname-short
Step 5: Portfolio site or Notion page (optional, 15 minutes)
A portfolio site is not required, but it adds a professional layer. Two approaches:
Option A: Simple Notion page
Create a Notion page with:
- Your name and one-line bio
- Links to resume PDF, GitHub, LinkedIn
- Your 3 projects with descriptions, screenshots, and links
- Make it public and use a clean URL via Notion's share settings
Option B: Personal site (if you have time)
Use a static site generator (Next.js, Astro, or even plain HTML):
- Deploy on Vercel or Netlify (free)
- Custom domain (
firstname.devorfirstname.tech, ~Rs 800/year) - Include: About, Projects, Resume PDF download, Contact
- Keep it minimal — no animations, no dark patterns, no "loading" screens
What NOT to build:
- A portfolio site that took more time than your actual projects
- A template site that looks identical to 1,000 others
- A site with broken links or placeholder content
Step 6: The external review (10 minutes)
Send your complete package to 2 people for review:
- A peer — another CS student who will check for obvious errors, broken links, and consistency
- Someone non-technical — a friend or family member who will tell you if your About/bio makes sense to a normal human
Ask them specifically:
- "Can you tell in 10 seconds what I do and what I'm looking for?"
- "Do the project descriptions make sense to you?"
- "Are there any broken links?"
The candidate package checklist
RESUME
[ ] One page PDF, properly named
[ ] 3 projects with strong bullets
[ ] All links clickable and working
[ ] Proofread by at least one other person
GITHUB
[ ] Professional photo and bio
[ ] 3-6 pinned repos with complete READEs
[ ] Commits within the last 30 days
[ ] Profile README (concise, no fluff)
LINKEDIN
[ ] Optimized headline with role + skills + year
[ ] About section with project links
[ ] 10 technical skills added
[ ] Featured section with best work
CONSISTENCY
[ ] Same name, year, projects across all platforms
[ ] All cross-links work (resume → GitHub, LinkedIn → GitHub)
[ ] Project names and tech stacks match everywhere
OPTIONAL
[ ] Portfolio site or Notion page
[ ] Cover letter template saved
## Cover letter template (for companies that require one)
Dear [Hiring Manager / Team],
I'm a [year] CS graduate from [College] applying for the [Role]
position at [Company]. I'm drawn to this role because [specific
reason — a product feature, a tech blog post, a team focus area].
In my recent work, I [one strong project/internship sentence with
a specific outcome]. This experience taught me [skill directly
relevant to the role].
I've also built [second project], where I [technical decision
or challenge], which connects to [aspect of the job description].
My resume, GitHub, and project demos are linked below. I'd welcome
the chance to discuss how my skills align with your team's work.
Best,
[Name]
[Email] | [GitHub] | [LinkedIn]
---
Keep it under 200 words. One page. No fluff.Try it yourself
- Open your resume, GitHub profile, and LinkedIn in three browser tabs
- Run the consistency audit table from Step 1 — fix every mismatch
- Complete the final pass for each platform (Steps 2-4)
- Optional: Create a Notion portfolio page (Step 5)
- Send the complete package to 2 people for external review (Step 6)
- Set a calendar reminder for 30 days from now to check that your GitHub still has recent activity
Common mistakes
- Inconsistent project names — your resume says "SmartSearch" but GitHub says "smart-search-app" and LinkedIn says "AI Search Tool." Pick one name and use it everywhere.
- Dead links — a GitHub link on your resume that 404s is worse than no link. Test every link in your final PDF.
- Spending a week on a portfolio site — if your projects are not strong, a beautiful portfolio site just showcases weak work beautifully. Fix the projects first.
- Skipping the external review — you are blind to your own mistakes after staring at your resume for hours. A fresh pair of eyes catches things instantly.
- Setting and forgetting — your candidate package needs updates every month. New project? Update everywhere. New internship? Update everywhere. Stale profiles lose interviews.
Quick quiz
Q: A recruiter sees your resume, likes it, and clicks your GitHub link. Your GitHub profile has a different set of projects than your resume lists. What happens?
How to explain it in an interview
"I maintain a consistent candidate package across my resume, GitHub, and LinkedIn. The same 3 projects appear on all platforms with matching names, tech stacks, and descriptions. Every project links to a GitHub repo with a README that explains how to run it and what technical decisions I made. I update all three platforms whenever I ship something new."
Checklist
- Completed the consistency audit — all platforms match
- Resume is final: one page PDF, proper naming, all links working
- GitHub is final: photo, bio, pinned repos, READMEs complete
- LinkedIn is final: headline, about, experience, skills, featured
- Sent package to 2 people for external review
- All cross-platform links tested and working
- Set a monthly reminder to update the package