Job search
How to Verify a Recruiter and a Job Offer Before Sharing Sensitive Information
Verify a recruiter and job offer through independent company channels before sharing sensitive information. A worked case shows how to record conflicting signals and hold an unresolved request.

A recruiter message can name a real company and link to a real opening while leaving the sender's connection to that company unverified. Before sharing identity documents, banking information, or money, establish an independent route to the employer and examine what the request actually asks you to do. A convincing offer document cannot resolve those questions by itself.
This guide uses current public Federal Trade Commission guidance and an explicitly fictional review. No recruiter was contacted, account opened, document uploaded, or payment made. If you need a role to investigate, browse recently posted jobs on LandOffer, then verify the employer and application route independently. LandOffer publishes this guide and benefits from readers using its job search.
Establish which identity you are trying to verify
There are several different claims inside a recruiting approach. The company may exist. An opening may appear on its careers website. A named person may work there. The person sending this particular message may be authorized to recruit for that particular opening. Finding evidence for the first claim does not automatically establish the others.
Start by preserving the message and reading its request without following its embedded route. Record the claimed employer, role title or job identifier, sender address, proposed next step, and any requested information or payment. Keep that record private. You do not need to paste the entire message, your resume, or identity details into a public forum to begin assessing it.
The FTC's guidance on unexpected job texts recommends checking through company contact information you find independently, rather than relying on information supplied in the message. That establishes a useful direction for verification: a route obtained separately from the person whose claim you are checking.
For example, navigate independently to the employer's known website and look for its careers page or an appropriate recruiting contact. A link copied from the questionable message is still part of that message's evidence chain. Search results can help locate a site, but the first result's position is not proof that it represents the employer. Compare the actual domain and company identity before treating the route as independent.
Find the employer contact route independently, then check whether it supports this sender's claimed recruiting relationship. This step does not require accusing anyone. You are checking whether a claimed relationship is supported before making a consequential disclosure.
A completed review that preserves the unknowns
Elodie Mercer and Mallow Circuit are invented for this guide. Every item in the following packet is an authored teaching assumption, not an observed employer website, candidate report, or real accusation. The fictional incoming message names an engineering-support opening, directs Elodie to a sender-provided contact route, asks for banking information, and requests an upfront equipment payment.
The invented reference packet separately contains an employer careers listing for that role and an independently recorded recruiting contact route. It contains no confirmation connecting the message's sender to that employer. Elodie completes the following record without replying, paying, or sharing documents.
| Item reviewed | What the fictional packet establishes | What remains unresolved | Completed decision |
|---|---|---|---|
| Company and role | A reference listing names the employer and opening | Whether this sender represents either | Keep the listing as context only |
| Contact route | The independently recorded route differs from the message's route | Whether the claimed recruiter is authorized | Use the independent route for any later inquiry |
| Sender identity | The message asserts a recruiting relationship | No independent confirmation supports that assertion | Mark identity unverified |
| Equipment payment | The message requests upfront payment | The request's connection to a genuine hiring process | Do not pay; hold the process |
| Banking details | The message requests sensitive financial information | A verified purpose and trustworthy recipient | Do not provide the information |
The completed fictional record supports holding payment and disclosure; it does not establish the sender's identity or make an individual fraud finding. The request is held because a consequential demand remains unsupported and includes a payment pattern the FTC warns about. No single domain difference is used to declare a particular person a scammer.
This makes the review useful even while uncertainty remains. “Unverified; no payment or sensitive information shared” is a concrete state. “Probably fine because the job exists” would collapse several separate claims into one.

Treat warning signs as evidence, not a point score
Some legitimate recruiting arrangements involve an agency or a different domain. Some fraudulent approaches use accurate company names, copied staff profiles, polished documents, and plausible terminology. A rule that accepts every corporate-looking email or rejects every outside recruiter will therefore answer the wrong question.
Compare the independent sender confirmation with the particular payment, document, or banking request before deciding the next step. Does the sender explain which employer or agency they represent? Can you verify that relationship through an independent route? Does the next step ask you to disclose information or transfer value before the relationship is established? Is the message pressuring you to skip verification?
The FTC's job-scam guidance advises against paying for a promised job. It also recommends researching the company and recruiter, while explaining that finding no complaints does not establish honesty. Those are different evidence limits: a payment request can warrant stopping the transaction, while a clean search result cannot supply missing identity confirmation.
Avoid turning the review into a numerical legitimacy score. There is no supported rule here that a certain number of reassuring details outweighs a request to send money. Equally, a spelling mistake alone does not establish fraud. Write down the concern and the independent check that could address it.
The record separates supporting context from the missing sender confirmation. In Elodie's packet, the real-looking role is supporting context, the sender relationship is unresolved, and the equipment payment remains on hold. A later verified response could add evidence about the sender; it would not retroactively make an earlier payment safe to have sent.
Complete a minimal inquiry before sending anything
An independent inquiry should ask for the missing relationship, rather than expose additional personal information. If the employer offers a suitable recruiting contact or help route, a short question can identify the role and ask whether the named approach belongs to its process. Use the route found independently, not a reply address or telephone number supplied only by the message.
Here is Elodie's completed, unsent inquiry draft. The employer and role are fictional; the destination is deliberately absent because this is a teaching exercise.
I found an engineering-support opening attributed to Mallow Circuit. A message claims to recruit for that opening and requests an equipment payment and banking information. Could your recruiting team confirm whether this approach is part of your hiring process, and identify the official next step for this role? I have not paid or shared sensitive information.
The inquiry is now ready for review, but it has not been sent. It includes no bank account, identity document, date of birth, password, verification code, or complete resume. The role reference and description of the request are enough to explain what needs checking in this fictional example.
The inquiry asks for the missing recruiting relationship without adding sensitive information to the unresolved exchange. If a real employer's route asks for additional material, consider what is necessary for the inquiry and whether the recipient has been established. Do not include sensitive details merely because a form provides a large free-text box.
Elodie's finished decision note reads: “Sender association unresolved. Inquiry drafted through an independent route. No contact, payment, or disclosure performed. Application and offer acceptance remain on hold.” This is the second completed asset: a usable inquiry plus a state record that cannot be mistaken for a verified recruiter or a submitted application.
Inspect the offer and the information request separately
An offer can contain a role title, compensation, start date, signature, and employer logo while still leaving its origin uncertain. Read its terms, but do not let visual polish substitute for verifying who issued it. A document claiming that a recruiter is authorized is still an assertion from the same packet until independently supported.
Compare the offer's role, employer identity, location or work arrangement, and next steps with information obtained through the employer's own verified route. A changed detail may have a reasonable explanation, but it should be explained before you rely on it. Keep the original version so a later correction does not erase what you were initially asked to accept.
Then examine each information request on its own. What is requested? At which stage? For what stated purpose? Through which verified system? A process may eventually require sensitive onboarding information, but that general possibility does not authenticate a particular link or justify supplying it to an unverified sender now.
Ordinary application details also deserve care. Share only what the current step needs, and inspect an upload before attaching it. Remove unrelated private records from the file. Never provide a password or a verification code to a recruiter as a way to prove your identity. A claimed urgent start date does not answer the recipient or purpose questions.
In this example, Elodie does not evaluate whether the offer is legally enforceable or whether particular onboarding requirements are lawful. The completed review is narrower: the sender is not independently established, and the requested transfer and financial disclosure are held. That is enough to prevent the unsupported next step.
Do not use available funds as proof of an employer
Equipment requests sometimes come with a supposed employer check and instructions to purchase items or forward part of the money. The FTC's fake-check guidance explains that funds appearing available does not establish that the check is genuine. Do not treat an account balance as confirmation of the sender or send funds onward on that basis.
This is official consumer guidance about a known pattern, not a finding about a specific person's bank account. Elodie's fictional packet contains an upfront payment request, not a deposited check. Adding an imaginary deposit or recovery outcome would make the case more dramatic while weakening its evidence boundary.
If a real request involves payment, gift cards, cryptocurrency, or forwarding money, stop that action and review the FTC's relevant guidance. If you already transferred money or disclosed information, the next useful step is to consult the appropriate official reporting or account-provider route. Preserve the original message, requested payment method, documents, and relevant transaction record privately. A report is a way to provide evidence; it is not a promise of reimbursement or a completed investigation.
End with a decision you can explain
Verification is complete only to the extent that the evidence supports a particular claim. You may establish an employer's website while still needing to establish the sender's authority. You may finish an inquiry draft while still waiting for an independent answer. Record those states separately so the next person reviewing your notes can see what happened.
For Elodie, the finished outcome is a safe hold with a minimal unsent inquiry. The company listing stays in the record, the sender remains unverified, and no money or sensitive information leaves her control. The unresolved relationship stays visible until an independent answer provides further evidence.
For your next search, choose a recently posted role on LandOffer, record the independent employer route, the evidence connecting this sender to the role, and the information requested at the next step. Move forward only when the evidence supports the next step you are considering.
Sources and Further Reading
- FTC: Job Scams — payment demands, recruiter research, and the limits of complaint searches.
- FTC: Unexpected Job Texts — verification through independently found company contact information.
- FTC: Fake Check Scams — why available funds do not establish a genuine check.