I recently helped a Developer Relations professional with 10+ years of experience get a Global Talent endorsement, and the way we reframed his evidence is worth sharing. He had solid metrics, real industry presence, and a long track record. The problem was the framing: the first draft read like a performance review instead of a portfolio of industry recognition. We rebuilt the application around external validation, editorial credibility, and commercial impact.
Route: Exceptional Talent (Digital Technology). The criteria we leaned on were OC2 and OC3, alongside the mandatory criterion.
Editorial publications beat personal blogs
Not all published content is equal in the assessors’ eyes. Personal blogs on Medium or Hashnode, where anyone can publish without review, carry less weight than editorial publications and are often disregarded entirely.
We leaned on articles published on outlets with editorial gatekeeping. These went through review before publication, so they represent someone else deciding the work was worth publishing, rather than self-promotion.
The presentation was efficient too. Instead of submitting each article as a separate piece of evidence, we used a single screenshot of the author profile page showing the full publication history. That consolidated several articles into one piece and showed sustained technical writing over time, not a one-off.
Industry recognition is not the same as being good at your job
One of the most common rejection patterns: applicants prove they’re excellent employees but never show industry-level recognition. Being good at your job is not the same as being known in your field.
While preparing, we read through a rejected AI/ML application on this forum, and it was instructive. Everything in it demonstrated job performance, but nothing showed the wider industry knew who the person was.
So we inverted the framing. Instead of leading with what he’d accomplished at work, the evidence led with external recognition: speaking panels, published articles, community leadership. The employment context supported these rather than defining them. That shift, from “I’m a great employee” to “I’m recognised in my field”, changes how an assessor reads every other piece of evidence.
Back every claim with third-party evidence
Assessors review hundreds of applications and have seen every inflated metric and self-aggrandising statement. Without external validation, impressive statistics look like fabrication.
So every significant claim was backed by someone outside his immediate circle. Product adoption numbers weren’t just internal dashboard screenshots; they were corroborated by reference letters from product managers who could verify them. Community impact was demonstrated through testimonials from senior industry figures, not just stated.
The pattern is simple: make a claim, then show someone independent can verify it. That’s what turns assertions into facts an assessor will trust, because the assessor has no reason to take an applicant at their word.
Community leadership as OC2 evidence
OC2 asks you to show contribution to the digital technology sector outside your paid job. Running a London tech meetup gave us strong evidence here.
The meetup had been running consistently, but screenshots of event pages weren’t enough on their own. The key was getting endorsement from the right people. Rather than testimonials from random attendees, we secured support from speakers and senior figures who had presented at the events. Those carry weight because they come from people an assessor might recognise or could easily verify.
We also emphasised sustained activity over one-off involvement. Running the meetup for around a year showed consistent commitment. For community work to count, the assessor needs to see a pattern, not a single event.
Connecting DevRel work to commercial outcomes (OC3)
DevRel is a particular challenge for OC3, which is about commercial or technical contribution. The impact is usually indirect: articles drive awareness, community work builds trust, content educates future users. Connecting that to hard commercial outcomes takes deliberate evidence.
We used internal company data showing product adoption for a new database release. A presentation slide showed the latest version had better adoption than previous ones. On its own that wasn’t enough, so the evidence explicitly linked his community evangelism, open-source projects, and technical articles to that adoption.
A reference letter from the Product Manager reinforced the connection between the DevRel activity and the commercial result. Winning an internal hackathon for building a plugin integration added concrete technical contribution that directly benefited the product. Together, that turned indirect influence into documented commercial impact, which is exactly what DevRel people struggle to do.
What carries over to other applicants
This applies to anyone whose impact is spread across communities, content, and influence rather than one product:
- Lead with recognition, not job performance.
- Back every claim with someone independent who can verify it.
- Pick platforms and endorsers that carry credibility of their own.
- Connect indirect work to a measurable outcome.
Happy to answer questions in the thread. Best of luck in your applications 