Every AI resume tool will happily rewrite a bullet point to sound more impressive. Most of them don’t ask whether the impressive version is still true.
We enforce one rule on everything we generate, and it’s simple enough to say in one sentence:
Would you actually say this out loud in an interview?
If the honest answer is no, it doesn’t go on the resume. Not as a style guideline we mention in the FAQ — it’s a hard constraint built into how resumes get generated, checked line by line before anything reaches you.
In practice that rules out the tricks that make “AI resume” a slightly dirty phrase right now:
- No white-text keyword stuffing. Hiding a wall of invisible keywords for the parser to find might sound clever, but it surfaces the moment a recruiter copies your resume text into an email — and a hidden block of false claims is worse than a visible one, because concealment reads as intent. Several tools that shipped this have quietly walked it back.
- No claiming tools or skills you’ve never touched. Not even at a “familiar with” level, if you’ve genuinely never used it.
- No date inflation to paper over a gap. A gap is a fact. We’ll help you talk about it honestly; we won’t help you hide it.
- No borrowing your team’s win as your own. If the team shipped it and you contributed to it, that’s a real, defensible sentence. If you didn’t touch it, it’s not yours to claim.
None of this means your resume undersells you — it means the confident version of your experience has to be a version you’d defend, unscripted, across a table from someone who might ask a follow-up question. That’s a higher bar than “does this sound good,” and it’s the only bar that actually protects you once the interview starts.
Legitimate keyword saturation still belongs on your resume — just visibly, in a skills section, where it’s both true and expected. A recruiter searching for a specific platform or tool should find it because you actually used it, not because it’s buried in ten-point white text at the bottom of the page.