Paste your job duties in plain English. Get ATS-ready, action-verb bullets that get noticed.
Put in your job title, paste your duties one per line in the plainest language you have, and pick a tone. The generator rewrites each line to start with an action verb matched to that tone, so the same duty reads differently for a results-focused sales role than for a technical one.
Write the duties as you would say them to a friend: "ran the weekly stock count", "trained two new hires", "fixed the printer nobody else would touch". The plain version is the raw material. If you paste polished corporate language, the output is polished corporate language with a different verb in front.
Duties pasted as ran social media accounts / managed a team of 3 / created monthly reports / helped grow email list, with the title Marketing Manager and tone Results-focused, come back as bullets built on verbs like Increased, Grew and Delivered, with the industry folded in as context.
The gap between the raw duty and a hiring-manager bullet is a number. "Managed a team of 3" is a fact with no scale; "Managed a three-person team across two product lines" is the same fact with the ambiguity removed. The generator supplies the verb and the structure, and it deliberately leaves the number blank, because it cannot know yours. Adding "3" where the duty already says three is the whole job: you are the only source for the magnitude.
A resume bullet has three parts: a verb, an object, and a result or scale. The verb tells the reader what you did, the object tells them what you did it to, and the number tells them whether it was worth mentioning. Generated text gives you the first two reliably and the third only if your input contained it.
Treat every line as a draft with a hole in it. Read each bullet and ask what a sceptical interviewer would challenge: "increased engagement" invites "by how much, over what period, measured how?" If you have the answer, put it in. If you do not, either drop the claim or replace it with something you can defend. A bullet you cannot back up in an interview is worse than a plain description of the work.
Keep the numbers honest and specific. "Cut invoice processing from three days to one" is checkable. "Improved efficiency by 40%" usually is not, and interviewers have learned to hear the difference.
Most should. It removes the "responsible for" opening that wastes the first two words of every line, which is the part a reader's eye lands on.
Three to five for a recent role, one or two for an older one. Space spent on a job from a decade ago is space taken from the work you want to be hired for.
Describe scope instead: the size of the team, the number of accounts, the systems you owned, the volume you handled. Scope is a fact even when a percentage is not.
Plain text with standard job titles helps, and so does avoiding tables and graphics. No tool can promise a specific system's result, so keep the formatting simple and the keywords honest.
Past tense for previous roles, present tense for the job you still hold. Pick one per role and stay with it.
The verb list is this page’s. The job-search advice worth reading is not.
Last updated: November 2, 2026. Reviewed by David Liu.