JD-targeted rewrite: aim real experience at the role

No — that's a hard constraint. The AI only reorganizes and aligns the real content you provide; it won't invent experience, employers, titles, dates or numbers. Verify every line is true before using it — both for integrity and because recruiters detect padded resumes.

This rewrite is not local-only: the snippet you paste is sent to the online rewrite backend for a single pass, then discarded — no database, no logging of content, no training use.

Yes. Without a JD it just makes the wording clearer and stronger (still no fabrication); with a JD it additionally aligns to the role's wording for a tighter match.

Tailor a version for every role worth applying to. One generic resume blasted everywhere usually has the lowest hit rate, because each JD cares about different keywords and emphasis. Tailoring isn't rewriting from scratch — it's adjusting wording, surfacing your most relevant experience, and describing the same true work in the employer's terms. Spending effort on the few roles you actually want beats mass-sending a hundred generic resumes.

Recruiters don't object to 'you used AI' — they object to AI padding: flowery, generic content that doesn't match how you perform in an interview. PolishCat's rewrite is hard-constrained to reorganize only the real experience you provide, with no fabrication, and it keeps your own voice. Always read it through and make it sound like you. A resume that's factually sound and reads as yours is fine whether or not a tool helped; what actually backfires is invented content that collapses under one interview question.