How to write a resume, step by step

Most resume advice jumps straight to formatting tips without covering the order of operations. Here is the order that actually works, from a blank page to something ready to send.

1. List everything before you write anything

Before touching layout, write down every job, project, and piece of relevant education, with rough dates. Do not filter yet. The goal is a raw inventory you can cut from, because it is much easier to remove weak material from a full list than to remember it later once you are three sections deep into a draft.

2. Pick the job first, then the content

A resume is not one fixed document; it is a different selection of the same facts for each job you apply to. Before writing bullet points, read the job listing and note which two or three skills or experiences it cares about most. Those get the most space. Everything else gets compressed or cut.

3. Write experience bullets around results, not duties

The weakest bullets describe a responsibility: “Responsible for backend development.” The strongest describe an outcome, ideally with a number attached: “Reduced API response time by 40% by rewriting the query layer.”

A simple structure to fall back on: what you did, how you did it, what changed as a result. Not every bullet needs all three, but the ones that get remembered usually have the third part.

4. Keep the skills section short and specific

List the tools and languages you have genuinely used in a working context, grouped by category (languages, frameworks, infrastructure). A list of eight relevant items reads as more credible than a list of thirty, because it looks like a filtered judgment rather than everything you have ever opened once. We go deeper on this in skills to put on your resume.

5. Format for one column, plain text

Applicant tracking systems parse resumes by extracting text in reading order. A multi-column layout, a table, or a skills graphic can scramble that order or vanish entirely, even if it looks fine on screen. One column, standard section headings (“Experience,” not “My Journey”), and no text embedded in images. Jake’s Resume template is a widely used example of this approach and worth a look even if you are not using LaTeX.

6. Check length against your experience

One page for most candidates, extending to two only past roughly a decade of relevant history. See how long should a resume be for the full reasoning.

7. Proofread by reading it backward, section by section

Reading top to bottom, your brain fills in gaps and skips typos because it already knows what the sentence is supposed to say. Reading each section in isolation, out of its normal order, makes errors easier to catch.

8. Have someone else read it for ten seconds

Hand it to someone unfamiliar with your work and ask what they remember after ten seconds. If they cannot name what you do or your strongest achievement, the resume is burying its own best information.

Starting from real evidence instead of a blank page

For developers, a lot of step one, listing everything you have built, already lives in a GitHub account: repositories, languages, and a contribution history. resumefromgit.com reads a public GitHub username and generates a visual CV and an ATS-safe PDF resume from that activity directly, which turns step one from a memory exercise into a starting draft you edit down rather than build from nothing.