Resume Handbook

1. The Google XYZ Resume Formula

The most effective way to frame your achievements is using the XYZ formula: “Accomplished [X] as measured by [Y], by doing [Z].”

The XYZ formula was popularized by Google's internal resume review guidelines and is now widely adopted across the tech industry. It forces you to quantify your impact rather than simply listing responsibilities. Every bullet point on your resume should answer three questions: What did you accomplish? How did you measure success? What specific actions did you take? This structure gives hiring managers and ATS algorithms concrete evidence of your capabilities rather than vague descriptions of job duties.

2. Layout and Structure Guidelines

Corporate recruiters spend an average of 6 seconds reviewing a resume. Keep your structure clean:

• Single page only (unless you have 8+ years of experience).
• Single-column layout to ensure ATS compatibility.
• Consistent margins of 0.5 to 1.0 inch.
• No visual scales, percentages, or stars for skill levels.

Beyond these basics, maintain consistent spacing between sections, use a font size between 10 and 12 points for body text, and keep section headings at 14 to 16 points. Your name should be the largest element on the page at 18 to 24 points. Avoid using header and footer regions in document editors, as ATS parsers often skip content placed in these areas entirely. Stick to a chronological or hybrid format — functional resumes that hide employment timelines are strongly flagged by ATS algorithms as potential attempt to conceal employment gaps.

3. Action Verbs to Start Every Bullet

Always begin bullet points with strong, active verbs in the past tense (or present for current roles):

Avoid weak verbs like “Was responsible for,” “Helped with,” “Worked on,” or “Participated in.” These phrases dilute your impact and fail to communicate ownership. Each bullet should start with a powerful verb that immediately signals your direct contribution to the outcome.

4. Quantifying Impact with Metrics

Numbers are the single strongest signal you can include on a resume. Whenever possible, attach concrete metrics to your achievements. Common dimensions include: percentage improvements in performance or efficiency, absolute counts of users, customers, or transactions affected, revenue generated or costs saved measured in currency, time saved measured in hours or days per cycle, and scale of systems managed (servers, databases, codebases in LOC).

For software engineering roles, prioritize metrics that demonstrate technical impact: reduced page load times, increased test coverage percentages, decreased error rates in production, throughput improvements in data pipelines, and uptime or availability percentages for critical services. If you don't have access to exact numbers, research industry benchmarks and use conservative estimates clearly marked with “approximately” or “~.”

5. ATS-Compatible Formatting Guide

Applicant Tracking Systems parse resumes by extracting text from the file and matching it against job requirements. To ensure your resume parses correctly: use standard section headings (Education, Experience, Skills, Projects, Certifications), avoid text boxes, tables, columns, and floating elements that confuse parsers, embed all fonts in your PDF to prevent rendering discrepancies, save your final file as PDF/A format for maximum compatibility, and name your file professionally (FirstName_LastName_Resume_Company.pdf rather than resume_final_v3.pdf).

ResumeFlow's default ATS Strict template automatically handles all of these requirements. The LaTeX compiler ensures single-column flow, standard font embedding, and precise margin control that passes parsing audits for Greenhouse, Lever, Workday, Taleo, and SmartRecruiters.

6. Common Resume Mistakes to Avoid

• Including a photo or headshot: In most countries outside of parts of Europe and Asia, photos on resumes lead to immediate rejection due to anti-discrimination hiring policies.
• Listing references or “References available upon request”: This wastes valuable space. Hiring managers know to request references when needed.
• Using jargon or acronyms without expansion: Spell out abbreviations at least once — the ATS or recruiter may not recognize team-specific acronyms.
• Including outdated technologies: If you haven't used a technology in over 5 years and it's not relevant to the target role, remove it to keep your skills section focused.
• Submitting in editable formats: Never send .docx or .pages files. These formats render differently across operating systems and can have formatting stripped by ATS ingestion pipelines.
• Using creative fonts or decorative elements: Stick to professional fonts like Times New Roman, Helvetica, Arial, Calibri, or Georgia. Fancy scripts and decorative fonts are stripped or garbled by parsers.