Home› Module 18› Resume Guide
Module 18 · Guide 5

Resume Guide

Write a developer CV/resume that gets past ATS systems and makes hiring managers want to call you.

The Purpose of a Resume

A resume has one job: get you an interview. It does not need to tell your life story. It needs to give a hiring manager enough information to decide "this person is worth talking to" in about 10–15 seconds of scanning.

For a junior developer, the resume is less important than the portfolio — but many companies still use it as a filter. Make sure yours does not eliminate you before they see your work.

Resume Structure

A developer resume should be one page (two pages maximum for senior roles). Stick to this order:

  1. Header: Name, email, phone, location (city/country), portfolio URL, GitHub URL, LinkedIn URL
  2. Summary (optional, 2–3 sentences): Who you are, what you do, what you are looking for
  3. Skills: Technical skills grouped by category
  4. Projects: Your best 3–4 projects (more important than experience for juniors)
  5. Experience: Any relevant work experience. Non-tech jobs are fine — transferable skills matter
  6. Education: Degrees, bootcamps, certifications

Writing Each Section

Skills section

Group your skills logically. Only list skills you can talk about in an interview.

Languages:    HTML5, CSS3, JavaScript (ES6+)
Frameworks:   React, Next.js
Tools:        Git, GitHub, npm, VS Code, Chrome DevTools
Other:        Responsive Design, Accessibility, REST APIs, localStorage

Do not list every technology you have touched for 5 minutes. List what you are confident with.

Projects section

This is the most important section for a junior with no professional experience. Format each project as:

Weather App | HTML, CSS, JavaScript, Open-Meteo API          [Live] [GitHub]
- Fetches real-time weather data for any city using async/await and the Fetch API
- Displays current conditions, 5-day forecast, and supports °C/°F toggle
- Handles loading states and error states for failed API requests

Three bullet points per project is ideal. Use action verbs: Built, Implemented, Fetched, Designed, Added, Integrated, Optimised.

Experience section (if you have non-tech jobs)

Emphasise transferable skills: problem-solving, communication, working to deadlines, customer service, teamwork. Even retail or hospitality experience shows you can work with people and handle pressure.

Education section

Self-Taught Frontend Developer                              2025–2026
Completed Frontend Learning Roadmap (HTML, CSS, JavaScript, Git)

BSc History, University of Manchester                         2019–2022

Formatting Rules

  • Readable font — Inter, Calibri, Helvetica. 10–12pt for body, 14–16pt for name.
  • Generous whitespace — cluttered CVs are hard to scan.
  • Consistent formatting — all dates in the same format, all bullet points the same style.
  • PDF format — never Word. PDF looks the same on every device and cannot be accidentally edited.
  • No photos (in most countries outside of mainland Europe) — reduces bias and saves space.
  • No "References available on request" — assumed.
  • Hyperlinked URLs — portfolio, GitHub, LinkedIn should be clickable.

ATS (Applicant Tracking Systems)

Large companies use software to filter resumes before a human sees them. ATS systems parse your resume and score it against keywords from the job description. To pass ATS:

  • Use standard section headings (Experience, Education, Skills)
  • Use a simple, single-column layout (no tables, no columns, no text boxes)
  • Include keywords from the job posting — if they say "React", write "React" not just "a JavaScript framework"
  • Avoid headers/footers for important information (ATS often cannot read them)
  • Submit as PDF unless the application specifically asks for Word

Tailoring Your Resume

The best candidates tailor their resume for each application — adjusting the summary, reordering projects, and matching keywords from the job description. Even 10 minutes of tailoring per application significantly improves response rates.

Keep a "master resume" with all your projects and experience. For each application, copy it and cut/rearrange to highlight what is most relevant for that specific role.

Resume Red Flags to Avoid

  • Typos and grammar errors (use Grammarly)
  • Skills you cannot discuss in an interview
  • Lying about experience or qualifications
  • Generic objective statements ("Looking for a challenging position...")
  • Listing "Microsoft Office" as a technical skill
  • Using a non-professional email address (jokeyname@gmail.com)
  • A photo that looks unprofessional
  • Using "References available on request" (takes space, adds nothing)
← GitHub Profile Guide Freelancing Guide →