How do I start a resume from scratch?

Start with a plain single-column document containing your name, contact details, a three-line summary, then experience, skills, and education. Write each role as three to five bullet points that begin with an action verb and end with a measurable result, then tailor the wording to the job posting.

Do applicant tracking systems reject resumes automatically?

Most applicant tracking systems do not auto-reject. They parse your resume into fields and rank it against the job description, so parsing failures and missing keywords push you down the list rather than removing you outright.

What file format is best for an ATS resume?

A text-based PDF is the safest format for most modern systems. Avoid scanned images, and use .docx only when the employer explicitly asks for it.

Career guide

How to write an ATS-friendly resume for tech roles

Applicant tracking systems read your resume before a person ever does — and in 2026 a layer of AI screening usually reads it after that. Here is how to start a resume from scratch and shape it so both machines and hiring managers can follow it.

What an ATS actually does

An applicant tracking system is a database, not a bouncer. When you apply, it parses your document into structured fields — name, contact, employers, dates, titles, skills, education — and stores them. Recruiters then search and filter that database by keyword, and increasingly an AI layer ranks candidates against the job description.

That means two separate failures cost you interviews. If your layout is unparseable, your experience lands in the wrong fields or vanishes. If your wording does not match how the role is described, you simply never surface in the recruiter’s search. Neither one sends you a rejection email.

Start a resume from scratch in seven steps

Open a blank single-column document. No template with sidebars, no design tool export. One column, top to bottom.
Header: full name, city and country, phone, email, LinkedIn, and GitHub or portfolio. Plain text lines — never inside a text box, header, or footer, which many parsers skip entirely.
Summary: three lines. Your title, your years of experience, your domain, and the single result you are most known for.
Experience: reverse-chronological. For each role write Job title — Company — City — Mon YYYY–Mon YYYY on one line, then three to five bullets.
Bullets: action verb, what you built, and the measurable outcome. “Rebuilt the checkout API in Go, cutting p95 latency from 840 ms to 180 ms across 2M monthly requests.”
Skills: a flat, comma-separated list of concrete technologies. Skip proficiency bars and star ratings — parsers read them as noise.
Education and certifications: degree, institution, year. Add certifications only when they are relevant to the target role.

Formatting rules that decide parsing

Do

One column, standard section headings (Experience, Skills, Education)
A text-based PDF, unless the employer asks for .docx
Standard fonts at 10–12 pt with real bullet characters
Consistent Mon YYYY date formats on every role
Spell out an acronym once: “CI/CD (continuous delivery)”

Avoid

Tables, columns, and sidebars — parsers read them out of order
Logos, headshots, icons, and charts carrying real information
Contact details inside page headers or footers
Keyword stuffing in white text — screening tools flag it
Creative section names like “My Journey”

Optimizing for modern AI filters

Keyword matching used to be literal. Today’s screening models also compare meaning, which changes the tactics: you need the exact terms from the posting and enough surrounding context to make them credible.

Mirror the posting’s vocabulary. If it says “distributed systems”, do not only write “microservices”. Use both.
Put keywords inside achievements. A skills list alone reads as unproven; the same term inside a quantified bullet reads as evidence.
Match the job title where it is honest. If your title was “Software Engineer II” and the role is “Backend Engineer”, write “Software Engineer II (Backend)”.
Quantify roughly a third of your bullets. Numbers survive summarization better than adjectives.
Tailor per application. One resume per posting beats one resume for fifty, and it takes about ten minutes once the base document is solid.

A quick self-check before you submit

Copy your resume out of the PDF and paste it into a plain text editor. If the reading order scrambles, a section disappears, or your phone number ends up inside a job title, the ATS will see the same mess. Then check that the top ten nouns in the job posting appear somewhere truthful in your document, and that the file name is Firstname-Lastname-Resume.pdf.

Common questions

How long should a tech resume be?: One page under roughly eight years of experience, two pages beyond that. Depth on recent roles beats completeness on old ones.
PDF or Word?: A text-based PDF for nearly every modern system. Send .docx only when the application explicitly requests it, and never a scanned image.
Do I need a cover letter?: When the field exists, fill it. A short, specific letter that names the team’s problem and your closest matching project is still one of the cheapest differentiators available.