Career
CV Writing for Fresh Graduates: What Recruiters Actually Look For
The average recruiter spends less than thirty seconds on a first pass of your CV. For a fresh graduate, this feels unfair: how can a life of study be judged in half a minute? But once you accept it, the strategy becomes clear: a CV is not your biography. It is an advertisement with one goal: earning an interview. Everything on the page either serves that goal or takes space from something that does.
The structure that works
For a fresh graduate, one page. Not two. The sections, in order:
- Header: your name, phone, professional email, city, and links to LinkedIn, GitHub, and your portfolio. No photo, no date of birth, no full home address; modern hiring practice in most industries neither needs nor wants them.
- A two-line summary: who you are and what you are looking for. "Software engineering graduate with hands-on experience building web applications in React and Node.js, seeking a junior developer role" is specific, short, and done.
- Projects: for a graduate with no work history, this section replaces experience, and it goes near the top. More on it below.
- Education: degree, institution, years. Include your grade only if it is strong.
- Skills: a plain, honest list of technologies, grouped sensibly. No percentage bars, no star ratings.
Projects are your experience
A common mistake is treating projects as an afterthought: one line, one title. Instead, treat each project the way an experienced engineer treats a job. Give it two or three bullet points that say what you built, what it does, which technologies you used, and where possible, a number: "supports 200 registered users," "reduced page load time by half," "covered by 40 automated tests." Numbers stop the skimming eye in a way adjectives never do.
Include a clickable link to each project. A recruiter who can see your work running in a browser needs far less convincing from the text.
Verbs, not duties
Weak CVs describe duties: "was responsible for the front end." Strong CVs describe actions and results: "built the front end in React, including authentication and a real-time dashboard." Start every bullet with a verb (built, designed, implemented, automated, led, improved) and cut every phrase that could appear on anyone's CV. "Hardworking team player with good communication skills" has appeared on ten million CVs and moved exactly none of them forward.
The mistakes that get CVs rejected instantly
- Typos and grammatical errors. They signal carelessness on the one document you had unlimited time to perfect. Read it aloud, run a spell checker, and have one other person read it.
- An unprofessional email address. coolboy_2004@ email addresses end careers before they begin. Use some form of your name.
- Lying. Inflated skills collapse in the first ten minutes of a technical interview, and the interviewer will not tell you that this is why you were rejected. Honest and modest beats impressive and false.
- One CV for every job. You do not need to rewrite it each time, but reorder your skills and projects so the most relevant ones for that particular job appear first. Ten tailored applications outperform fifty identical ones.
- Overdesigned templates. Many companies use software that reads CVs automatically, and elaborate multi-column designs with graphics confuse it. A clean single-column layout with clear headings survives both robots and humans.
Send it as PDF, name it properly
Always export to PDF so your formatting survives every device, and name the file like a professional: Firstname-Lastname-CV.pdf. A file called final_cv_new2(1).pdf tells its own small story, and not a good one.
Finally, remember what the CV is for. It does not need to prove you are the best candidate; no document can. It needs to make someone curious enough to meet you. Keep it short, concrete, and honest, and it will do that job.