Like I said, it would be a pure optimization over a more rigorous proof-of-identity + proof-of-income path. You can always allow the user just fall back to that more-rigorous path if they don't have such a verifiable address.
Linkedin will never require proof of income. That's much more intrusive. So no it's not an optimization over something that simply never will occur.
I think you may just have to accept that if you want to verify an employee, you'll need to call their previous employers. This is the way it's always been done.
> I think you may just have to accept that if you want to verify an employee, you'll need to call their previous employers
You're talking about "they" as in the people reading the CV. Which works fine for the scale individual employers operate at.
But the point of this conversation, is what the services themselves, dealing with fake profiles at scale, should do. LinkedIn themselves don't make hiring decisions; they make money off of how reliable their listings are. Their incentive is entirely different than the employer's incentive.
By analogy: it's fine to talk about how a given person should carry pepper spray with them if they want to avoid getting mugged. But what should a city government do to make a city a place people want to move to, where people generally don't want to move to cities where they might have a high chance of getting mugged?
> Linkedin will never require proof of income. That's much more intrusive.
You seem to think we're talking about this being done for every company automatically. But my understanding is that bots are always trying to impersonate the same top companies — so this requirement would either be for a certain whitelist of important employers, or (more likely) would be an org setting that the LinkedIn org admin for a given company would set (when they're having trouble with bots), to require LinkedIn to do extended verification for people claiming to specifically be employees of that company. Very much like how Cloudflare has an "I'm under attack" toggle that forces visitors through CAPTCHAs. If your previous employer sets that flag... well, that's their fault. Same as it's their fault if they aren't willing to give you a reference for petty reasons.
