115M Profiles Verified and LinkedIn Still Shipped Vouching — the 4 Dubai Screening Habits I Retired This Week

I source engineers for Dubai companies, which means I spend a large part of every week trying to establish whether things strangers have written about themselves are true. On Tuesday that job got structurally easier, and one category of work I have been billing clients for quietly stopped being worth billing for. Here is what actually shipped, what it does not cover, and the four habits we changed in our own screening the same week.

What LinkedIn Actually Shipped on 23 September

The release, reported by Sarah Perez in TechCrunch under the headline “LinkedIn adds new tools to fight fake profiles and bogus work histories”, has three distinct parts, and they are worth separating because they fail in different ways.

Peer vouching for work experience. A member can now vouch that a colleague or classmate genuinely held a role during a stated period. LinkedIn is explicit that this is not an endorsement — an endorsement recommends a person for a skill, whereas a vouch attests to a fact. The gating is the interesting part: the voucher must already have a verified profile, must have been connected to the person for at least a year, and must have two-factor authentication enabled on their own account. That last condition exists to make hijacked accounts a poor vehicle for manufacturing vouches.

Company-page controls. Page administrators can now remove accounts that falsely claim to work at the company, which stops those accounts appearing on the company page and in associated search results. LinkedIn is also testing an optional requirement that future profile associations be confirmed through workplace verification such as a work email address.

Wider identity verification. Truecaller and PeerSpot join Adobe and UserTesting as verification partners, with the Truecaller integration letting a verified LinkedIn identity surface on an inbound call.

The scale numbers matter for whether any of this becomes a norm: LinkedIn says 115 million members and more than 700,000 companies have been verified to date, and that verified profiles get 50% more post views and 90% more impressions on average. Oscar Rodriguez, LinkedIn’s VP of Product, framed the motivation directly: “faking credibility has never been cheaper or easier than it is today; and conversely, showcasing credibility has never mattered more.”

Our Expert Take #1 — The Cheap Half of Reference Checking Just Died

Be honest about what reference calls have actually been doing. In our own Dubai placements, a meaningful share of every reference conversation was spent on confirmation: you worked there, yes? From March to November, yes? As a backend engineer, yes? That is administrative work performed by two senior people on a scheduled call across a four-hour time difference, and it has been the single most reliable source of delay in a UAE hiring cycle, because the former manager is frequently in another country and frequently does not call back.

Vouching does not remove reference calls. It removes the part of the reference call that was never a conversation. If a candidate’s two most recent roles carry vouches from verified long-standing connections, you have the dates and the role. What you still do not have — and what you should now spend the entire call on — is judgement: how did this person behave when the architecture decision went against them, what did they do in the week a release slipped, would you hire them again.

The question I have started asking instead of “can you confirm the dates” is “what did they get wrong while they worked for you, and how did you find out?” The answers to that have never been available on a profile and never will be.

Our Expert Take #2 — Why This Lands Harder in the UAE Than Almost Anywhere

Most markets hire most of their engineers domestically. Dubai does not. A large share of the developers we place arrive from another country, which means the employment history a UAE employer is asked to trust was accumulated under a different jurisdiction, in a different language, frequently at a company that has since been acquired, renamed or wound up, and supervised by a manager who has themselves since relocated.

This is why the cost of verifying a claim is not evenly distributed across the world. A London employer checking a London role makes one phone call. A Dubai employer checking that same role makes one phone call too — and then waits, because the number is in a country where the working week ends on a different day. Any mechanism that makes cross-border employment history checkable without that call removes more cost from a UAE hiring cycle than from a domestic one.

There is a second-order effect worth naming. The scarcer the skill, the more a Dubai employer has been willing to proceed on an unverified history rather than lose the candidate to a competitor. That trade-off has been quietly corrosive, and it is the one that a low-friction verification layer actually repairs: you no longer have to choose between speed and certainty on the identity question. You still have to choose carefully on everything else, which is the subject of our UAE developer background check guide.

Our Expert Take #3 — The Failure Mode Nobody Is Talking About Yet

Every verification system creates a new incentive, and the incentive here is legible from the gating conditions. A vouch requires a verified voucher connected for at least a year with 2FA enabled. That is a real barrier to a bot farm. It is a much smaller barrier to a group of five people who genuinely have known each other for years and are willing to attest to roles that were shorter, more junior or more peripheral than stated.

In other words, vouching hardens the system against fabricated strangers and does comparatively little against friendly exaggeration — which, in our experience of Dubai engineering hires, is by a wide margin the more common problem. We have almost never encountered a candidate who invented an entire employer. We encounter, regularly, a candidate who held a role for five months and describes it as a year, or who sat adjacent to a migration and describes it as having led one. A vouch from a friendly former colleague survives both of those.

So the honest reading is narrower than the headline: this release raises the floor on identity and existence, and leaves the ceiling on accuracy exactly where it was. Plan your screening around that asymmetry rather than around the press coverage.

The 4 Screening Habits We Retired This Week

Concrete changes, made to our own process, in the order we made them.

1. We stopped opening reference calls with confirmation questions. Where the two most recent roles carry vouches from verified connections, the dates and title are established and the call starts at judgement. This alone took roughly fifteen minutes out of every reference conversation and, more importantly, removed the reason a call had to be rescheduled when the former manager only had ten minutes.
2. We started reading the absence of verification as information — carefully. With 115 million members verified, an unverified profile is no longer the default state. It is also not evidence of anything on its own: verification depends on document and region availability, and plenty of excellent engineers have simply never been prompted. We treat it as a question to ask, never as a filter to apply, and we say so out loud to clients who want to sort by it.
3. We ask company-page administrators, not just former managers. The new page controls mean the employer of record now has a direct interest in the accuracy of who claims to work there. For a candidate whose most recent employer is a company with an active page, that page is a faster and more reliable confirmation route than a former manager’s mobile number.
4. We moved the weight of our assessment further toward work sampling. If the identity and existence questions are cheaper to answer, the proportion of screening effort that should sit on demonstrated output rises. Nothing in this release touches whether a developer can build what you need, and the gap between a real title and real competence is now the widest unverified thing in the process.

What a Dubai Employer Should Actually Do This Month

Three practical moves, none of which require a new tool.

First, claim and clean your own company page. The ability to remove false employment claims is useless if nobody at your company has administrative access, and in our experience a surprising number of Dubai SMEs have a page created years ago by someone who has left. This is also a brand-protection matter rather than purely a hiring one: accounts falsely claiming to work at your company appear in searches associated with you.

Second, rewrite your reference-call script. If it still contains the words “can you confirm,” it is now partly obsolete. Replace those questions with behavioural ones and keep the call the same length rather than shortening it — you have been given better questions, not less time.

Third, do not let any of this touch your right-to-work process. Verification on a platform has nothing to do with UAE work authorisation, which runs through the Ministry of Human Resources and Emiratisation regardless of how thoroughly a profile is verified. If you are building the surrounding paperwork, our employer-of-record and WPS payroll guide covers the sequence, and colleagues running the same problem in Singapore have written up the equivalent under Employment Pass, CPF and employer-of-record hiring.

One last note on where this is heading. The engagement figures LinkedIn published — 50% more post views, 90% more impressions for verified profiles — are not a neutral statistic. They are an incentive, and they tell you that verification is being pushed as a distribution advantage rather than only a trust feature. Expect the verified share of any candidate pool you source from to rise quickly for that reason alone, which is precisely why the absence of verification will become tempting to over-read. Resist that. The signal is about identity. Your assessment is about the work, and if you are hiring a team rather than an individual, our guide to building a fintech product in the UAE sets out the staffing sequence we use.

FAQ — LinkedIn Verification and Dubai Developer Screening