Digital
Information technology
Charcoal sidebar with code-style headings.
Accent colour
Software, data, testing
IT CV templates
For developers, testers, data specialists and system operators. Languages, technologies and projects are grouped into separate blocks so readers can take them in quickly.
Technologies grouped by typeLanguages, frameworks and tools are kept separate, never mixed up.Projects with your role and resultsEach project shows which part you built and what it achieved.ATS compatibleA single-column layout with the right keywords so nothing gets missed.
Developer
Programming · Software
Dark left column in command-line teal.
Accent colour
Data
Data analysis
Purple with halftone dots that build up like a chart.
Accent colour
Testing
Software testing · QA
Fresh green with evenly spaced plus signs, easy to scan.
Accent colour
Infrastructure
IT infrastructure · DevOps
Steel blue on a technical grid.
Accent colour
Automation
Automation · Robotics
Deep blue with a large ring in the corner.
Accent colour
Interface
UI/UX design
Screen purple with a tidy, faint dot grid.
Accent colour
Film editing
Film editing · Post-production
Darkroom purple with bold bars like an editing timeline.
Accent colour
Cybersecurity
Cybersecurity · SOC
Black and cyan like a monitoring screen.
Accent colour
AI & machine learning
AI · Machine learning · Data science
Modern low-poly purple with raised section cards.
Accent colour
Game developer
Game development · Unity
Bright orange, pixel confetti and a dark right column.
Accent colour
Writing an IT CV that tech leads notice: stack, projects, GitHub and what to leave out
At a software company, your CV goes past two different readers: HR looks for keywords and years of experience, while the tech lead looks for the right stack at the right level, projects with a clear role, and a GitHub link to see how you write code. Việc Hot has 11 IT CV templates for developers, testers, data roles and systems operations. The sections below cover how to arrange your skills, how to write up projects and when you need an English CV.
Who reads an IT CV and what they look at first
The first round is usually HR or screening software: they search for the exact technology names in the job post (Java, Spring Boot, React, AWS), years of experience and level. So write the names in full: "JavaScript, TypeScript" rather than just "JS/TS", "PostgreSQL" rather than just "Postgres", and add the English job title if the post is in English.
The second round is the tech lead, the person you will be working with. They skip the career objective, go straight to projects and skills, and silently ask three questions: does the stack match, which parts did you build yourself rather than just "take part in", and is there any code they can look at.
Group skills by category and level
A list of 30 technologies shows that you do not know where your strengths lie. Split them into groups of three to six items each, put what you use every day first, and add the number of years or a note saying "learning":
| Position | Skill groups to include | What the reader looks for |
|---|---|---|
| Developer | Skill groups to includeLanguages; frameworks; databases; Git, Docker, CI/CD | What the reader looks forWhether you understand deployment and testing |
| Tester | Skill groups to includeSelenium, Playwright, Postman, JMeter; SQL; Jira | What the reader looks forWhether you have automated testing on any project |
| Data | Skill groups to includeSQL, Python; Power BI or Looker Studio; Airflow, dbt | What the reader looks forWhich pipelines or reports are actually in use |
| Operations, DevOps | Skill groups to includeLinux; Docker, Kubernetes; AWS or Azure; Terraform | What the reader looks forAWS certifications, number of systems you have run |
How to write up a project so it is credible
Each project covers five points: name and a one-line description, scale (users, team size), technologies, your role and what you personally did, and measurable results.
A project written up with all five points
Order management system for a chain of 40 building materials stores, about 300 internal users. Node.js (NestJS), PostgreSQL, Redis, Docker, GitLab CI. Role: backend developer in a team of 5; designed the data schema, wrote 40 APIs and a queue-based inventory sync mechanism. Result: inventory sync time between stores cut from 15 minutes to under 1 minute, and stock discrepancies down to under 1% a month.
Experience written as action, figure, result
For each position, the first sentence states the product and team size; the lines that follow say what you did and what changed as a result: "Optimised revenue report queries, cutting page load time from 8 seconds to 1.5 seconds"; "Wrote an automated test suite of 320 cases for the payment flow, catching 27 bugs before release"; "Moved 6 services to Kubernetes, reducing server costs by about a quarter". If you have no measurements, state the scope: number of screens, APIs or users.
GitHub, certifications and English-language IT CVs
Put your GitHub link next to your email address. Pin three or four repositories with a README that explains what the project does and how to run it; unpin empty assignment repositories and forks you have not changed. List only certifications that carry weight in the industry: AWS Certified Cloud Practitioner or Solutions Architect Associate, Microsoft Azure Fundamentals, ISTQB Foundation for testing, Google Data Analytics for data.
Outsourcing companies with foreign clients, product companies with international teams, and posts written in English: an English CV. Domestic companies posting in Vietnamese: a Vietnamese CV, with technology names kept as they are.
Common mistakes in developer and tester CVs
- Listing every technology you have ever heard of.
- Percentage bars such as "Java 85%" and "React 70%".
- Projects with only a name and technologies, without saying which part you did in the team.
- No GitHub link, or repositories last updated three years ago.
Frequently asked questions
List course projects and personal projects with public source code, covering your role, the technologies and the results; a small app that works and has a README is worth more than a list of ten technologies.
No. Software companies in Vietnam and abroad almost never ask for one; use that space for your GitHub and LinkedIn links.
About 10 to 15 items, grouped by category, covering exactly what you could use from your first day. Technologies you have only read about should be marked "learning" or left out.