Repository navigation
[D] CV
Qabas Alkaissi edited this page Jun 16, 2026
·
1 revision
Answer these first:
- What is the story I want this CV to tell?
- What are my 3–5 strongest items? Those go first within each section
- Who is reading this, a professor scanning for 30 seconds, or an admissions committee?
Always:
- Education (GPA if strong, rank if you have it, awards)
- Research experience even if it was one semester, even if it was informal
- Selected projects with tools and a one-line impact statement
- Skills like languages, frameworks, tools.
If you have it:
- Publications, preprints, conference papers anything with your name on it
- Certifications relevant to the field
- Leadership roles (especially if research-adjacent)
Leave out:
- High school anything
- Unrelated work experience (unless it shows something unique)
- Soft skills written as soft skills
The template follows a clean single-column academic format:
| Section | Notes |
|---|---|
| Header | Name, contact, LinkedIn, GitHub, no photo |
| Education | University, degree, GPA/rank, honors |
| Experience | Research first, then other relevant roles |
| Publications | IEEE format, linked if possible |
| Selected Projects | Max 3, tools listed, repo linked |
| Certifications | Only if genuinely relevant |
| Skills | Grouped by category |
- One/Two page(s)
- Reverse chronological within each section, most recent first
- Use action verbs: built, designed, implemented, published, led
- Quantify where you can: "improved accuracy by 12%" beats "improved accuracy"
- Keep formatting consistent: if one date is right-aligned, all dates are right-aligned