For product managers applying to Tech Nation
I was refused the Global Talent visa. Here is how to avoid my mistake.
Read this before you pay the £561 endorsement fee, because that fee is not refunded if you are refused.
If you work in this field, you probably assume your product launches speak for themselves. To a Tech Nation assessor, they only speak if you show them in the right format, with the right proof, against the right criteria.
I know this because it happened to me. Below is my story, the mistakes that cause most refusals, and how to avoid them. All of it is free to read. Keep going.
My story
I did it myself. I made a lot of mistakes. Then I got endorsed.
I applied for the Global Talent visa myself, and I was refused.
Looking back, I made a lot of mistakes, not just one. I chose the wrong criteria for my profile. I did not put my evidence together properly. And there were more small errors that added up, the kind you only spot once someone shows you what an assessor looks for.
A refusal is painful. The endorsement fee is not refunded, you lose months, and you start again from the beginning. It is also easy to take the wrong lesson from it, like deciding you are not good enough. That was not the lesson.
So I went back through the rules, found every place my application had gone wrong, and fixed each one. I applied again, and this time I was endorsed. I did the whole application myself.
That is why this guide exists. My goal is to help you avoid the mistakes I made, so you can get it right the first time.
The biggest mistake
The mistake that cost me: choosing the wrong criteria
To be endorsed on the Talent route, you must meet the Mandatory Criterion and two of the four Optional Criteria. In short, the four are innovation (OC1), recognition beyond your job (OC2), the impact of what you built or led (OC3), and research or academic work (OC4).
Here is the trap. You can have strong evidence and still be refused, because you lined it up against criteria it does not prove. The assessor does not rearrange your case for you. They check what you claimed.
As a rough guide, this is how strong evidence maps to the right criterion for product managers:
| If your strongest evidence is… | Lead with |
|---|---|
| Outside people choosing you: press, awards, judging, invited talks | MC, recognition as a leader |
| Mentoring, teaching or writing beyond your job | OC2, work beyond your job |
| A launch with revenue or user results, linked to you by a named letter | OC3, impact |
| A product you created that independent sources call new | OC1, innovation |
That table is the short version. Your own mix of evidence decides the best pair, and the wrong pair is the quickest way to a refusal. Criteria are only the first of the common mistakes. Here they are for product managers.
Why product managers get refused
Seven reasons product managers get refused, and how the guide helps you avoid them.
01
Applying from a delivery role or a non-tech employer
Business skills only count at product-led tech companies, and Tech Nation says non-technical applicants from non-technical organisations are generally not eligible.
The guide gives a three-question product-led test for every employer, and shows how to present in-house and big-tech product work.
02
Listing features shipped instead of outcomes
A roadmap or release list doesn’t show what changed for users or the business.
The guide shows how to build an evidence chain from your product work to launch, users, revenue and funding, with proof for each link.
03
Claiming the team’s results as your own
Assessors reject outcomes described as a team effort, and ask what you personally owned and decided.
The guide shows how to state your role, your team and your decisions in one line, and have referees and investors confirm them.
04
Templated or colleague-only letters
Letters with the same structure or phrasing raise authenticity concerns, and letters that repeat your CV add nothing.
The guide shows how to brief three referees, including one from outside your employers, so each writes in their own words.
05
Relying on your own dashboards
Assessors treat internal dashboards, screenshots and self-written descriptions as self-reported.
The guide lists 20 kinds of third-party proof, from investor announcements to partner confirmations, to back every number.
06
Leaning on salary and self-published posts
Salary alone is insufficient, and self-published LinkedIn or Medium posts rarely carry a criterion.
The guide shows which recognition counts for product managers under Tech Nation’s rules: main-stage talks, judging, awards, unpaid invited writing and in-person mentoring.
07
A CV that doesn’t match LinkedIn
Assessors cross-check dates and titles, and unexplained gaps are cited in refusals.
The guide gives a 3-page CV layout and a final check that every date, title and figure matches across your CV, letters, statement and LinkedIn.
How to avoid them
The five-step approach that avoids them
The combination that works best for most product managers is the Mandatory Criterion plus Optional Criteria 2 and 3: your recognition, your mentoring, teaching and writing beyond your job, and the commercial impact of the products you led. Here is how to build a case on it.
Check your employer against the product-led test. Product managers who took a product from discovery to launch at a product-led company fit. Product owners managing a backlog for a delivery team at an agency, and roles in corporate IT or internal tools, struggle.
Choose your criteria on purpose. Pick the pair you can prove best, instead of trying to cover everything. This is the step that sank my first application.
Turn your work into short evidence documents. Each one is limited to 3 sides of A4 and ties to one criterion.
Back every claim with proof an assessor can check. Third-party proof beats your own screenshots, and your referees should write in their own words.
Run a final consistency check. Dates, titles and figures must match across your CV, letters, statement and LinkedIn before you submit.
That is the outline. Doing it well is where the detail matters, and the next section shows what that detail looks like.
A page from the guide
This is what an evidence document looks like
Here is one page from the guide, so you can see the level of detail before you decide. It shows which product roles pass the first test.
Product roles that fit, and product roles that struggle
Fits: product managers who took a product or major feature from discovery to launch at a product-led company, with results; senior and principal product managers who own a product line and its revenue; heads of product and chief product officers at start-ups and scale-ups; growth, platform or API product managers whose work moved the numbers.
Struggles: product owners who manage a backlog for a delivery team at a consultancy or agency; project or programme managers with a product title but no ownership of outcomes; product managers whose only employers are banks, telcos or retailers building internal tools; product managers with a strong day job but nothing public.
What to do if your role struggles
- Leave corporate IT, ERP and internal-systems work out of the evidence.
- A non-profit you volunteer for can support Optional Criterion 2, as work outside your job.
- Build outside recognition before you apply: talks, writing, mentoring, judging or press.
The guide has worked samples like this for every kind of evidence, with the proof pages listed, so you know what to gather before you write.
If you are refused
What an appeal looks like, decoded
A refusal is not always the end. The guide includes anonymised refusal cases as reported by applicants, plus a review method. Here is one of them.
The Promise product manager whose evidence was about her job
A product manager at a start-up backed by a well-known US accelerator applied for Exceptional Promise. Three of her four Mandatory Criterion documents described products she had built, using product documents, chat screenshots and standup calls. The refusal said her OC3 evidence did “not link individual contributions to outcomes”.
Lesson: Documents about your own products are not recognition. The Mandatory Criterion needs people outside your company choosing you.
Three refusal lines, decoded
| What the refusal said | What it really meant |
|---|---|
| OC3 evidence did “not link individual contributions to outcomes” | The proof that you led the work must sit in the same document as the outcome. |
| She had ticked OC1 but given OC2 evidence, and one letter came from her company’s co-founder | Match each document to the criterion it supports, and use referees from outside your own company. |
| Analytics and sales-tool screenshots did not show a connection to the applicant (a second case) | Put a head of product’s letter behind every screenshot, and point to it by document, paragraph and line. |
The guide gives you the full set of cases and the review method, so you know how to answer each kind of refusal if it happens to you.
Cases are anonymised and reported by applicants. They show how others have handled refusals, and no one can promise the same result. The guide is general information, not legal advice.
Want more?
The Endorsement Guide for Product Managers
The guide takes every step above and shows you how to do it, with Tech Nation’s own rules for each document. It is 119 pages in 7 parts, aligned with Tech Nation’s applicant guide, and you download it as a PDF straight after paying.
- 10-document mock evidence pack
- Evidence, letter, CV and statement templates
- 20 evidence checklists, a 12-week planner and final checks
What's inside
Everything you need to go from first draft to submitted.
PDF · 7 parts · 119 pages
The guide
- How the route works
- Are you eligible as a product manager?
- The application pack at a glance, with Tech Nation’s rules for every document
- Choosing your criteria: why MC + OC2 + OC3
- Mandatory Criterion: recognised as a leader
- Optional Criterion 2: recognition beyond your job
- Optional Criterion 3: significant contributions and the evidence chain
- Optional Criteria 1 and 4: the alternatives
- The 3-page evidence template
- Recommendation letters
- Third-party verification of your personal impact
- Your CV
- Your personal statement
- No evidence yet? A 12-month plan
- Common mistakes
- The six rejection patterns and 18 fixes
- What real refusals say: 4 applicant-reported cases and 12 more fixes
- How to request a review (appeal) and win, with a worked example
- Pre-submission checklist
- Evidence checklists for 20 kinds of evidence
- Your 12-week application planner and trackers
Worked example
10-document mock evidence pack
A complete fictional application with every document in the 3-page format, built from Tech Nation’s rules and publicly reported endorsed product manager cases, plus 4 swap-in documents for Optional Criteria 1 and 4.
Templates
Evidence, letter, CV and statement templates
A fill-in 3-page evidence template, what every recommendation letter must include, a 3-page CV layout and a personal statement plan, each with fictional samples.
Checklists
20 evidence checklists, a 12-week planner and final checks
A checklist for every kind of product manager evidence, a week-by-week planner with evidence and referee trackers, 30 refusal fixes, 4 applicant-reported refusal cases with the wording decoded, a worked review (appeal) and a pre-submission checklist.
If you are just starting
Planning your first application
Choose your criteria first, then follow the 12-week planner. Collect the right evidence while you still have time to get it, instead of finding gaps the week you submit.
If you were already refused
Planning to reapply or request a review
Use the refusal fixes and the review method to read what the decision really meant and decide your next move. I reapplied after a refusal, and it worked.
Success stories
From evidence pack to endorsement
Real messages from people Tech Immigrate has helped. Names hidden for privacy.
Stop and think
You have two options
Option 1: work it out alone
Free, plus your time
- Read the official guidance and piece together what counts
- Guess which criteria and evidence an assessor will accept
- Submit, then wait for the decision
- If refused, pay the £561 fee again and wait again
Option 2: use the guide
$79$30 one-time
- Pick the right criteria before you write anything
- Copy the format from a full worked example
- Check everything before you pay the fee
- Instant PDF download
UK immigration solicitors typically quote £2,000 to £5,000 to help with a Global Talent application. One refusal costs the £561 fee. The guide costs less than a tenth of that.
Get your head start today
- Pick the right criteria before you write anything
- 10-document mock evidence pack
- 20 evidence checklists, a 12-week planner and final checks
- Evidence, letter, CV and statement templates
Limited-time offer ends 31 October.
Secure checkout by Stripe · Instant PDF download
The guide is general information, not legal advice, and no one can guarantee an endorsement.
Questions about this guide
Possibly, but it’s harder. Tech Nation says non-technical applicants from non-technical organisations are generally not eligible. Section 2 gives the product-led test employer by employer and explains when an in-house digital product can count, and Section 13 gives a 12-month plan to build evidence from product work and contributions outside your job.
Yes, if most of your evidence is product outcomes. Section 2 explains when a product manager is assessed as a technical applicant instead of a business applicant. If your strongest evidence is your code, the Software Developers guide is a better fit; if it is the company you founded, such as customers, revenue and funding, the Startup Founders guide is.
No. The samples follow a fictional applicant, Wanjiru Kamau, a head of product, and show the standard to aim for. Tech Nation says templated letters and anything written with AI tools are not acceptable, so your referees must write in their own words about work they saw.
Yes. This guide is written for Product Managers specifically, so it shows how to present your own kind of work, not engineering work, as evidence against the criteria. It does not assume you write code.
The route has two levels: Exceptional Talent for established leaders and Exceptional Promise for people earlier in their careers. The guide explains the difference and how to work out which one your record fits. It cannot promise either outcome. Whether you are endorsed is decided by the assessors.
The guide gives you evidence checklists and a planner, so you work through the application in order instead of facing everything at once. That is exactly where I lost time on my first attempt.
Section 14C explains how to request a review within 28 days, how to write each point with a full worked example, and when to fix your pack and reapply instead. Section 14B decodes refusal wording that product managers have published, with fixes.
Yes, briefly. Section 1 covers the visa fee, timings, the healthcare surcharge and dependants. The rest of the guide focuses on endorsement, where almost every refusal happens.
Yes. It follows Tech Nation’s Global Talent Visa Application Guide (last updated 27 February 2026), read in full in September 2026, including its rules on business applicants, in-person mentoring, main-stage talks, salary evidence, letters and AI tools. The mock pack was checked against the same rules. Rules can change, so check GOV.UK and Tech Nation’s guide on the day you apply.
Section 16 has a checklist for each of 20 kinds of evidence, showing what each document must have, what makes it stronger and the red flags that get it dismissed. Section 17 is a 12-week planner with key dates, tasks by stage and trackers for your evidence, referees and supporting letters.
Because the guides are digital downloads you can access straight away, sales are final once you’ve downloaded them. If a file is faulty or won’t open, email [email protected] and we’ll fix it or refund you.
Yes. It was checked against the rules in October 2026. If we update it, buyers get the new version in their downloads at no extra cost.
Straight after payment. You can download the PDF right away, and you can come back to your downloads page later using the email you paid with.
Checkout is by Stripe and takes major debit and credit cards. If a payment fails, email [email protected] and we will help you sort it out.
This one is written for product managers. Product managers, group PMs, heads of product and CPOs. Other roles have their own guides.
No, and nobody can. The guide shows you how to build the strongest case you can. The decision is Tech Nation’s.
Email [email protected] and we will reply.