Two job descriptions can share a title while describing very different work. One may emphasize hands-on delivery, another cross-team coordination. Comparing them by title or keyword count can obscure responsibilities, required experience, and the conditions of the role.
This guide produces a role requirement matrix with ChatGPT, without rewriting a resume or judging a person's suitability. It is an original comparison method using fictional examples. Current documentation was checked on October 6, 2026. The employer's published wording remains the evidence; a generated comparison does not establish additional requirements or hiring decisions.
Save the descriptions and their publication context
Collect the complete descriptions, including responsibilities, qualifications, location, working arrangement, and any stated application conditions. Record the employer, title, source URL, checked date, and version if available. A copied excerpt can omit a condition that materially affects the comparison.
Give the descriptions IDs such as ROLE-A and ROLE-B. Use passage labels for requirements and duties so the matrix can point to exact source wording. If a description changes, save the new version separately rather than silently replacing the comparison's evidence.
Check that both roles are still relevant to your purpose before using the result. A listing can change or close after the comparison date. The matrix should describe the versions reviewed, not imply that availability or employment terms will remain unchanged.
Separate requirements from responsibilities
A responsibility describes work expected in the role. A qualification describes an attribute or experience requested from applicants. A preferred qualification should remain preferred, even when it sounds useful. Do not promote it to mandatory because another employer requires something similar.
Also separate explicit conditions from vague language. “Occasional travel” is an employer statement, but it does not specify a frequency. Preserve the phrase and mark the amount unclear rather than estimating a number of trips.
OpenAI's ChatGPT usage reference documents comparing supplied files. Provide the descriptions as readable text or attachments, then confirm that both complete texts are available. The comparison method here depends on those sources rather than assumptions about typical roles.
Define the comparison dimensions
Use dimensions that make the work understandable: core duties, required experience, preferred experience, named tools, collaboration, decision authority, working conditions, and unresolved details. Include compensation only when the descriptions state it, preserving currency, interval, and qualifications.
| Dimension | ROLE-A evidence | ROLE-B evidence | Comparison treatment |
|---|---|---|---|
| Core work | Passage reference | Passage reference | Describe overlap and distinct duties |
| Required experience | Exact condition | Exact condition | Preserve mandatory wording |
| Preferred experience | Stated preference | Stated preference | Keep separate from requirements |
| Collaboration | Named groups or responsibilities | Named groups or responsibilities | Avoid inventing reporting lines |
| Working arrangement | Published condition | Published condition | Mark missing details explicitly |
Do not equate different experience statements automatically. “Experience leading projects” and “three years managing a team” may overlap, but one does not establish the other. The matrix should identify possible relationships and preserve the wording needed for clarification.
Ask for extraction before comparison
Have ChatGPT extract requirements and duties into separate tables before producing the side-by-side matrix. This makes misclassification easier to catch. Require source IDs for every row and an explicit missing-information label.
Compare the two supplied job descriptions in a role requirement matrix.
First extract responsibilities, mandatory qualifications, and preferred qualifications separately.
Preserve source IDs, original conditions, units, and qualifiers.
Identify overlap and differences without treating related terms as identical.
Mark information not stated in a description as not stated.
Do not rewrite a resume, evaluate an individual, or infer unstated hiring criteria.
Return the matrix and a concise list of questions for the employer.Review the extraction before accepting the matrix. A model can turn a sentence containing both a duty and a qualification into one broad requirement. Split those components when their distinction affects the interpretation.
Examine a fictional comparison
Imagine ROLE-A asks the employee to build reporting workflows and lists experience with a named analytics tool as preferred. ROLE-B asks the employee to coordinate reporting across teams and requires experience leading reporting projects. These descriptions share a domain but emphasize different daily work.
The matrix should show that overlap without declaring the roles equivalent. It should preserve ROLE-A's tool preference and ROLE-B's leadership requirement. A short observation can state that A emphasizes direct workflow creation while B explicitly includes coordination, citing the relevant passages.
If neither description states the reporting manager, mark that field not stated. Do not infer that a coordinator reports to operations or that a builder reports to engineering. Those may be useful employer questions, but they are not facts established by the supplied listings.
Handle synonyms and ambiguity carefully
Group terms only when the role context supports the relationship. “Stakeholder communication” and “cross-functional updates” may be related activities, but the expected audience and responsibility can differ. Retain the original phrases alongside a neutral normalized category.
Avoid attaching a seniority label solely from a title. Employers use titles differently, and responsibilities provide a more concrete comparison. If seniority is explicitly stated, record it as the employer's description rather than derive it from a guessed hierarchy.
Treat omissions as unknowns. A role that does not mention travel is not necessarily travel-free. A role that does not state a tool requirement does not establish that the tool will never be used. Use the matrix to identify useful questions rather than turn silence into a guarantee.
Review the matrix for factual accuracy
Check every material row against both sources. Pay particular attention to mandatory versus preferred wording, numeric experience conditions, location, working arrangement, and any stated compensation interval. Do not compare an annual amount with an hourly amount without an explicit, reviewed conversion assumption.
Inspect the observation column for unsupported judgments. “More demanding,” “better career growth,” and “easier to get” are conclusions the descriptions may not support. Replace them with concrete differences or label them as personal considerations requiring additional information.
If reviewers suggest changes to the comparison, use the feedback ledger guide to retain the source-based decision. The approved matrix should remain separate from any later resume or application work.
Turn uncertainty into useful questions
Create a short employer-question list from material gaps. Ask about decision authority, the balance of duties, the meaning of ambiguous conditions, or the expected tools when those details affect your understanding. Avoid questions already clearly answered in the description.
Keep the questions neutral and specific. “How much of this role involves building workflows versus coordinating their delivery?” is more useful than “Is this really a technical role?” The question should resolve the comparison's uncertainty rather than challenge an inferred label.
Retain the matrix with its source versions and checked date. Update affected rows if the descriptions change. You now have a traceable account of how the roles differ, which facts are shared, and what still needs clarification.
Frequently asked questions
Can the matrix determine which job is best for me?
It describes the supplied roles. Choosing a job also depends on your priorities and information that may not appear in either listing.
Should preferred qualifications count as requirements?
Keep them separate unless the employer explicitly changes that wording. Do not convert a preference into a mandatory condition.
What if the descriptions use different words for similar work?
Place them in a related category while retaining their original wording and noting any difference in scope or responsibility.
Can missing details be inferred from the job title?
No reliable comparison should depend on that inference. Mark important omissions and ask the employer for clarification.
Does this workflow require sharing a resume?
No. The deliverable compares job descriptions and produces clarification questions; personal application material is outside its scope.
