Resume, GitHub and LinkedIn
Your resume's job is to earn you the interview. Keep it to one page if you have under 5 years of experience.
Structure
- Header: name, email, phone, GitHub, LinkedIn (no photo, no full address).
- Education: degree, college, years, CGPA if strong.
- Skills: languages, frameworks, tools, grouped.
- Projects (and/or experience): 2 to 4 items with impact.
- Achievements: rankings, competitions, open source.
Writing bullet points
Use the pattern action verb + what you did + result.
| Weak | Strong |
|---|---|
| Worked on a website | Built a React and Node.js notes app used by 120 classmates; reduced load time 40% with code splitting |
| Did database work | Designed a normalised PostgreSQL schema (6 tables) and added indexes that cut report queries from 4s to 300ms |
| Participated in a hackathon | Won 2nd place of 80 teams by shipping a working ML demo in 24 hours |
CAUTION
Never list a skill you cannot discuss for 10 minutes. Interviewers pick one line from your resume and go deep.
Projects that stand out
- A live demo link and a README with screenshots, setup steps and design decisions.
- Real users, even a few, or a real data set.
- Tests, CI and a clear commit history.
- See Project ideas and Portfolio and README guide.
GitHub
- Pin your best 4 to 6 repositories with short descriptions.
- Write READMEs; add topics and a license.
- Commit regularly: a consistent history signals habits.
LinkedIn
- A clear headline: "Software developer | Python, React | Open to roles".
- An "About" section of 3 to 4 sentences with your focus.
- Add projects, skills and recommendations; connect with alumni and recruiters.
Checklist
- One page, consistent formatting, exported as PDF
- No typos (read it aloud)
- Every bullet has a measurable outcome where possible
- Links work and repos are public
- File named
FirstName_LastName_Resume.pdf
Loading Comments...