UK Global Talent visa for software engineers: what counts as evidence
By Mac · · 6 minute read
Software engineers are one of the groups Tech Nation's criteria were designed for. The guide lists principal engineers, DevOps and SysOps engineers, back-end, front-end and mobile developers, and CTOs or VPs of engineering among typical technical applicants. The challenge is rarely being eligible in principle; it is proving your contribution with documents.
What Tech Nation looks for in technical applicants
The guide describes technical applicants as showing proven technical expertise with current technologies: building, using, deploying or exploiting a technology stack and its infrastructure. Technical people working in non-technical organisations (for example a bank's engineering team) are eligible.
The mandatory criterion: recognition
For engineers, recognition often comes from:
- Open source. Leading or significantly contributing to a substantial project, shown with commit history, stars, downloads and maintainers acknowledging your work.
- Speaking at respected technical conferences, with the programme listing and audience size.
- Awards for technical excellence from recognised bodies (not internal company awards).
- Published material about your work in respected technical or trade publications.
- Judging or reviewing others' work, for example at hackathons or as a reviewer.
- High pay compared with the market, supported by contracts and earnings. On its own this is not enough; you also need to show impact beyond your day-to-day role.
Self-published posts on LinkedIn or Medium are not accepted as media recognition for this criterion.
Optional criteria engineers often use
OC3 – significant technical contribution. The most common choice. Show what you built or led, and what changed because of it: systems you designed, performance or cost improvements, reliability, scale (users, transactions, requests). Letters from your CTO or engineering director that give figures, plus annotated architecture diagrams or dashboards, make this concrete.
OC2 – contribution outside work. Open source, mentoring, running meetups, teaching on bootcamps, or writing for respected technical publications.
OC1 – innovation. If you worked on something genuinely new in your market, for example the first product of its kind, a novel technical approach or a patent.
Showing your contribution
The most common weakness in engineering applications is evidence that shows the company's success but not your part in it. For every document, make it clear:
- what you personally designed, built or led;
- the before and after, in numbers;
- who can confirm it (a senior leader's letter, a commit history, a design document with your name).
Evidence that works for engineers
- Commit summaries and contribution graphs for public projects
- Architecture diagrams with your role labelled
- Dashboards showing latency, uptime, cost or scale before and after your work
- Conference programme listings and recordings
- Letters from engineering leaders that quote specific results
Free download: get our one-page Global Talent evidence checklist: every document, limit and rule on a single page.
This article explains the rules published on GOV.UK and in the Tech Nation guide as we read them on 18 November 2026. Rules change, so check the official guidance before you rely on it. It is general information, not legal or immigration advice.