1-page IT CV or multi-page — this seemingly simple question determines whether HR will call you or quietly drop your application. This article shares a real developer’s experience after rebuilding their CV using AI, discovering the harsh truth about how HR actually reads resumes in 2026.
Have you been sending out dozens of CVs with no calls back? Did you use ChatGPT or AI tools to create a detailed 3–4 page resume packed with keywords, only to find your response rate dropped compared to your old simple CV? This isn’t a skill problem. It’s the ATS-vs-Human trap that countless IT freshers and junior developers fall into in 2025–2026.
Table of Contents
- 1. Why AI-generated long CVs get brutally rejected by HR
- 2. The truth about how HR reads a CV in 10 seconds
- 3. What a proper 1-page IT CV for 2026 should include
- 4. How to use AI correctly — not letting it make all the decisions
- 5. Real case study: 3-page CV vs 1-page CV
- 6. 6 most common IT junior CV mistakes and how to fix them
- 7. FAQ — Common questions about IT CVs
1. Why AI-Generated Long CVs Get Brutally Rejected By HR
In 2024, AI tools like ChatGPT, Rezi, and Kickresume became widespread, with millions of job seekers using them to “upgrade” their CVs. The results looked impressive on paper: keywords everywhere, dense bullet points, each project described in 5–6 lines of technical detail. A clean 1-page CV ballooned into 3–4 pages.
The problem is that a CV’s journey from your hands to the HR’s desk passes through two completely different screening stages — and you need to pass both.
1.1. Stage 1: ATS — the robot that reads keywords
Most companies with 50+ employees in Vietnam now use an Applicant Tracking System (ATS) to filter CVs automatically. ATS scans for keywords, technical skills, school names, and years of experience, then assigns a score. CVs without enough keywords from the job description get filtered out before HR ever sees them.
This is why people think “just stuff in keywords” — and AI is very good at stuffing keywords. But passing ATS doesn’t mean you’re done. That’s only the parking gate.
1.2. Stage 2: HR — a human reading in 10–12 seconds
After ATS filters, the remaining stack of CVs reaches HR. A typical recruiter processes 200–400 CVs per week across all open positions. They don’t read — they skim. Research from major recruiting platforms shows HR spends an average of only 10–12 seconds per CV in the initial screening round.
When your CV is 3–4 pages of dense text and HR can’t immediately find what they need — school, years of experience, main tech stack, notable projects — the next click is “Reject”. Not because you’re underqualified, but because your CV didn’t respect their time.
2. The Truth About How HR Reads A CV In 10 Seconds
To understand why a 1-page CV wins, you need to know what HR actually looks at when skimming an IT CV:
2.1. The order HR scans through
- Name + Target position — must be immediately clear in the header
- School + Major — many companies have filters by school or GPA
- Years of experience + Last company — to gauge your current level
- Main tech stack — React/Vue? Laravel/Spring Boot? — does it match the JD?
- Notable projects — project names, tech, metrics if any
- GitHub / Portfolio link — the only real evidence of your skills
HR wants to find all 6 of these on the first page, within 10 seconds. If your education is on page 2, your tech stack is buried under 2 paragraphs of self-introduction, and projects are lost in 30 technical bullet points — you’ve eliminated yourself.
2.2. Long CVs don’t prove more competence
There’s an interesting paradox: a 3–4 page CV often makes HR more suspicious, not more impressed. When a junior developer has a CV as long as a 10-year senior, the first question HR thinks is: “Did you actually do all of this, or did AI write this for you?” This is the reverse trap of over-inflating a CV with AI tools.
3. What A Proper 1-Page IT CV For 2026 Should Include
One A4 page — around 600–700 words — sounds thin, but it’s enough to hold everything HR needs to decide to call you in for an interview. Here’s the recommended structure for IT freshers and juniors (0–3 years of experience):
3.1. Header — Contact and identity information
- Full name + target position (e.g. Nguyen Van A — Frontend Developer)
- Phone number + professional email
- GitHub URL (mandatory for devs) + Portfolio if available
- LinkedIn (optional but recommended)
3.2. Summary — 2–3 lines, not an essay
Write 2–3 lines describing who you are, your main stack, and what you’re looking for. Don’t write sentences like “I am a dynamic, hardworking person with good teamwork skills…” — HR reads that 50 times a day and skips it instantly. Instead: “Fresher Frontend Developer with React + TailwindCSS experience, built 2 side projects with 1,000+ real users. Seeking a product company role to deepen system design knowledge.”
3.3. Technical skills — Clear tech stack, no inflation
Only list what you can actually use. Group into 2–3 short sections: Frontend / Backend / Tools & Others. Don’t list 30 technologies where 20 of them you’ve only “heard of”.
3.4. Experience / Projects — The most important section
For freshers without formal work experience, your projects are everything. For each project, write in this structure: Project Name — Tech Stack — Role — Result/Impact. Example:
- E-commerce Dashboard — React, Node.js, MongoDB — Fullstack Developer — Built an order management system for an online store with 500+ SKUs, reaching 200 DAU in the first month.
Just 2–3 projects like this is enough. A few projects with real metrics outweigh 8 vaguely described projects any day.
3.5. Education — Concise, complete
School name + Major + Graduation year + GPA (if 3.0/4.0 or above). No need to list every course.
4. How To Use AI Correctly — Not Letting It Make All The Decisions
AI isn’t the problem. Using AI the wrong way is. Here’s how to combine AI and your own judgment to build the right IT CV:
4.1. What AI should do: Improve language and ATS compliance
- Use AI to paraphrase project descriptions into more professional language
- Use AI to check if your keywords match the JD
- Use AI to write a concise summary from the information you provide
- Use AI to translate your CV to English for international applications
4.2. What AI should NOT decide: Length and structure
- AI doesn’t know whether the company you’re applying to uses ATS or not
- AI doesn’t know if that HR has 10 seconds or 5 minutes to read your CV
- AI tends to “add more” because it’s trained to produce long, detailed outputs
- You must decide: which information stays, which gets cut
Simple rule: After AI builds the draft, your job is to cut 50% of the content. Keep only what’s genuinely valuable. If after cutting it’s still over 1 page — cut more.
5. Real Case Study: 3-Page CV Vs 1-Page CV
This story comes from the direct experience of a Fullstack Developer with 3+ years working on real-world projects (Kia Vietnam, THACO, systems with 10,000+ DAU).
5.1. Results with the old 1-page CV (before AI rebuild)
- CVs sent in one month: 15
- HR calls received: 8–10
- Response rate: ~60%
- Characteristics: Simple 1-page format, clear tech stack, 3 projects with metrics
5.2. Results with the new 3-page AI-rebuilt CV
- CVs sent in one month: 20
- HR calls received: 3–4
- Response rate: ~15–20%
- Analysis: CV passed ATS but was rejected by HR for being too long, hard to find key information
5.3. Results after returning to a 1-page CV (with refinements)
- CVs sent in one month: 15
- HR calls received: 9–11
- Response rate: ~65–70%
- Key change: retained ATS keywords from the AI version, compressed content to 1 page, rewrote summary to be more concise
The takeaway: AI optimizes keywords (for the ATS stage), but humans must optimize layout and length (for the HR stage). Use the right tool for the right job.
6. 6 Most Common IT Junior CV Mistakes And How To Fix Them
Mistake 1: Summary full of generic phrases
Wrong: “I am a dynamic, hardworking individual with strong teamwork skills…” — Right: Write 2 specific lines: your main stack + type of projects you’ve done + what you’re looking for. Nothing more.
Mistake 2: Listing skills with no evidence
Writing “Proficient in React, Vue, Angular, Spring Boot, Laravel, Django…” but none of the listed projects use Angular or Django. HR will ask directly in the interview and you’ve set your own trap. Only list what you’ve actually used in the projects listed on your CV.
Mistake 3: Project descriptions with no metrics
“Built an e-commerce website for a client” — this says nothing. Replace it with: “Built a B2C e-commerce site for a fashion store, reaching 500 orders/month within the first 2 months, integrated VNPAY and MoMo payments.” Specific numbers make a complete difference.
Mistake 4: No GitHub or an empty GitHub
This is a fatal mistake for IT freshers. GitHub is your only real portfolio. If your GitHub only has a few cloned tutorial repos, don’t include the link. Instead, create at least 1–2 real projects with a clear README before applying.
Mistake 5: Not customizing the CV for each JD
Sending the same CV to 30 companies is the fastest way to get rejected. Each JD has its own tech stack and requirements — adjust your summary and skills section to highlight exactly what that JD needs. It takes 5 minutes but significantly improves your callback rate.
Mistake 6: Using a pretty Canva template that doesn’t pass ATS
Many Canva templates use 2-column layouts, embedded images, and complex graphic elements. ATS reads these files row by row, not column by column, causing information to get scrambled or lost entirely. For companies using ATS, use a simple, single-column template with standard fonts, exported as a clean PDF without complex graphics.
7. FAQ — Common Questions About IT Junior CVs
What should an IT fresher with no formal work experience put in the experience section?
List personal projects, capstone/graduation projects, internship experience (even part-time), or side projects you’ve built. The key is having a specific tech stack and measurable outcomes. Don’t leave the experience section blank — rename it “Projects” or “Real-World Projects” instead of “Work Experience”.
Should an IT CV be in Vietnamese or English?
It depends on the company. Startups, outsourcing companies, or companies with international clients typically require English. Vietnamese domestic companies usually prefer Vietnamese. If unsure, prepare both versions. For LinkedIn applications, use English.
Should a low GPA be included in the CV?
If your GPA is below 3.0/4.0, it’s generally better to leave it out. Instead, compensate with real projects, a GitHub profile with regular activity, or relevant certifications (AWS, Google Cloud, technical certs). Practical projects matter more than grades in IT hiring.
Should an IT CV include a photo?
In Vietnam, including a photo is common and accepted. However, for companies with international exposure or startups, you can skip it — a photo won’t get you hired, but a poor photo can hurt your chances. If you do include one, use a professional headshot: white or grey background, business attire.
How should you test your CV before sending it out?
Three quick checks: (1) Ask someone outside IT to read it for 10 seconds, then summarize what you do — if they can’t, restructure it; (2) Paste your CV into a free ATS scanner like Jobscan or Resume Worded to check keyword score; (3) Open the PDF on your phone — if you need to zoom or scroll sideways, the layout needs adjustment.
Summary And Next Steps
A 1-page IT CV isn’t a “lazy” CV — it’s a CV that respects how the real hiring process works. AI is a great tool for keyword optimization and language polish, but you must control the length and structure. The most important lesson: you pass ATS to reach HR, but HR is the one who decides whether you get the interview call — and they only have 10 seconds.
If you’re preparing for your next interview round, don’t miss the articles on IT junior interview tips A–Z and 2026 IT salary benchmarks by role and experience on khaizinam.io.vn to prepare as thoroughly as possible.
Author: Nguyen Huu Khai
21/04.2026