What is a resume?

A resume is a short document that summarizes your work history, skills, and education, written for the specific purpose of getting an interview. Not a job: an interview. That distinction shapes everything else about how one should be written.

What it is for

A hiring manager or recruiter typically spends well under a minute on a first pass through a resume. Its job is to survive that first pass and earn a closer look, not to fully represent everything you have ever done. A resume that tries to be comprehensive usually fails at the one job it actually has.

In the United States and Canada, “resume” is the standard term. In the UK, Ireland, and most of the Commonwealth, the equivalent document is usually called a CV, though the two terms describe different things once you leave academia. We cover that distinction separately in CV vs. resume: what’s the difference.

What every resume contains

Formats vary by industry and country, but nearly every resume includes the same core sections:

Contact information, meaning a name, email, and usually a location and a link, such as a LinkedIn profile or a GitHub username. Work experience, listed in reverse chronological order, with a title, employer, dates, and a handful of bullet points per role describing what you did. Education, usually degree, institution, and graduation year. Skills, a compact list of relevant tools, languages, or certifications.

Some resumes add a short summary at the top, a projects section, or publications, depending on the field. We go through what belongs in each part in what to put on a resume.

Length

One page is the standard expectation for most candidates, particularly early- and mid-career. Two pages become reasonable once someone has ten or more years of relevant experience to summarize. We cover the reasoning behind that guideline, and the exceptions to it, in how long should a resume be.

The part that is easy to miss: machine readability

Most job applications now pass through an applicant tracking system before a human sees them, software that parses the resume into structured fields and often screens or ranks candidates automatically. A resume that looks polished on screen can be functionally unreadable to that software if it uses multi-column layouts, tables, or text embedded inside an image. A single-column layout with real, selectable text almost always parses more reliably than something more visually elaborate.

Building one from evidence you already have

For developers, a resume built from scratch tends to undersell real work, mostly because it is hard to remember or quantify everything you have built over several years. A GitHub profile already contains a lot of that evidence: languages you actually write in, projects other people use, and a history of how consistently you have contributed.

resumefromgit.com reads a public GitHub username and turns that activity into a visual CV and a single-column, ATS-safe PDF resume automatically. You then add the parts GitHub cannot know, like job titles, dates, and education, and the result is a resume grounded in verifiable work rather than a blank page and a memory of the last few years.