# One Page or Two, and Format Basics — Resume & GitHub Portfolio

Source: https://www.skillbyai.com/en/resume-portfolio/f-format

> Length, layout and file type.

## Short, clean and easy to scan

A common guideline is **one page** for students and early-career engineers and up to **two pages** for experienced engineers with lots of relevant work; conventions vary by country and company, so check what is normal where you apply. Whatever the length, every line should earn its place. Use a single-column layout, a readable font at a sensible size, consistent dates and spacing, and clear section headings. Send a **text-based PDF** (exported from a document editor, not a scanned image) unless the application asks for another format. Name the file clearly, for example `firstname-lastname-resume.pdf`. Avoid photos, ratings bars for skills and dense graphics unless local norms expect them.

## A basic format checklist

Apply before sending any version.

```text
[ ] length fits your experience (often 1 page early career, up to 2 later)
[ ] single column, consistent fonts, sizes and spacing
[ ] standard headings: Experience, Projects, Skills, Education
[ ] dates aligned and in one format (e.g. Jan 2024 - Present)
[ ] text-based PDF; text can be selected and copied
[ ] file name: firstname-lastname-resume.pdf
[ ] no skill rating bars, no tables used for layout
[ ] spell-checked; read aloud once
[ ] links work and point to the right pages
```

## Test the copy-paste

Open your PDF, select all the text and paste it into a plain text editor. If the order is scrambled or words are missing, simplify the layout.

**Quiz:** Which file is generally the safest choice to send?

- [ ] A zip file of HTML pages
- [ ] A scanned image of a printed resume
- [ ] A screenshot of a website
- [x] A text-based PDF exported from a document editor

*Answer:* A text-based PDF exported from a document editor. Text-based PDFs keep layout and remain readable by software.