Random job generator

How it works

Inside is a catalogue of job titles: short strings such as baker, dispatcher, or librarian. A click returns one title, or a short set. There is no interview, no license check, and no knowledge of your town. The tool only knows the list. A list of fantasy guilds will never emit a municipal clerk. A list of modern office nouns will never emit a ship’s bosun. Quality is the catalogue, not the button.

Some pages add filters: field, indoor or outdoor, or a tone such as “serious” versus “silly.” A filter is a smaller list. It is not a career counselor. If you leave the filter on party gags and then paste the title into a human-resources mock that other people will treat as real, the mismatch is yours. Read a few draws before you ship one.

Repeats mean the list is short or the tool puts used titles back. For a table of characters who must not share a profession, shuffle and deal. For a private writing warm-up, a repeat next week can be useful: the same title on a new character is a different story. Decide that before you call a duplicate a bug.

The generator does not know seniority. “Engineer” and “principal engineer” are different strings if both are in the list. If only the short noun is in the list, you will not get a grade. Do not invent a pay band because the title sounded senior. The string does not contain a salary.

Titles, granularity, and lists that show off

Occupation names vary in grain. Chef is wide. Pastry chef is narrower. A cute generator that only emits “wizard of spreadsheets” is a joke machine. That is a legitimate toy. It is a poor source of dummy data for a payroll screen, where a realistic label helps you see whether the layout still works. Match the list to the job of the page, not to the joke you wanted at lunch.

Writing prompt: a title as a door into a character, not a biography. Game role: a class name; keep it consistent with the game’s own list if the game already has one. Layout fixture: boring, plausible titles at a stable length so the test is about the software.

Icebreaker: optional, kind, and not a status contest about real income. Proper nouns and real firms do not belong in a random occupation unless you are prepared for a collision with a living workplace. Prefer generic roles. If a draw names a regulated profession — physician, pilot, attorney — remember that the generator did not confer a license. Using that string as a pretend credential in a public setting is a different act from using it as a fiction tag.

Dummy roster versus a person who did not consent

Filling a test database with generated jobs is honest when the column is labeled as generated. It is not honest when a moderator later treats those rows as user profiles. Label the fixture. Keep language and length stable enough that the test is about wrapping and sorting, not about a generator that suddenly emits a paragraph of punctuation.

A generated job title is a costume. Do not put it on a tax form and then act surprised. In a workshop, draw a title and write one concrete sentence about a person doing that work at 9 a.m. Then stop clicking. Extra titles are a stall. In a product team, a random occupation is spice for a sample record, not a substitute for talking to the people who actually do the work. When the real research starts, close the generator.

Skip the picker when the assignment already named a role. Skip it when you needed labor statistics: those come from statistical agencies, not from a toy list. Skip it when the list was scraped from headlines you have not read. You can inherit a title you cannot support. Do not present a generated occupation as someone’s real job.