Stage 1 check my eligibility - Global Talent Visa

Stage 1: Tech Nation Endorsement
1

Exceptional Promise eligibility review — Smart Contract Engineer(Blockchain Engineer) and Security Researcher

Hello everyone,

I am considering applying for the UK Global Talent Visa under the Exceptional Promise route and would appreciate an honest assessment of my eligibility and proposed criteria.

Profile

  • Technical applicant specialising in Solidity, EVM smart contracts, DeFi protocol development, and blockchain security.
  • Approximately 4 years and 8 months of non-overlapping paid technology experience.
  • Six-month software engineering internship followed by six months as an Amazon Software Development Engineer in 2020.
  • Career break in 2021 to upskill in Web3 and blockchain.
  • Working professionally in smart-contract engineering since January 2023.
  • Currently a Senior Smart Contract Engineer at one protocol.
  • Getting paid $150,000 salary while working remotely from India. (Not sure if this puts any weight)

CORE DOCUMENTS

  • Recommendation Letters
    • Recommendation Letter from CTO of previous 2 Company where I worked
    • Recommendation Letter from ** CTO of my current company** (Knows my work)
  • Personal Statement
  • Curriculum Vitae (CV)

Potential Mandatory Criterion evidence

MC1 — Winner of security contest

  • Individual winner of security contest organized by one security company.
  • Received a $10,000 prize.
  • A public results announcement is available and will be included.

MC2 — Securing grant from one of the largest defi protocol

  • Received a competitively assessed $11,000 grant in April 2023.
  • Public proposal, approval, and payment evidence are available.

MC3 — Public security-research record

  • 16 High and 18 Medium valid vulnerability findings.
  • Four top-10 finishes and seven payouts across public security competitions.

Potential OC3 — Significant technical contribution

Company 1 - Senior Solidity Engineer

  • Led the design-to-mainnet development of their products working as a only Solidity Engineer directly under CTO, associated with approximately $40 million in funds.

Company 2

  • Developed the integration of their product with other company processing funds of more than $10 million.

Company 3

  • Led the end to end development of product working as a solo developer along with CTO.
  • The contracts passed external audits without critical findings and are live on Ethereum mainnet.

I plan to support these claims with public repositories, audit reports, architecture/design evidence, mainnet deployments, TVL data, and letters confirming my personal contribution.

Possible second optional criterion

I have participated in a structured mentoring programme run by one organization where I was awarded $6000 to mentor one engineer. I also conduct public security research outside my primary employment, although the competitions provide prizes or payouts.

I am unsure whether I should use:

  • OC1 for innovation as an employee working on new DeFi concepts; or
  • OC2 for structured mentoring and contributions outside my primary occupation.

Questions

  • What weaknesses or evidence gaps should I address before applying?

Thank you for reviewing my profile. I would appreciate candid feedback.

2

Your MC evidence is the strongest area. The contest win and the competitively assessed grant are individually judged recognition of you personally, which is what the Guide anchors MC on rather than employer achievements. Make sure each piece names you as the recipient and shows how the selection worked, since that is what separates recognition from participation.

On the OC1 versus OC2 question, go with OC2. The Guide’s OC1 bar wants genuine novel innovation: a granted patent, a new product-led venture, or work in a genuinely new digital field. Framing employee work on new DeFi concepts against that bar is hard, and it reads as strong engineering rather than innovation. Your mentoring and independent security research sit more naturally under OC2 as contributions beyond your paid role, and they are easier to evidence at the Promise level.

Overlap is the thing to watch. Your security-research record is carrying MC as recognition, and you also want to lean on independent research for OC2. The same findings counted twice weakens both. Keep MC about the wins and placements, and build OC2 on distinct activity like the mentoring programme.

OC3 rests entirely on the letters confirming your personal contribution to each protocol. Mainnet deployments and TVL figures show the work exists; a letter from the CTO tying specific design decisions to you is what turns that into significant personal contribution. The salary carries no independent weight, so leave it out and let the technical work speak.

3

Thanks a lot @Akash_Joshi . On the scale of 1-10, how would you rate my profile for qualification of GTV? I have recently read that they are not giving visas easily for digital technology on reddit.

4

If I had to put a number on it for Promise, you sit around a 7. The contest win and the competitively assessed grant give you a real MC floor that most applicants never reach, so you are not starting from a weak base. What holds it back from an 8 or 9 is the OC picture: your OC2 activity and OC3 letters are the pieces still to be locked down, and until the mentoring and the CTO attribution letters are firmly in place, there is genuine variance in how a panel reads them. Tighten those and you move up the scale.

The Reddit worry is overblown. Digital technology has no quota and no seasonal squeeze, and endorsements in your space are granted every month. What actually sinks applications is category fit: evidence filed under the wrong criterion, or a case that leans on the employer’s achievements instead of the applicant’s own recognition. That is a fixable framing problem, and your profile already avoids the worst of it. Focus your energy on the OC2 versus OC3 split we discussed, and treat the difficulty chatter as noise.

5

Hi @parth_15

When you’re describing what you do, it’s better to clearly relate it to an eligible role , something like experienced backend/blockchain engineer, eligibility is usually the first thing, I believe they check during assessment, so it helps set the right foundation.

About your MC security contest you need to clarify what exactly you competed for. Was it data security software, a cybersecurity detection algorithm, or something similar? If the contest required participants to build something and yours was selected because it was more valuable, that’s where the recognition comes in. You’ll need evidence of your invitation to participate, what you built, and proof of winning. If you present it that way, it can work.

For the grant, simply receiving it won’t show recognition unless you also show what you did that led to the grant. The amount is quite low, so it may not be seen as meaningful relative to what Tech Nation expects for MC. Also, because you approached them for the grant, it weakens the recognition angle. If you can show acceptance criteria or approval requirements, that can help. Payment evidence with your name can support it. The 16 high and 18 medium vulnerability findings won’t show recognition or sector impact.

For OC3, you’ve explained your work well and public repos, audit reports, architecture/design evidence, mainnet deployments, TVL data, and letters confirming your personal contribution can be okay. But the companies must be product‑led companies, and you need to clearly show individual ownership. The letter should also mention the commercial impact that resulted from your technical contributions.

Paid mentoring of an engineer won’t work for OC2 because it’s not voluntary. The research you participated in, where you received a payout, looks more like market research, companies often pay participants for that, so it doesn’t show sector advancement.

On your question about choosing between OC1 or OC2. You’ll need to mention the specific evidence you plan to use so I can tell what aligns best with the guidance and your narrative.

You do have some evidence that can work, but overall you need stronger, more convincing pieces that clearly align with the criteria to increase your chances.

Going by the recent feedback and the high level evidence you have listed here, if you are thinking numbers, 3/10.

All the best.

6

Overall, this looks like a potentially strong Exceptional Promise profile, particularly because the security contest win, competitive grant and public vulnerability record give you recognisable external evidence. The main question will be how convincingly you connect those achievements to your individual reputation and trajectory as an emerging leader, rather than simply showing that you are a technically capable engineer.

Your MC evidence is probably the strongest part. The security contest win provides clear third-party recognition, while the competitive grant can also support the case if the evidence shows its competitive nature, why it was awarded to you and its significance. For the vulnerability findings, make sure the evidence clearly establishes that the findings are yours, are valid/accepted, and demonstrate recognition within the digital technology/security community. The $150k salary is a useful background but I would not make it a central pillar of the application.

For OC3, your proposed structure is sensible. Public repositories, audit reports, deployment records and TVL/funds handled can establish impact, but the critical point is separating your personal technical contribution from the company’s overall success. Ideally, each project should show what you personally designed/built, the technical significance, and the resulting measurable impact, with independent corroboration where possible.

Between OC1 and OC2, I would lean towards OC2 if the mentoring programme is genuinely structured and clearly outside your normal employment. Your security competitions can also support the broader narrative of contribution outside your job, but avoid presenting prize-winning security work as mentoring unless the evidence actually demonstrates that.

The main gap I would address is independent validation of your professional impact. CTO letters are useful, but where possible strengthen them with public audit reports, competition results, protocol announcements, repositories, third-party coverage, grants, or other evidence that does not originate solely from your employers.

Also keep the application focused. You don’t need to prove every achievement you have; you need a coherent case showing recognition + emerging leadership + significant technical contribution + credible future potential in UK digital technology.