IT hiring in South Africa moves through two filters: a recruiter or applicant tracking system checking whether you match the technical requirements, and a technical hiring manager checking whether you can actually do the work. A good IT CV passes both. It names the right technologies clearly and then proves, with specific examples, what you built, fixed or improved.
This guide covers software developers, IT support and infrastructure, data and analytics roles, and anyone moving into tech.
The structure that works for IT CVs
- Name, contact details, LinkedIn and GitHub or portfolio links
- Professional profile
- Technical skills, grouped by category
- Professional experience
- Selected projects (essential for juniors, optional for seniors)
- Certifications
- Education
Experienced professionals can move education to the end. Juniors and career changers may want projects above experience if their projects are more relevant than their jobs so far.
Write a profile with a clear technical identity
Hiring managers want to know immediately what kind of technologist you are. Name your role, your main stack and the kind of systems you work on.
Weak: Motivated IT professional with strong problem-solving skills and a passion for technology.
Strong: Backend developer with five years' experience building payment and integration services in C# and .NET on Azure. Comfortable owning features from design to production support, and experienced with SQL Server performance tuning and CI/CD pipelines in Azure DevOps.
The strong version tells a recruiter which roles to match you to, and gives a technical manager reasons to keep reading.
Technical skills: grouped, honest and relevant
A wall of 40 technologies tells the reader nothing about what you are actually good at. Group your skills and list the most relevant first.
| Category | Example entries |
|---|---|
| Languages | C#, TypeScript, Python, SQL |
| Frameworks and libraries | .NET, React, Node.js, Django |
| Cloud and infrastructure | Azure, AWS, Docker, Kubernetes, Terraform |
| Data | SQL Server, PostgreSQL, Power BI, Databricks |
| Tools and practices | Git, Azure DevOps, Jira, automated testing, Agile and Scrum |
| Support and networking | Active Directory, Microsoft 365 administration, Intune, TCP/IP, firewalls |
Only list what you could discuss in a technical interview. If the advert asks for a technology you know well, make sure it is spelt exactly as in the advert, for example "PostgreSQL" rather than "Postgres", so that keyword searches find it. Our ATS-friendly CV guide explains why this matters.
Experience bullets that show impact
The difference between an average and an excellent IT CV is almost always in the experience bullets. Good bullets follow a simple pattern: what you did, with what technology, and what changed as a result.
Before and after: developer bullets
Before:
- Worked on the company's API.
- Fixed bugs and did code reviews.
After:
- Rebuilt the order status API in .NET with caching in Redis, cutting typical response times from around two seconds to under 300 milliseconds during month-end peaks.
- Reviewed pull requests for a team of six developers and introduced a shared checklist that reduced production defects reported by the support desk.
Before and after: IT support bullets
Before:
- Helped users with IT problems.
After:
- Resolved first and second line tickets for around 250 users across three branches, covering Microsoft 365, VPN access, printers and laptop builds.
- Migrated 120 staff to Intune-managed laptops, writing the step-by-step guide that the help desk still uses.
Use real numbers where you have them: users supported, systems migrated, response time improvements, deployment frequency, costs saved. If you do not have exact figures, describe the scale honestly ("for a national retail client", "across five branches") rather than inventing a percentage.
Projects: proof for juniors and career changers
If you are a graduate, a bootcamp or academy learner, or moving into tech from another field, projects are your evidence. Choose two to four that show the skills employers ask for, and describe each like a small job:
- What it does and who it is for
- The stack you used
- What you personally built
- A link to the code or live version
For example: "Municipal outage notifier: a React and Node.js web app that sends users reminders before planned water or electricity maintenance in their area, using published municipal notices. Built the frontend, API integration and notification service; deployed on a free cloud tier." A project tied to a real South African problem is memorable, and it shows initiative.
Make sure linked repositories are tidy. Pin your best work, add a README with setup steps and screenshots, and remove anything half-finished from your pinned list.
Moving into IT from another career
Plenty of people move into tech from teaching, finance, engineering, call centres and retail. If that is you, do not hide your previous career. Frame it as an advantage. A former accountant who now builds reporting tools understands what finance users actually need. A former call centre agent moving into IT support already knows how to calm a frustrated user.
- Lead your profile with the role you are targeting and the technical skills you have built, then mention your background as context.
- Put projects and relevant training above your previous experience.
- In previous roles, highlight anything technical you did: building spreadsheets and reports, supporting colleagues with systems, testing new software or documenting processes.
- Use your cover letter to explain the move in two or three sentences. Our cover letter guide shows how.
Certifications
Certifications carry more weight in some IT areas than others. In cloud, networking, security and support roles, vendor certifications are frequently named in adverts. Examples include Microsoft role-based certifications such as Azure Administrator, AWS certifications, Cisco CCNA, and CompTIA A+, Network+ and Security+.
List the full certification name, the issuing body and the year. If a certification has expired, either renew it or leave it off. If you are studying towards one, you can write "in progress" with an expected date, as long as you are genuinely working on it.
Education
List degrees, diplomas and relevant qualifications with the institution and year. A BSc in Computer Science, a Diploma in IT or an NQF-registered occupational qualification are all worth including. If you completed an IT learnership or a recognised coding academy programme, list it here or under certifications.
Once you have a few years of experience, keep education short and place it at the end.
Contracting and freelance work
Many South African IT professionals work on contract through consultancies or as independent contractors. List each client engagement clearly, with the consultancy and client name where you are allowed to share it, the duration, your role and the stack. If you had many short contracts, group them under one heading to avoid a long, fragmented page.
If a client relationship is confidential, describe the client generically, such as "a large South African bank" or "a national retailer".
Formatting for IT roles
- Use a clean, single-column or simple two-column layout. Recruiters and tracking systems read these reliably.
- Keep technology names in plain text, not logos.
- Avoid tables for layout, text in images, and headers or footers holding important information.
- Two pages is usually the right length. See how long a CV should be.
- Save as a PDF unless an agency asks for Word, which some do so they can add their own branding.
Our CV templates guide shows designs that suit technical CVs.
Where to apply
Tech roles in South Africa are advertised on LinkedIn, PNet, CareerJunction and Indeed, through specialist IT recruitment agencies, and directly on company careers pages. Recruiters often search LinkedIn by skill, so keep your profile consistent with your CV: same job titles, same dates and the same core technologies.
Common IT CV mistakes
- Listing technologies you cannot discuss in depth
- Describing projects with no indication of your own contribution
- Outdated skills at the top of the list
- Jargon-heavy bullets that a recruiter cannot follow; write so a non-technical reader understands the outcome and a technical reader understands the method
- Broken links to GitHub or a portfolio
Quick checklist
- Profile names your role, main stack and the systems you work on
- Skills grouped by category, most relevant first, spelt as in the advert
- Bullets show what you did, with what, and the result
- Projects with links for juniors and career changers
- Current certifications with issuer and year
- Clean layout, plain text, two pages