How to Check a Job Listing Before Sharing Personal Information

Define what you need to verify

A public reader described the problem directly: “I've come across many listings, but it's hard to tell what's trustworthy.” That wording comes from one public post. It is not evidence about how often job fraud occurs. Public question context

Separate that broad concern into questions you can answer:

1. Which employer does the listing name?
2. Does an independently found employer source confirm the role and application website?
3. Does that employer confirm the recruiter’s claimed connection?
4. What information or payment does the message request?
5. What must you stop or clarify before you continue?

A recruiter is a person or organization that seeks applicants for an employer. You need to check the claimed business connection. You do not need to investigate the person’s private identity.

Use these decision terms consistently:

“Verified” applies to a fact, such as the employer’s confirmation of an application website. It does not mean the whole listing is safe.

Follow these eight checks

1. Save the public listing and collection date

Record the listing’s address, title, stated company name and the date you collected it. Save the public description when available. Keep the original wording separate from your notes.

Record the collection time and your manual check time separately. You may collect a listing on one day and check the employer’s website later. Neither time proves when the employer first published the role.

If the description is missing, write “description missing.” Do not treat an empty field as evidence that the listing contains no payment request or no request for sensitive information. You cannot assess text you do not have.

2. Find the employer’s website independently

Use a separate search to find the employer named in the listing. Do not use the recruiter’s message as your only route to the employer’s website or contact details.

Open the public company pages and look for its careers page or published recruiting contact. Record the page you used. If you cannot establish which website belongs to the named employer, leave that relationship unresolved.

The purpose is to obtain an independent contact for the employer. A matching company name alone does not complete this check. Do not copy the message’s contact details into your record and describe them as independently verified.

3. Compare the role and application website

Compare the listing with the employer’s public job information. Use the job title, duties, location and any role reference that the public pages provide. Record what agrees and what remains unclear.

Check the application domain too. A domain is the part of a web address that names the website. If the application domain differs from the employer’s domain, record the difference. Ask the independently found employer contact to confirm that exact application website.

A domain mismatch remains unresolved until checked. Do not call it fraud merely because the names differ. Do not mark it verified merely because the page displays the employer’s name.

If you cannot find the role, record “not found in this search,” with the search date and source. That result does not prove fraud or reveal hiring intent. The separate guide on what public listings can show about ghost jobs explains that limit.

4. Check the recruiter’s claim through the employer

Compare the recruiter’s stated connection with the employer’s public information. If you need confirmation, use the recruiting contact found in step 2.

Keep the question narrow. Ask whether the role, recruiting contact and application domain belong to the employer’s process. For example, you can ask the employer to confirm the listing title and the website where you were told to apply.

Do not send identity documents, bank details or a copy of the applicant’s private conversation to support this check. Begin with the public listing and the business claim that needs confirmation.

No reply means the claim remains unresolved. It does not prove fraud. This method proposes a contact step for the reader; it does not contact anyone automatically.

5. Record the information or payment requested

Write down the request category and when the request occurred. Useful categories include an identity document, bank details, a payment to obtain the job, an equipment purchase, or a deposited check followed by a request to send money.

Record the category without copying the sensitive information itself. For a private message, a short note such as “equipment purchase requested before employer confirmation” can describe the issue. Keep the private message out of the research file.

Separate an observed request from missing evidence. “No payment request observed in the public listing checked today” is narrower than “no payment will be requested.” If you have not checked the relevant material, write “not reviewed.”

The US Federal Trade Commission advises against paying for a promised job. It also warns about deposited checks followed by requests to send money. Those requests require a protective action, not a numerical risk score. FTC job-scam guidance

6. Use official guidance for your jurisdiction

A jurisdiction is the country or region whose rules and official guidance apply. Use its current official fraud-prevention guidance when you review a request.

The official guidance supplied for this article is from the US Federal Trade Commission. It supports the payment warnings described here. It does not establish reporting procedures or legal rules for every country.

If you need to make a report, check the applicable official instructions directly. Keep that step separate from your listing review. This guide does not make a legal finding about an employer or recruiter.

7. Pause when facts conflict

Pause the related action when the employer, recruiter or application website does not agree with the independently found source. Identify the exact question that remains open.

For example, “application domain not confirmed by employer” gives you a clear next check. “Looks suspicious” does not explain what you observed or what would resolve it.

For a payment to obtain a promised job, do not pay. For a deposited check followed by a request to send money, do not send the money. Do not allow agreement on other details to cancel that stop decision. The FTC identifies these payment requests as job-scam patterns. FTC job-scam guidance

For an unresolved request for sensitive information, pause the disclosure while you verify the employer and the purpose of the request. Do not treat a confirmed job title as confirmation of every later request.

8. Save the result with minimal private data

Record what you checked, the supporting public source, the date and the next action. If the employer provides clarification, record the result of that check without adding the applicant’s private messages to the research file.

Keep identity documents, bank details and private conversations out of a shared research table. Public listing data and applicant records have different purposes. Access to a public listing does not give anyone access to the applicant’s private records.

Recheck unresolved facts before you act. A record describes the evidence available at its check time. It is not a permanent guarantee.

Keep a source-linked review table

Use one review record for each listing. Add separate check entries when one listing has several requests or conflicts. This keeps one verified fact from hiding an unresolved request.

Do not enter zero where information is missing. An unknown requested amount is not a payment request for zero dollars. A blank description is not zero warning signs. A missing employer reply is not a refusal or confirmation.

The table also does not decide whether a remote role fits your location. Use the separate remote location requirement guide for that question. Keep location requirements separate from payment and privacy checks.

Use the Actor only to collect public listing evidence

You can complete this method manually for one listing. If you want a small collection of public listings, the Indeed Jobs Scraper provides a documented starting point.

An Actor is a hosted program that collects web data. A Task is a saved input preset for an Actor. Neither the presence of a listing nor the presence of a Task confirms an employer’s claims.

The supplied evidence checked public default build 1.2.14 on 25 October 2026. Its declared input fields accept this proposed sample:

{"country":"us","maxItems":3,"maxPagesPerSearch":1,"saveOnlyUniqueItems":true,"searchTerm":"data analyst"}

Replace `searchTerm` with the role you want to inspect. Replace `country` with the supported source-country code you need. The sample uses `us` and “data analyst.” It does not contain a remote-only setting, so do not describe it as a remote-only collection.

`maxItems` sets a limit of three collected items. `maxPagesPerSearch` limits the search to one page. `saveOnlyUniqueItems` requests unique items. None of these settings confirms an employer or recruiter.

Plan one review record for each listing actually returned. If a future run returns three listings, the planning calculation is 3 listings × 1 review record per listing = 3 review records. This is hypothetical arithmetic. It is not a collected result or a count of employers or people.

The checked input passed static schema validation. A schema defines permitted fields and value types. Static validation checks the input against that definition without collecting data. No Actor run occurred for this brief. The check does not prove data availability, complete coverage or successful collection.

The checked output definition includes `jobId`, `jobUrl`, `title`, `companyName`, `locationRaw`, `employmentType`, `salaryRaw`, `descriptionStatus`, `descriptionText` and `scrapedAt`. Keep the source text and collection time. Values can be missing where the source or field definition permits. Missing compensation text, for example, does not mean a salary of zero.

The Indeed Jobs Scraper Task page was present with the exact Task identifier `d9aAeJkHeurv5Lvt8` at the supplied check. Its current saved input was not verified. Inspect its settings before use. The sample above is proposed replacement input, not a copy of that Task’s saved settings.

The documented fit is public listing collection. You must perform the independent employer checks and make the privacy and payment decisions yourself. Applicant account status, private conversations, identity documents and bank details are outside this public-data method.

Original fictional worked example: Alder Works

This is original fiction for teaching. It is not an Actor run, customer result or observed finding about a company.

A fictional listing names Alder Works. A message asks the applicant to buy equipment with a deposited check and send money onward. The applicant has not yet verified the message through an independently found employer contact.

The next action is to pause the transaction and not send the money. The FTC identifies deposited-check offers followed by requests to send money as a scam pattern. The applicant does not need to calculate a fraud probability before taking that protective action. FTC job-scam guidance

The applicant then finds the fictional employer’s public website independently. They use its published recruiting contact to ask whether the role and message belong to the employer. This contact step is a proposed action. No reply or successful verification is invented here.

The stop decision concerns the requested transaction. It does not require a claim about the private identity of the sender. The employer connection remains unresolved until checked.

An unrelated application domain, if observed, would also remain unresolved until checked. That fact alone would not justify an accusation. Keep each decision tied to its own evidence.

Handle missing evidence without guessing

A missing description means you cannot assess the full listing text. Retain the listing reference and seek the public source before completing that check.

An inaccessible employer page means you could not inspect it at that time. It does not prove that the employer is fraudulent. Record the access failure and the check that remains open.

A role absent from your search remains “not found in this search.” A recruiter who has not been confirmed remains unverified. Neither state becomes verified because other listing details agree.

A confirmed application domain also does not approve a later payment request. Reassess each new request before you share information or move money. Keep the decision specific to the action in front of you.