"No experience" does not mean "nothing to show." It means your experience does not come with job titles yet. A student CV translates projects, coursework, and skills into the language employers scan for.
The mindset shift
Employers hiring juniors are not expecting a work history. They are looking for signals: can this person do the work, learn fast, and communicate? Every section of your CV should answer one of those.
Structure that works
Contact info, a two-line summary, skills, projects, education, then anything extra (volunteering, languages, certifications). That order puts proof before pedigree — exactly right for someone without job titles.
Projects are your experience section
Give projects the same treatment jobs get: name, one-line description, 2–3 bullet points of what you built and the result. "Built a study-planner web app used by 40 classmates; implemented auth and a PostgreSQL backend" tells an employer everything.
The skills section, done right
Group by category (Languages, Tools, Concepts) and only list what you could discuss in an interview. Ten honest skills beat twenty aspirational ones — interviewers probe, and bluffing collapses fast.
The one-page rule
One page. Recruiters spend under a minute on a first scan. If it does not fit, you are listing too much — cut ruthlessly. White space is a feature.
Tailor every application
Mirror the job post's keywords honestly (only skills you have), and reorder projects to lead with the most relevant one. A tailored one-pager beats a generic two-pager every time.
Mistakes to avoid
Typos, unprofessional email addresses, walls of text, and listing every workshop you ever attended. And never invent experience — background checks and technical interviews exist, and getting caught ends the opportunity instantly.
