Before a company can publish a job listing, its domain has to be verified. This is the gate people are most surprised by, so it is worth explaining what it checks and why.
What it proves
That whoever set the company up controls its domain. Nothing more.
It is not a background check, not a check that the business is solvent, and not an endorsement.
It is the cheapest available proof that a listing claiming to be from example.com was posted by
somebody who can receive mail at, or publish DNS for, example.com.
The two methods
Email domain. If you signed up with an address at the company's own domain, that is already the proof. Free-mail domains do not count — a Gmail address proves you control a Gmail account, not a company.
A DNS record. Add the TXT record we give you to the domain, and we look it up. Use this when your account address is not on the company domain, or when someone other than the domain owner set the company up.
Why it gates publishing
Because the alternative is a job board where anyone can post as anyone. That fails in one specific way: a fake listing collects real applications, with real CVs, from real people. The cost of getting it wrong falls on the candidate, not on us.
It is one of three gates between a draft and a published listing — see Posting a job for the other two.
The badge on a profile
Some parts of the product refer to a verified profile. That is a separate signal about a person, and it is not shipped yet — no profile currently displays a verification badge. Company verification, described above, is what exists today.
We would rather say that than let a page imply a check nobody is running.