Your CV is one page. Make it count: the first tech CV guide
By Privatus Cosmas
2026-10-27
https://depriver.tech/blog/first-tech-cv/

What a lecturer's red pen would mark on a student CV, the seven sections in the right order, how to write projects with impact, why FPT counts as experience, and the checks before you hit send.

Your CV gets you the interview, so it has to do its job in a few seconds. Here's what a lecturer's red pen would mark on a typical student CV, and how to fix every mark. *CV ya kwanza, ifanye vizuri.*

## What the red pen sees

- **Personal details nobody needs:** date of birth, religion, marital status, P.O. Box. *Si lazima.*
- **A generic objective:** "To work in a reputable company that will help me grow." *Kila mtu anasema hivi.*
- **Non-tech skills:** "MS Office, Internet, Hard working." *Skills za tech?*
- **No projects at all.** *Hapa ndipo pa muhimu!*

The fix: say less about yourself on paper, and show more proof of what you can do.

## Seven sections, in this order

1. **Header:** name, phone, email, location, GitHub and LinkedIn
2. **Summary:** two lines on who you are and what you build
3. **Skills:** the languages, frameworks and tools you've really used
4. **Projects:** your strongest proof, with links
5. **Experience:** FPT, internships, gigs and volunteering
6. **Education:** most recent first, with your GPA if it's good
7. **Referees:** two or three, with their permission

As a student, your projects *are* your experience, so put them early.

## Header and summary

Use a professional email (name.surname@…, not boy_mtundu99@…). Your summary should say what you build, not what you want. For example:

> *Computer Science diploma graduate who builds web apps for small businesses with Laravel and React. Shipped a POS used daily by a shop in Mbeya.*

That's an example, so use your own real details. Never copy someone else's CV.

## Projects: show impact, not just tasks

- ❌ "Did a website for a shop."
- ✅ "Built a sales and stock app for a shop in Mbeya with Laravel and MySQL. Used daily by 3 staff; stock errors dropped in the first month."

**The formula:** Built [what] for [who] using [tools], so that [result]. Then add the GitHub or live demo link. Use real numbers only, and never invent results.

## Your FPT is experience

Write it like a job: your role, the company, the months, and three bullet points starting with a verb (Built, Configured, Fixed, Led). Use your logbook so the details are accurate. Gigs and volunteering count too.

## Before you hit send

- **One page.** Two pages only if you have real work experience.
- **Save it as a PDF**, because Word files break on other computers.
- **Name the file properly:** Amina-Juma-CV.pdf, not CV final(2).pdf.
- **No typos.** Read it out loud, then ask a friend to read it.
- **Referees have agreed.** Ask your FPT supervisor or lecturer first.
- **Tailor it** to the skills in each job advert.

**What's the hardest part of your CV?** Niambie kwenye comments, and share this with a classmate who's job hunting.

Slide captions
1. Your CV is one page. Make it count. CV ya kwanza, ifanye vizuri.
2. What the red pen sees: personal details nobody needs, a generic objective, no tech skills, no projects.
3. Seven sections in this order: header, summary, skills, projects, experience, education, referees.
4. Header and summary: easy to call, easy to remember.
5. Projects: show impact, not just tasks. Built [what] for [who] using [tools], so that [result].
6. Your FPT is experience. Write what you did, starting with a verb.
7. Before you hit send: one page, PDF, a proper file name, no typos, referees agreed, tailored.
8. What's the hardest part of your CV? Niambie kwenye comments.
