Common Output Quality Fixes
On this page
Even strong tools benefit from a quick human review. If your generated CV output isn’t quite right, these fixes will help you improve it fast.
1) “This sounds generic”
Fix:
- Add 1–2 concrete details to your base CV (metrics, tools, project scope).
- Shorten vague adjectives and replace with proof.
Example:
- “Highly motivated team player” → remove
- Add: “Led migration of X to Y; reduced cost by 22%.”
Related: /docs/add-your-base-cv
2) “The summary is too salesy”
Fix:
- Generate in Balanced mode.
- Keep the summary to 2–4 lines and focus on role-relevant proof.
Related: /docs/how-to-choose-a-writing-mode
3) “Too many keywords / feels stuffed”
Fix:
- Remove repeated keywords that don’t add meaning.
- Ensure every key skill is backed by at least one bullet with proof.
Related: /docs/how-to-avoid-keyword-stuffing
4) “Missing metrics”
Fix:
- Add 1–2 metrics per recent role in your base CV:
- time saved
- revenue impact
- cost reduction
- scale (users, events, data volume)
5) “Wrong emphasis for this role”
Fix:
- Re-check the job description (expand ‘See more’).
- Regenerate and compare versions.
- Update base CV with a relevant project if you repeatedly see misalignment.
Related:
6) “It’s too long / too short”
Fix:
- Shorten by removing older irrelevant bullets.
- Expand by adding proof-based bullets (not fluff).
See: /docs/how-to-control-length-one-page-vs-two-page
7) “Layout looks off in PDF”
Fix:
- Try a different template.
- Shorten overly long lines and bullets.
- Keep section titles consistent.
Related:
FAQ
Do I need to edit every generated CV?
You should always do a fast review pass. Most edits are small (tone, clarity, one metric).
Can I get consistent improvements over time?
Yes—treat the process as a feedback loop: improve the base CV, then regenerate.