# Check Whether a Job Title Matches the Work Described

To spot a job whose duties differ from its title, map the work the description assigns. List the outputs, repeated tasks, decisions, and people who review the work. Compare that map with the role you want. Ask the employer about missing details before you decide. A mismatch is a reason to ask questions. It is not proof that the employer lied.

Start with the complete public job description. You can do this review by hand for one role. A data collection tool can help you save several descriptions, but you must still read the duties and ask about unclear responsibilities.

Your result will be a duty-scope map and a question sheet. A duty-scope map is a table that shows what work belongs to a role and where its responsibilities remain unclear.

## 1. State the work you want

Write a short statement of your intended role before you study the title. Name the work you want to do, the decisions you want to make, and responsibilities you need to understand before accepting.

For example, a person seeking analysis work might want to investigate data, explain findings, and produce reports. That person may need to ask whether accounting preparation or final approval also belongs to the role. This is a statement of preference. It is not a rule about what every analyst title must mean.

Separate these two questions:

1. Does the stated work match the role I want?
2. Can I show that I can do the work?

This guide answers the first question. Use the separate [guide to comparing jobs with your work evidence](/en/articles/jobs-fit-shortlist/) for the second question. Keep your ability assessment out of the duty-scope map. You can be able to perform a duty and still decide that you do not want it as a main responsibility.

A [public account read on 25 October 2026; reported experience, not verified employer facts](https://www.reddit.com/r/antiwork/comments/1tnzk1t/new_data_analyst_job_is_turning_into_replacing_a/) describes this concern. The writer says a data analyst role was presented as dashboards, reporting, data infrastructure, and process improvement. The writer later questioned whether the actual job was different. This account helps frame the question. It does not establish what the employer required or how often this problem occurs.

## 2. Save the title and complete duties

Read the full description before you classify the role. A search result or short extract may leave out a duty, a reporting line, or a qualification on a responsibility.

Save the original text without rewriting it. Put your interpretation in a separate column. This lets you check whether a concern comes from the employer's words or from your reading of them.

For one job, a manual copy with its public link and the date you read it can support this method. If you use collected records, retain these declared output fields:

| Field | What to retain and check |
| --- | --- |
| `jobId` | The source job identifier. Keep it as text. |
| `jobUrl` | The public listing address, when supplied. |
| `title` | The stated title, unchanged. |
| `companyName` | The stated employer name, when supplied. |
| `locationRaw` | The location wording from the source. |
| `descriptionText` | The saved description that supports your map. |
| `descriptionStatus` | The supplied information about description availability. Read it with the text. |
| `scrapedAt` | The time the record was collected. It is not employer confirmation. |

A field is a named part of a record. A record is one saved job listing. Several declared fields can have missing values. A missing employer name means the name is unknown in that record. A missing description does not mean the job has no duties.

Check that the saved text belongs to the intended listing. Read the title, employer, identifier, and source link together. If the description is missing or incomplete, mark the map as incomplete. Do not infer that an unmentioned duty is absent from the job.

## 3. Use a small collection only when it helps

The [LinkedIn Jobs Scraper Actor](https://apify.com/chronometrica/linkedin-jobs-scraper) is an option for collecting public job records. An Actor is a hosted program for collecting data. Its documented fields support saving the title and description for a manual review.

A Task is a saved input preset for an Actor. The public [LinkedIn Job Description Skills Demand Dataset Task, checked 25 October 2026; page presence only](https://apify.com/chronometrica/linkedin-jobs-scraper/examples/linkedin-skills-demand) can serve as a starting point. Its current saved settings and runtime behavior were not verified. The input below is a proposed small input. It is not a copy of verified saved Task settings, and it was not run for this guide.

```json
{
  "fetchJobDetails": true,
  "location": "United States",
  "maxItems": 3,
  "maxPagesPerSearch": 1,
  "saveOnlyUniqueItems": true,
  "searchTerm": "data analyst"
}
```

3. Use a small collection only when it helps

Replace `searchTerm` with your intended role. Replace `location` with your intended country or place. Keep the small limits for the first check.

`fetchJobDetails` requests job details. `maxItems` sets the item limit to 3. `maxPagesPerSearch` sets the page limit to 1. `saveOnlyUniqueItems` requests unique items. These settings limit a proposed collection. They do not promise three usable descriptions or complete coverage.

The [public default build checked 25 October 2026; declared fields and static validation only](https://api.apify.com/v2/acts/kkH2KvT3IfbFf6A6P/builds/default) was build 0.2.26. It declared these input fields and the retained output fields above. The proposed input passed a static schema check. A schema is a set of rules for data fields. A static check compares the input with those rules without collecting jobs.

No live collection occurred for this brief. The check does not prove data availability, collection success, or complete descriptions. If a collection fails, the result is unknown. Do not report zero jobs from a failed collection. If it reaches the item limit, do not treat the saved items as every available job.

This method uses public descriptions. Private application records, inbox messages, and internal work instructions are separate evidence. Keep answers you receive through your own process separate from public listing text.

## 4. Map outputs, tasks, and decisions

A deliverable is an output someone must produce. Examples include a dashboard, a monthly report, or a completed check. A recurring task is work repeated on a schedule. Authority is permission to make a decision or approve work.

Read each duty and ask:

1. What must the person produce?
2. What work must the person repeat?
3. What decisions must the person make?
4. Who checks the work?
5. Who gives final approval?

Review and approval are different responsibilities. A reviewer checks work. The person with final approval decides whether it can be accepted or released. Signoff means that final approval. Do not assume that producing a report also gives the person authority to approve it.

Use one row for each distinct scope item. A scope item is one responsibility that needs its own explanation. Keep closely linked wording together when splitting it would change the meaning.

Save these manual fields beside the source record:

| Map field | What to write |
| --- | --- |
| Source passage | The exact words supporting the row. |
| Deliverable | The output, or “not stated.” |
| Recurring task | The repeated work and any stated schedule. |
| Work group | A plain description, such as reporting or accounting preparation. |
| Ownership | Who must complete the work, if stated. |
| Authority | Which decisions the role can make, if stated. |
| Reviewer and signoff | Who checks and who approves, kept separate. |
| Time allocation | The stated hours or share of time, or “unknown.” |
| Role comparison | How this responsibility relates to your intended work. |
| Open question | The missing fact that could change your decision. |
| Evidence status | Public wording, your interpretation, or an employer answer. |

Group duties by the work they describe. Do not group them only by software names. Two duties can use the same tool while assigning very different responsibilities.

If a duty also suggests something you want to learn, keep that as a separate decision. The [guide to building a skills learning plan](/en/articles/jobs-skills-curriculum/) addresses study choices. Here, establish what work the role assigns before deciding what to study.

## 5. Find the missing responsibility limits

Look for wording that leaves ownership unclear. Words such as “support,” “manage,” or “handle” need context. They can leave open who prepares the work, who makes judgments, and who approves the result.

Mark each unanswered point directly. Use “not stated in this description” for missing wording. Use “unclear” when wording exists but does not settle the responsibility. Neither label means the employer has no process.

Check these limits:

1. Does the role produce the output or help another person produce it?
2. Does the role prepare information or make the final judgment?
3. Does another person review the work before release?
4. Who sets priorities when duties compete?
5. Who provides support when the work exceeds the role's authority?
6. What reporting line is stated, and what remains unknown?

Keep the title visible, but base each concern on a duty or an unanswered question. “The title says analyst” is less useful than “The description assigns final reporting approval, but the approval limits are unclear.”

A long duty list does not establish a time split. One short sentence can describe work that takes much of the week. Several longer sentences can describe occasional tasks. Count scope items only as scope items.

## 6. Work through one fictional example

Original fiction. This example is not an Actor run, a customer result, or an observed company finding. The role, wording, and reader preference below are invented for teaching.

The fictional title is “Data Analyst.” The fictional description says:

### 6. Work through one fictional example

Prepare a dashboard, complete monthly accounting tie-outs, and handle final reporting approval.

A dashboard displays selected information together. An accounting tie-out compares related accounting records or totals to check whether they agree. The phrase “handle final reporting approval” does not clearly say whether this person approves the report or prepares it for another person's approval.

The fictional reader wants analysis work. The reader has not yet received an employer explanation.

| Scope item | Work described | What is stated | What remains unresolved |
| --- | --- | --- | --- |
| Dashboard | Produce a dashboard | The role prepares the output. | Schedule, users, reviewer, and priority. |
| Monthly accounting tie-outs | Prepare accounting comparisons | The task repeats monthly. | Who makes accounting judgments and who reviews differences. |
| Final reporting approval | Take part in an approval process | The description assigns an approval-related responsibility. | Whether the role approves or prepares for approval, and the limits of that authority. |

The map contains 3 scope items:

1 dashboard item + 1 accounting preparation item + 1 approval item = 3 scope items.

The unit is scope items. It is not hours per week, people, or a percentage of the workweek. Three items do not mean equal thirds of the job. The description supplies no time amounts, so the time split remains unknown.

The word “monthly” establishes a repeated schedule for the accounting task. It does not establish how many hours that task takes each month. Unknown hours are not 0 hours.

The reader can now write a precise concern: the dashboard duty relates to the analysis work they want, while accounting preparation and approval responsibilities need explanation. A match on a software name would not settle those responsibilities.

The example supports a question about role design. It does not support a finding that the employer used a false title or intended to mislead an applicant.

## 7. Turn each gap into a question

Ask questions that can resolve the map. Connect each question to the stated duty rather than asking whether the title is “accurate.”

For the fictional example, use this question sheet:

| Gap | Question to ask | Answer needed for the decision |
| --- | --- | --- |
| Time split | In a typical month, how is time divided among dashboard work, accounting preparation, and approval work? | A stated allocation or a clear explanation that it varies. |
| Accounting judgment | Who decides how accounting differences should be resolved? | The responsible role and this job's limits. |
| Review | Who reviews the monthly tie-outs before they are used? | The review responsibility. |
| Final approval | Does this role give final approval or prepare reports for someone else's approval? | A clear division of preparation and approval. |
| Priority | When the dashboard and monthly accounting work have the same deadline, who sets the priority? | The decision owner and expected order. |
| Success | What outputs would show that this person is doing the job well? | Success measures tied to the actual duties. |

If the employer gives a time estimate, save its unit. Hours per week differ from hours per month. A share for a typical month may differ from a busy reporting period. Preserve words such as “usually,” “up to,” or “during month-end.” Do not turn an estimate into a fixed promise.

Ask for clarification through your own application or interview process. This article does not send questions or establish what an employer will answer. Until an answer arrives, keep the field unresolved.

## 8. Check the map and make the next decision

Review the complete map before you use it. Each interpretation must have source wording or a clearly marked answer behind it.

1. Confirm that the description belongs to the intended job.
2. Check that each mapped duty has a supporting passage.
3. Separate production, review, and final approval.
4. Keep missing details distinct from stated limits.
5. Check that every time amount has a unit and its original qualification.
6. Remove any time split inferred from the number of duties.
7. Keep employer answers separate from your interpretation.

An employer answer confirms what that contact stated. It does not prove how every working week will occur. Save who gave the answer, when you received it, and which question it answered.

Use the evidence to choose your next step. If the stated responsibilities match your intended work, record why. If a material responsibility remains unclear, continue the clarification. If confirmed responsibilities conflict with the work you want, record that conflict as your reason for reconsidering the role.

Keep failure states visible. Missing text requires a complete description. Unclear approval wording requires an authority question. Unknown time allocation requires a workload question. An unanswered question remains unanswered; it does not become evidence of deception.

## Put one role through the method

Choose one job you are considering. Save its complete public description and build the duty-scope map. Identify the unanswered responsibility that matters most to your decision. Ask the employer about that point before drawing a conclusion from the title.

If collecting public descriptions would help, use the [LinkedIn Jobs Scraper Actor](https://apify.com/chronometrica/linkedin-jobs-scraper) with the proposed small input above. Check the returned text before you map duties. Your next decision should rest on the stated work, the answers you receive, and the uncertainties that remain.

## Sources

- [Original public account, read 25 October 2026; reported role concern, not verified employer facts or evidence of frequency](https://www.reddit.com/r/antiwork/comments/1tnzk1t/new_data_analyst_job_is_turning_into_replacing_a/)
- [LinkedIn Jobs Scraper public default build 0.2.26, checked 25 October 2026; declared fields and static input check, no live collection](https://api.apify.com/v2/acts/kkH2KvT3IfbFf6A6P/builds/default)
- [LinkedIn Job Description Skills Demand Dataset Task, checked 25 October 2026; page and exact Task ID present, saved settings and runtime unverified](https://apify.com/chronometrica/linkedin-jobs-scraper/examples/linkedin-skills-demand)