Lesson 2.2: Writing Clear Prompts for Job Analysis Tasks

Using Codex and ChatGPT for Job Analysis
Lesson Content
0% Complete

A good prompt tells the AI exactly what kind of help is needed. In job analysis work, vague prompts often produce vague answers. A beginner may type, “Make this better,” and receive a response that sounds polished but is too general to use. A stronger prompt gives the model a role, a task, constraints, and a desired output format. This makes the tool much more useful and reduces the chance of getting generic wording.

A simple prompt structure for job analysis includes four parts: context, task, rules, and format. Context explains the role or document being worked on. Task tells the model what to do. Rules define what to avoid or preserve. Format describes the output structure. For example: “You are helping draft a job analysis for a front-desk coordinator in a medical clinic. Rewrite the following notes into clear task statements. Do not add new duties. Use simple workplace language. Present the result in a table with columns for task, frequency, and notes.” This prompt gives the AI enough direction to stay focused.

One of the most useful prompt habits is to ask for specific output types. Instead of asking for “help,” ask for a table, a list of interview questions, a competency summary, or a cleaned-up task statement. Specific output formats make it easier to review and compare the result. For instance, if the analyst wants to compare tasks by frequency, a table is better than a paragraph. If the goal is to prepare supervisor interviews, a list of questions is better than a summary.

Another important habit is to tell the AI what not to do. If the source notes mention only customer support tasks, the prompt can say, “Do not include sales responsibilities unless they are explicitly mentioned.” This reduces the risk of added assumptions. AI tools often try to be helpful by filling in missing details, but in job analysis, that can create inaccurate outputs. Clear boundaries improve reliability.

Here is an example of a stronger prompt:

“Act as a job analysis assistant. Use the notes below to draft five task statements for an entry-level warehouse associate. Keep the wording specific and factual. Use action verbs. Do not invent tasks that are not in the notes. After the task statements, list three follow-up interview questions to clarify frequency and physical demands.”

A prompt like this encourages both drafting and deeper inquiry. The analyst can then review the task statements and use the follow-up questions in a real interview.

Codex can also be prompted in structured ways. For example, if the analyst has a CSV-style list of tasks, the prompt could request grouping by theme, cleaning up formatting, or identifying repeated phrases. The key is to match the tool to the need. ChatGPT is often best for drafting and question generation. Codex is useful when the output must be structured, transformed, or organized in a repeatable way.

Beginners should also learn to use examples inside prompts. If the analyst wants task statements written in a certain style, including one example can guide the model. For instance: “Task statement style example: ‘Responds to customer inquiries by phone and email and documents outcomes in the CRM system.’ Write the rest of the statements in a similar style.” This gives the AI a model to follow.

Strong prompting is not about using fancy language. It is about being clear, specific, and careful. The better the prompt, the less time spent correcting the output. In job analysis, that means the analyst can spend more time validating real job information and less time cleaning up generic AI text.