Write a resume that survives ATS and a 20-second recruiter scan

Layout that parsers can read

Use a single-column Word or Google Doc, then export PDF. Avoid tables, text boxes, icons, and two-column templates. ATS tools still mangle those. Standard headings only: Summary, Skills, Experience, Education, Projects.

File name: Firstname-Lastname-Role.pdf. The role should match the posting (Software Engineer II, Salesforce Architect), not “MyResumeFinal2”.

Skills is a keyword list, not a story

Put 10–16 tools the JD actually names, grouped: languages, cloud, data, testing. If the JD says PySpark, write PySpark, not “big data processing.” If it says Salesforce (SFDC), include both Salesforce and SFDC once.

Bullets that a recruiter can scan

Each bullet: verb + what you built + scale or result. Weak: “Responsible for developing APIs.” Stronger: “Built REST APIs in Java Spring Boot used by 3 client teams; cut p95 latency from 800ms to 220ms.”

• Start with shipped work, not coursework, once you have a job.
• Name the stack in the bullet (Python, Azure, Kubernetes) so the parse and the human both see it.
• Drop “team player” and “hard working.” Show it with a collaboration or on-call bullet instead.

Tailor in 15 minutes, not a rewrite

Keep a master resume. For each apply, change the summary line, reorder skills to match the JD, and swap 2–3 bullets so the first screen matches the posting. That is enough. Rewriting the whole document for every job is how people stop applying.

What to delete

Objective statements, 10-year-old internships once you are mid-level, every college club, and a skills bar chart. GPA only if you are a new grad and it helps. Notice period can go in the application form; it does not need a resume line unless the JD asks.