Information Technology
Examples for software engineers, IT support specialists and data analysts, including how to present projects and technical skills.
Software Engineer CV Example
Developer CVs get filtered on technical skills first, so languages and frameworks need to appear under their exact names. But what separates you from a hundred other applicants who know the same stack is impact: what you built, for how many users, and what got better as a result.
- JavaScript
- React
- Node.js
- REST API
IT Support Specialist CV Example
IT support is a role measured in numbers: how many tickets you close, how fast, and how many are resolved on first contact. A CV that states those metrics immediately outperforms one that just lists operating systems.
- IT support
- troubleshooting
- Active Directory
- CompTIA A+
Data Analyst CV Example
Data analysts don't get hired for knowing SQL; they get hired for turning data into a decision. Your CV needs to show the whole chain: what the data was, what you did with it, and what decision changed as a result.
- SQL
- Python
- Power BI
- Tableau
Technology CVs are screened by software more than any other field, because the skills are product names rather than adjectives. The most common mistake is not a lack of skill but flooding the page with it: a list of twenty technologies reads to an engineer as a claim; five with what you built using them reads as experience.
Give scale, not job title
"Developed interfaces" and "maintained systems" do not separate a beginner from a professional. Scale does: users, requests per day, data volume, tickets closed.
The number tells the reader what class of problem you actually met. Someone who built a service handling fifty thousand requests a day saw problems that someone building the same service for a hundred users did not, and the reader knows it.
- Developer: users and requests, and response time before and after
- IT support: ticket volume, response time, first-contact resolution
- Data analyst: data volume, dashboards, and the decision you changed
- GitHub link at the top — it is opened before your summary is read
Cloud certifications are the most named today
In the Saudi market specifically, AWS and Azure certifications are what technology postings name most often, followed by cybersecurity. A generic "information technology" certificate is not something anyone filters on.
And write the certification exactly as its issuer names it. "AWS Certified Solutions Architect – Associate" matches; "Amazon cloud certificate" matches nothing.
Formatting breaks parsing here more than anywhere
Technology CVs are the most likely to reach for two-column layouts, icons and skill bar charts. Those are precisely what fails machine reading: columns interleave, a chart yields nothing, and an icon is not text.
A bar saying your Python is "eighty per cent" means nothing to a reader or a system. Write years of use, or what you built with it, instead.
Common questions
- How many technologies should the skills section list?
- Five to eight you genuinely know, ordered by relevance to the role. A long list weakens you, because you can be asked about any item on it, and one question you cannot answer casts doubt over the rest.
- Is a GitHub link necessary?
- For developers, yes, and it is the strongest thing on the CV. But an empty repository, or one full of half-finished course projects, is worse than none — two complete projects with a clear readme is enough.
- Do I need a degree to work in tech?
- At banks, Aramco and government bodies, usually yes. At startups and product companies a degree is routinely waived for anyone with work that proves capability. Professional certifications close part of that gap, not all of it.