DevRel wins on
authored artefacts developers adopt
— not follower counts, impressions, or talks given.

Reference letter from a maintainer of a project that adopted your SDK: 'I maintain [open-source project] and have worked with [Advocate] since [Year]. They authored [the specific SDK / sample framework / docs], now depended on by [N] downstream projects and downloaded [figure] times. Their specific contribution was [precise work — e.g. the client library and the reference integration]. Beyond authoring it, they drove its adoption through [named-conference keynote / the docs they wrote], and I'd place them among the people who materially shaped how developers use [technology].'

Adoption-impact narrative for the personal statement: 'As DX lead at [Company] I authored the [SDK / sample framework] ([public repo]) and owned the developer-adoption programme. Over [period] SDK downloads grew from [X] to [Y], API sign-ups from [X] to [Y], and activation rate improved from [X%] to [Y%] — attributable to the [specific artefact / docs overhaul / sample-repo programme] I built. The numbers are corroborated in [public product metrics / a case study], and [named referee outside my reporting line] can attest to my specific scope.'

Letter ask you can send to a conference programme chair or recognised-programme lead: 'Hi [Name], I'm applying for the UK Global Talent visa under Tech Nation. The panel weights external recognition it can verify — a keynote acceptance, a recognised-programme membership — over audience size. Would you write a 1-page letter on [the accepted keynote / my GDE / CNCF Ambassador standing] — what it required, how competitive it was, and how the work is regarded? I can share a short brief on what the panel's recognition criterion looks for.'

Innovation-criterion narrative example: 'Authored [open-source SDK / sample framework / docs system] ([Year], [public repo]). It introduced [specific pattern — e.g. the first typed client for X / a reference DX for Y], adopted by [N named projects], downloaded [figure] times, and cited in [N] conference talks. Maintained through [N] releases since.'

Recognition narrative example: 'Google Developer Expert (Web / Cloud), [Year]–present. Accepted keynote at [KubeCon / re:Invent / Google I/O] [Year] ([attendance]). Author of [technical book] ([publisher], [Year]), [N] copies sold. Programme-committee member for [named conference] [Year].'

Tech Nation assesses contribution to the digital technology sector, and it can only reward what it can verify as technical, not marketing. Much of a developer advocate's day-job — social posts, a growing following, community management, giving talks — looks like marketing, and the panel discounts marketing and vanity metrics. A follower count, an impressions figure, and 'I grew our Discord to 20,000 members' are the weakest lines an advocate can lead with: they're easily gamed and tell the panel nothing about whether any developer adopted anything because of you.

The advocates who clear the bar convert audience into verifiable technical contribution: an authored SDK or sample framework with download and dependent-project counts, docs or a course with checkable reach and adoption, attributable developer-adoption numbers from a programme they ran, keynotes at named conferences, and a recognised-programme badge. The through-line is authorship and adoption — something you built that developers use — plus third-party attestation the panel can confirm.

External recognition for an advocate means: (a) artefacts others adopt — an SDK, a sample framework, docs, a course, a book developers use; (b) third-party attestation — accepted keynotes at named conferences, recognised-programme membership (GDE / MVP / GitHub Star / CNCF Ambassador / Docker Captain), programme-committee or standards roles; (c) a verifiable footprint — package-registry downloads, dependent-project counts, publisher sales figures, public programme profiles, conference programmes.

If you read this section and realise your record is a following and a stack of unnamed talks, that's the most valuable finding you can make before applying. The fix is not a better-worded personal statement — it's authoring an artefact developers adopt, landing an accepted keynote at a named venue, and earning a recognised-programme badge, or applying for Promise, where building that footprint is the expected profile.

Pattern 1 — engineer who advocates (strongest): authored, adopted OSS / SDK / sample framework (download and dependent-project counts) plus keynotes at named conferences about it. Shipped the code, then advocated for it — the profile most likely to reach Talent, because the technical contribution is unambiguous.

Pattern 2 — adoption-impact owner: a DX programme you ran with attributable developer-adoption numbers (SDK downloads, API sign-ups, activation lift) backed by public metrics or a case study, plus one external recognition signal. Commercial impact via developer adoption is a strong lever for this cohort.

Pattern 3 — recognised-programme advocate: Google Developer Expert, Microsoft MVP, GitHub Star, CNCF Ambassador, or Docker Captain standing plus accepted named-conference keynotes and authored content. The programme badge is a clean, verifiable recognition artefact; pair it with an authored artefact for technical contribution.

Pattern 4 — author / educator: a technical book with a major publisher or a widely-adopted course / docs system, with verifiable sales or enrolment, plus named-conference talks. Verifiable in publisher and course-platform figures; a strong recognition and innovation pattern.

Pattern 5 — typical advocate building externally (Promise): a growing footprint — first named-conference acceptances, an SDK gaining adoption, an early recognised-programme nomination. The honest fit is Exceptional Promise, not Talent.

Rejection 1 — follower / subscriber / impressions counts as recognition. Fix: these are vanity metrics the panel discounts. Replace with named-conference keynote acceptance, a recognised-programme badge (GDE / MVP / CNCF Ambassador), an authored artefact developers adopted, or attributable adoption numbers.

Rejection 2 — 'I've given N talks' with no venue prestige. Fix: recognition is a keynote or competitive-CFP acceptance at a named conference. Name the venue, show the acceptance and the competitiveness — one accepted KubeCon / re:Invent keynote beats fifty unnamed meetup talks.

Rejection 3 — community-size metrics with no engineering substance. Fix: community size is a growth metric, not contribution. Point at an authored SDK / sample framework / docs and its download or dependent-project counts, or attributable activation numbers.

Rejection 4 — marketing / growth metrics framed as technical contribution. Fix: attribute a developer-adoption number precisely to a DX artefact you built and a third-party source, or satisfy your 2-of-4 via Recognition plus Innovation and drop the technical-contribution claim.

Rejection 5 — 'I evangelise product X' with no authored artefact. Fix: author something developers adopt (an SDK, sample framework, docs, course), show the adoption, and lead with it. If no artefact exists yet, apply for Promise and build it first.

Day one of Global Talent grant: you can work for any UK employer, hold multiple DevRel or DX roles, run your own UK or non-UK company, contract, freelance, advise, or continue maintaining a remote open-source project. There's no SOC code, no salary floor (vs Skilled Worker), and no employer-tied amendment process — useful for advocates who keep an independent content, course, or open-source practice alongside a main role.

Compensation context: senior developer-advocate and DX-lead salaries in London run roughly £80–140k, with head-of-DevRel and DX-lead roles at scaled developer-tools and platform companies reaching £150k+ base plus equity. Total comp at UK arms of US developer-tools companies, which often keep US RSU rates, can run well above the local base — DevRel is a well-paid function at API-first and infrastructure firms.

Founder and independent optionality: Global Talent permits founding companies, running a paid course or content business, and advisory work — directly relevant for advocates moving toward founder, independent-educator, or fractional-DevRel paths. The SEIS / EIS investor-incentive schemes favour early-stage equity, and the UK has a dense developer-tools and API-first startup base.

ILR clock: 3 years for Talent, 5 years for Promise. Time spent outside the UK over 180 days in any rolling 12-month period can break the clock — track it meticulously, especially if you travel heavily for conferences and developer events. After ILR the route's conditions fall away; British citizenship is reachable 12 months after ILR.