The output
What the fake AI resume generator produces
One sample resume per run, written from the brief you type, delivered as plain text in the result pane with a Copy button. Contact line, summary, work history, education and skills, all invented. It is fixture content: the thing you need when a real CV would be inappropriate to paste into a ticket, a screenshot or a demo.
The run happens on our AI server, so the brief is sent to us rather than processed in the page. The allowance is 5 free runs in a rolling 24 hours, the brief box takes up to 12,000 characters, and the optional instruction field below it takes 300.
The run
How to generate a fake resume in three steps
Under a minute, and worth planning because the runs are counted.
- Step 1
- Write the brief in the pane labelled Your brief: role, seniority, length of history, the sections your template or parser needs.
- Step 2
- Use the instruction field for a constraint that applies to the whole output, such as a word ceiling or a date format.
- Step 3
- Press Generate, read the result pane, copy it out. The footer tracks how many of the 5 runs remain.
Input quality
Write the brief like a spec, not a keyword
There is no industry menu and no seniority menu here, which the hosted alternatives do offer. The brief field replaces both, so the level of detail is yours to set, and a vague brief is the main cause of a bland result.
- The role in plain words
- Regional facilities manager, second-year paralegal, night shift line lead. Job titles drive the whole vocabulary of the output.
- A shape for the history
- Four employers in nine years with one promotion, or one employer for a decade. Shape is what breaks layouts.
- Region and date convention
- A US resume and a UK CV differ in sections and in phrasing. Say which, and say whether dates carry months.
- The fields under test
- Certifications, publications, security clearances, referees. Ask for exactly the blocks your parser has to read.
- Edge cases
- A long hyphenated surname, an employment gap, a role with no end date. Ask for them or you will not get them.
Rationing
Working inside 5 runs per 24 hours
The allowance is per rolling day, so treat each run as a deliberate request rather than a dice roll. Two habits cover it. Write the whole brief before the first press, including the edge cases, because refining a vague brief costs a run each time. And copy the result immediately: the model runs with randomness and no seed, so an identical brief returns a different resume and nothing can be reproduced later.
The response is capped at 1,400 tokens, about one page, which sets the ceiling on what a single run can carry. Asking for three full resumes in one brief gets you three truncated ones. Asking for one resume plus a short second variant usually fits.
Coverage
Building a set of test resumes that covers the awkward cases
A parser or a template fails on shape, not on subject matter, so vary the structure across the set rather than the industry. Five runs spread over two days is enough for a small suite that finds real bugs.
- The long one
- Fifteen years, six employers, a publications block. Tests overflow and pagination.
- The sparse one
- A graduate with one internship and no employment history. Tests empty sections.
- The irregular one
- Contract work with overlapping dates and a career break. Tests date parsing.
- The typographic one
- Accented names, a hyphenated surname, an address with unusual punctuation. Tests encoding end to end.
- The wrong-shaped one
- Skills first, education last, no summary. Tests assumptions about section order.
In the build
Where sample resumes fit into a workflow
Design first: layouts need plausible text before they need real content, and a placeholder resume shows where a two-line job title wrecks a column. Then QA, where resume parsers and applicant tracking integrations need inputs that vary in structure.
After that come the softer uses. Demo environments that must not contain a real person's employment history. Screening and interview training material. Classroom exercises where students mark up a CV. In every one of them the point is that nobody real is attached to the document.
The line
What a fake resume generator is not for
Not for applying to jobs. A fabricated work history submitted to an employer is fraud, and the output here is placeholder content with nothing behind it to verify.
It is also a poor tool for the job on its own terms. Recruiting guidance now describes structured phone screens about specific projects, skills assessments, references reached through a company switchboard rather than a supplied number, and cross-checks between a resume and a public profile. Invented roles do not survive a conversation about them.
Plan around these
Limits to plan around
No file export of any kind. No PDF, no Word document, no template picker, no batch mode, no API. The result is text you copy.
No repeatability, because there is no seed. No guaranteed structure either: you can ask for a particular layout in the brief and it usually complies, but this is a language model rather than a schema generator, so validate anything you intend to feed a parser. And no claim is made about any applicant tracking system, recruiter or AI detector, in either direction.