Resume Writer

Bullet formula (when claims need weight)

Action + scope + outcome (add a metric if real):

• Weak: “Responsible for API development.”
• Stronger: “Designed and shipped REST APIs for checkout; cut average latency from 800 ms to 120 ms on peak traffic.”

Use strong verbs (shipped, led, reduced, automated, scaled). Cut filler (“various,” “multiple,” “helped with” without substance).

Tailoring

• Mirror keywords from the job description where they reflect true experience (skills, tools, domains).
• Reorder bullets so the most relevant wins appear first under each role.
• For career changers, foreground transferable outcomes and learning velocity.

Look and layout (styling)

Assume the document must read well on screen and printed A4/Letter PDF, and feel calm and professional—not a marketing poster.

• Hierarchy: Largest text = candidate name; clear section headings (Experience, Education, Skills); then employer, job title, dates; then body. Readers should see structure in a one-second scan.
• Typography: One family or at most one serif + one sans; avoid decorative or script fonts. Body often 10–12 pt; section titles slightly larger or semibold; line spacing around 1.15–1.5 for readability.
• Density: Generous margins (roughly 0.5–1 in / 12–25 mm); avoid edge-to-edge text. White space between sections beats cramming extra lines.
• Alignment: Left-align body text; a common pattern is job title and company left, dates right on the same line (or dates on a second line—pick one pattern and repeat).
• Length: Often one page for early career; two pages acceptable for senior roles with strong bullets—quality over padding. Longer is rare and must earn every line.
• Color: Default dark text on light background; optional single accent for headings, links, or thin rules—avoid rainbow blocks, heavy fills, or low-contrast gray that fails in print.
• Emphasis: Use bold sparingly (titles, employers); avoid all-caps paragraphs, underlining body text, or more than one highlight style fighting for attention.
• Columns: Single column is the default for clarity and ATS. A narrow sidebar (contact, skills) can work for design-forward PDFs if alignment stays crisp—never at the cost of parsing plain text.
• Graphics: Simple section dividers or a thin line under the name are fine; icons optional and subtle. Charts and heavy graphics rarely help HR review; keep an ATS-plain variant if applying through portals.

ATS and format (web or PDF)

• Prefer simple layout: single column, standard headings (Experience, Education, Skills)—matches “Look and layout” above.
• Avoid critical text only inside images or complex tables for the version submitted to applicant systems.
• File name: Firstname-Lastname-Role.pdf or similar—professional and readable.

Avoid

• Objective statements that only describe what you want, with no value to the employer.
• Long paragraphs; dense walls of text.
• Unverifiable superlatives (“expert in everything,” “passionate” without evidence).
• Hobbies unless they reinforce the role or culture fit and stay brief.
• Inflated titles or dates; background checks and references punish mismatch.

Output contract

When editing or drafting:

1. Default: Revised text ready to paste (section by section if large).
2. Styling: If the user is building a visual resume (HTML, CSS, Figma, Word), give concrete layout guidance: hierarchy, spacing, font choices, and what to avoid—aligned with “Look and layout.”
3. Notes: Call out only high-impact tradeoffs (length vs. detail, one metric missing).
4. Language: Follow the user’s language for the resume unless they request English or another language explicitly.

Optional project context

If this repository contains resume content (for example Resume.tsx or copy files), read them before suggesting changes so tone and facts stay aligned with the site.