# How to Read a LinkedIn Job Applicant Count

Preserve the exact wording of a public job applicant display, note the observation time, and treat the counted event as unknown. A LinkedIn applicant display alone cannot tell you how many qualified people are competing for a job. An Actor is a hosted data collection program. A Task is a saved input preset.

## Collection setup and field limits

To set up collection, replace the current preset inputs where `searchTerm` has three roles, `startUrls` is `[]`, and `saveOnlyUniqueItems` is `true`. Replace the entire role list with one intended `searchTerm` and location, set `maxItems` to `3`, `maxPagesPerSearch` to `1`, and `fetchJobDetails` to `true`.

Public build 0.2.19 provides row fields `jobId`, `jobUrl`, `title`, `companyName`, `applicantsRaw`, `postedAtRaw`, `postedAt`, and `scrapedAt`. The `applicantsRaw` field is a nullable string. Native string values like "35 applicants", "72 applicants", and "88 applicants" prove field availability only. The derived `postedAt` field comes from relative text and is not proof of exact publication time. Run outputs like `requestedMaxItems`, `jobsSaved`, `candidateItemsSeen`, `pagesParsed`, `detailRequests`, `detailFailures`, `blockedRequests`, `failedRequests`, and `stopReason` track job execution. A `stopReason` of `max_items_reached` proves a hit cap, not full market coverage.

A typed table means each column has one stated value type. An integer display is an exact transcription of the visible integer, but the underlying counted event remains unknown. A rounded display like "2K" is not a verified exact value or rounding interval. A lower bound display like "Over 100" shows a bound above 100, not exactly 100.

## Step-by-step collection method

1. State the actual question. A displayed counter does not show worker skills, job eligibility, unique people, or finished forms. This method creates a clear evidence record, not a hiring score or advice to quit.
2. Collect one public job sample. Check the job ID and URL, and save the raw applicant text with the scrape time. The display can change or disappear later. Keep private recruiter reports out of your public data.
3. Separate display states. Sort the text into integer display, rounded display, lower bound display, nonnumeric phrase, and unavailable. Keep the exact words plus the parsing rule. An integer is just a text copy, not proof that the event is exact or unique. Do not erase signs like over or plus.
4. Parse only what the words say. The text "35 applicants" means an integer of 35. The text "Over 100 applicants" means a lower bound above 100, not exactly 100. The text "2K applicants" is shorthand with no verified rounding rule. A phrase like "Be among the first 25 applicants" is promotional text, not a direct count. A null value means unavailable, not zero.
5. Add the event definition state and evidence. Without an official definition for this public page, keep the event unknown. Campaign Manager click and application counts belong to a different tool and do not define this public counter.
6. Keep publication age separate from collection time. A relative label like "3 days ago" and one snapshot do not give an exact daily rate. A later observation shows a difference only if the job ID and display rules match. It is not proof of market growth.
7. Use the record to see limits in your choice. Do not divide one by the count to find your chance of getting the job. Different applicants apply, the event is unknown, and no selection process is measured. Read the job details and [assess your evidence](/en/articles/jobs-fit-shortlist/) instead of trusting a public rank.
8. Deliver a typed table with raw text, display state, numeric evidence, event definition, date evidence, and unresolved reasons. Keep unknowns visible instead of guessing a real applicant number.

## Original fictional complete raw-display ledger

The following examples and table rows are original fiction.

| Job ID | Source Ref | Raw Display Text | Display State | Numeric Evidence | Event Definition | Date Evidence | UTC Observation Time | Unresolved Reasons |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| J1 | fictional_src_01 | 35 applicants | integer_display | 35 | unknown | 3 days ago | 2026-10-13T06:00:00Z | Event type undefined |
| J2 | fictional_src_02 | Over 100 applicants | lower_bound_display | above 100 | unknown | 1 week ago | 2026-10-13T06:00:00Z | Bounded lower limit |
| J3 | fictional_src_03 | 2K applicants | rounded_display | unverified | unknown | 2 weeks ago | 2026-10-13T06:00:00Z | Shorthand rounding |
| J4 | fictional_src_04 | Be among the first 25 applicants | nonnumeric_phrase | none | unknown | 4 days ago | 2026-10-13T06:00:00Z | Promotional text |
| J5 | fictional_src_05 | null | unavailable | none | unknown | 5 days ago | 2026-10-13T06:00:00Z | Field missing |
| J6 | fictional_src_06 | 0 applicants | integer_display | 0 | unknown | 6 days ago | 2026-10-13T06:00:00Z | Zero count, not missing |

In this fictional set, there are six observation rows, two integer displays, one lower-bound display, one rounded display, one nonnumeric phrase, and one unavailable field. No set here contains six known applicant counts. Do not sum these states into a total market size. Unknown values remain separate from zero.

If J1 with the same identity is observed on 2026-10-14T06:00:00Z and shows "40 applicants", the comparable display difference is plus five. It is not five confirmed new unique finished applications. If it instead shows "Over 100", there is no exact comparable delta. A relative age of three days does not support dividing 35 by three to claim eleven applications per day.

## Next action

Save one raw applicant display with its precision and unknown event meaning before using it in a job choice by using the [LinkedIn Jobs Scraper Actor](https://apify.com/chronometrica/linkedin-jobs-scraper) and the [LinkedIn Applicant Pressure Task](https://apify.com/chronometrica/linkedin-jobs-scraper/examples/linkedin-applicant-pressure).

## Sources

- [LinkedIn Campaign Manager Definitions](https://www.linkedin.com/help/linkedin/answer/a414844/)
- [Data Engineering Job Posts Discussion](https://www.reddit.com/r/dataengineering/comments/1s46fea/why_are_data_engineering_job_posts_getting/)