Reliability and platform work wins on
external artefacts
— not your internal on-call rota.

Reference letter from a co-maintainer or downstream user of your open-source work: 'I have collaborated with [Engineer] on [CNCF project] since [Year]. They are a named maintainer in the project's OWNERS file and own [specific area — e.g. the autoscaling controller / the OTLP exporter]. Their specific contribution was [precise work — e.g. designing and landing the leader-election rewrite in v[X]]. The project is run in production by [named companies including ones we don't control], and I'd place [Engineer] among the most influential contributors to this area of the cloud-native ecosystem.'

Quantified reliability-impact narrative for the personal statement: 'As staff SRE on [Service] at [Company], led the reliability programme that reduced p99 latency from 1.4s to 95ms and improved availability from 99.9% to 99.99% across 8B+ daily requests, by introducing [specific change — e.g. an error-budget-driven release gate and load-shedding at the edge]. The approach is documented at [public engineering-blog URL] (42,000 reads) and was the subject of my track talk at SREcon EMEA 2025 (650 in-person, 9,000 on-demand views).'

Open-source maintainer-letter ask you can send to a co-maintainer: 'Hi [Name], I'm applying for the UK Global Talent visa under Tech Nation. The panel weights letters from collaborators outside my employer who can speak to a specific external contribution. Would you write a 1-page letter on my maintainer role on [project] — the area I own, a concrete change I landed, and who runs it in production? I can share a short brief on what the panel's technical-contribution and recognition criteria look for.'

Innovation-criterion narrative example: 'Authored [open-source operator / tool] (v1.0 [Year]), maintainer and top contributor by review count, run in production at [named users]. It introduced [specific novel approach — e.g. declarative progressive-delivery for stateful workloads], adopted by [N] downstream projects and cited in [N] conference talks. Maintained through [N] major releases since.'

Recognition narrative example: 'Track talk at KubeCon Europe 2025 (observability track, 1,100 in-person, 18,000 on-demand). OpenTelemetry semantic-conventions contributor (merged [N] spec PRs). Author of [sustained reliability blog / newsletter at verifiable readership]. Programme-committee reviewer for SREcon [region] 2025.'

Tech Nation's guidance distinguishes internal achievement (promoted twice, ran the biggest incident of the year, built the internal platform) from externally-recognised contribution (work attested by people outside your employer). For this cohort the gap is structural: the most impactful reliability work is, by nature, internal and invisible. The applicants who clear the bar are the ones who externalised it.

External recognition here means: (a) artefacts others run or read — a maintained open-source project, public postmortems and reliability writeups, spec contributions; (b) third-party attestation — invitations or accepted CFPs at named conferences, advisory engagements, programme-committee roles; (c) a verifiable footprint — OWNERS-file maintainer status, merged spec PRs, blog or newsletter analytics, conference attendance figures.

'Maintainer of a CNCF-ecosystem project run in production' is the canonical strong pattern for this role. The panel rewards: project name + named user companies + your specific area and contribution (not just 'I made commits') + verifiable governance evidence. Public examples of the kind of work that lands: maintainership across the Kubernetes SIGs, Prometheus / Thanos / Cortex, Grafana / Loki / Tempo, Envoy, Cilium, Argo CD / Workflows, Crossplane, OpenTelemetry, etcd, Helm, and containerd.

Spec and standards work — OpenTelemetry semantic conventions, SLO / SLI conventions, CNCF working-group output — is gold-standard and badly under-claimed. If you've merged conventions PRs or chaired a working group, lead with it; it's verifiable in public archives and reads as peer recognition by definition.

Pattern 1 — CNCF maintainer: named maintainer or top-N contributor on an infrastructure project run in production at companies you don't control. Pair with a named-conference talk + a letter from a co-maintainer or downstream user. This is the strongest single pattern and often supports a Talent application on its own.

Pattern 2 — Reliability author + speaker: a body of public reliability writing with verifiable readership (postmortems, SLO / error-budget practice, on-call design) + an invited or track talk at SREcon, Monitorama, or KubeCon. Strong for both tiers; pairs well with quantified internal impact you've externalised.

Pattern 3 — Standards / spec contributor: merged contributions to OpenTelemetry semantic conventions, SLO conventions, or a CNCF working group + the implementations that follow. Verifiable in public archives — extremely strong, and under-used.

Pattern 4 — Platform engineer at a name-brand infrastructure company: reliability or platform ownership for a service the panel can verify (Stripe, Cloudflare, Datadog, Fastly, a hyperscaler runtime) with public numbers + named-conference talks + contributions to that platform's open-source ecosystem.

Pattern 5 — Systems-reliability researcher: published papers at named venues (OSDI, SOSP, NSDI, USENIX, EuroSys) + open-source implementation. Sometimes a stronger fit for the Royal Society or RAEng peer-review route than Tech Nation; the fast-track applies.

Rejection 1 — applied for Talent on internal-only evidence. Fix: apply for Promise — the bar is meaningfully lower for senior ICs building toward leadership, and on-call leadership plus a growing external footprint is a clean Promise profile. Don't spend an attempt on Talent if your evidence never leaves your employer.

Rejection 2 — 'I use Kubernetes / Terraform / Prometheus at work' framed as technical contribution. Fix: operating a tool is not contributing to it. Reframe as maintainer / top-N contributor with OWNERS-file or contributor-stats evidence and named production users — or drop the claim.

Rejection 3 — certifications presented as recognition. Fix: CKA / CKAD / AWS / GCP corroborate competence, not standing. Replace as recognition evidence with talks, maintainership, public-writing audience, or advisory roles.

Rejection 4 — internal on-call / ops leadership framed as recognition. Fix: externalise it (public postmortem, reliability writeup, named-conference talk with the numbers) or treat it as Promise-tier evidence.

Rejection 5 — personal statement that inventories tools and clouds. Fix: argue the holistic mandatory case instead — what reliability or platform impact you delivered, the numbers, the public artefact that verifies them, and why it benefits a named UK digital sub-sector (fintech, AI infrastructure, healthtech, climate).

Day one of Global Talent grant: you can work for any UK employer, multiple employers simultaneously, your own UK or non-UK company, contract, freelance, or advise. There's no SOC code, no salary floor (vs Skilled Worker), no employer-tied amendment process — useful for platform engineers who do fractional or advisory infrastructure work alongside a main role.

Compensation context: senior SRE and platform-engineering salaries in London run roughly £110–200k for staff+ ICs at scaled tech firms, with principal / infra-lead roles at name-brand companies reaching £230–320k base. Add equity at high-growth companies, and total comp at UK arms of US public companies (which often keep US RSU rates) can approach mid-tier Bay Area packages.

Founder optionality: Global Talent permits founding companies — relevant for engineers building infrastructure or developer-tools startups. The SEIS / EIS investor-incentive schemes are structurally favourable to early-stage equity, and the UK has a dense early-stage VC base across enterprise and infra (Index, Accel London, Notion, Plural, LocalGlobe, Seedcamp, EF).

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 do on-call or travel for an international team. After ILR the route's conditions fall away; British citizenship is reachable 12 months after ILR.