UK Global Talent Visa(Digital Technology) – Evidence Structure (Exceptional Promise)

Stage 1
1

Hi everyone,

First of all, thank you so much for the incredible work you’re all doing in this community. I’ve spent a lot of time reading through the discussions and responses here, and they’ve been extremely helpful in shaping my understanding of the UK Global Talent endorsement process. I’m genuinely grateful for the knowledge and guidance everyone is willing to share.

I’m preparing my UK Global Talent endorsement application under the Digital Technology – Exceptional Promise route and would really appreciate a critical review of my proposed evidence structure.

My background is in software engineering(Almost 5 years), beginning with frontend development and evolving into full-stack engineering, alongside product development and technical leadership as the CTO of a startup I am building. Over the past few years, I have led the design, development, and growth of digital products while contributing both technically and strategically to product direction, engineering execution, and business outcomes.

I intend to apply using:

  • Mandatory Criterion
  • Optional Criterion 2 – Recognition for Work Beyond My Immediate Occupation
  • Optional Criterion 3 – Significant Technical, Commercial or Entrepreneurial Contribution

Mandatory Documents

Personal Statement

Curriculum Vitae

3 Recommendation Letters:

  • CTO at my past company – 18+ years’ experience across multiple CTO and Head of Engineering roles.
  • Senior Software Engineer (US company) & Startup CTO – 12+ years’ experience in software engineering and startup technology leadership.
  • CEO (formerly CTO during the company’s stealth phase) – Worked directly with me on product development and engineering.

Mandatory Criterion (MC)

Evidence 1 – Recognition as CTO Leading a Digital Product

Evidence demonstrating my leadership as CTO of a digital event ticketing platform, including:

  • Led the product strategy, technical direction, and engineering execution from inception.
  • Since launching the product in June 2024, the platform has processed over ₦180 million in transactions, sold more than 20,000 tickets, and supported approximately 100 events under my leadership.
  • Evidence includes:
    • Paystack sales dashboard demonstrating transaction volume and commercial growth.
    • System architecture diagrams illustrating my technical leadership and platform design.
    • GitHub commit history evidencing my direct engineering contributions.
    • Pull request reviews demonstrating engineering leadership and code review responsibilities.
    • Recommendation letters from the CEO and testimonials validating my leadership and contribution.

Evidence 2 – Leadership Through Published Technical Articles

Evidence demonstrating my contribution to the digital technology sector through technical articles published on technology publications, covering software engineering concepts, and digital transformation. Evidence includes publication titles, publication dates, proof of authorship, and audience engagement metrics where available.

Evidence 3(Suplimentary) – High Salary Demonstrating Market Recognition

Evidence demonstrating that my remuneration is significantly above the local market rate for comparable software engineering roles in Nigeria.

Evidence includes:

  • Payslips.
  • Glassdoor salary benchmarks.
  • Local salary comparisons for equivalent roles.
  • Analysis showing my compensation exceeds that of comparable peers.

Optional Criterion 2 (OC2)

Evidence 4 – Mentorship and Community Contribution (2024 - present)

Evidence demonstrating my contribution to the technology community through an invitation-based mentorship programme, where I was invited based on my previous mentoring experience.

Responsibilities and evidence include:

  • Mentored aspiring software engineers.
  • Delivered career development sessions on securing software engineering roles.
  • Reviewed capstone projects and provided technical feedback.
  • Guided students on portfolio development, interview preparation, and industry best practices.
  • Invitation letter, programme documentation, session materials, testimonials, and photos.

Evidence 5 – Technical Mentorship and Industry Knowledge Sharing (2025 - present)

Evidence demonstrating my contribution through a second mentorship programme, where I was invited because of my experience building products and working with international technology companies.

Responsibilities and evidence include:

  • Delivered technical sessions on modern software engineering practices and product development.
  • Shared practical experience from building production systems in startup environments.
  • Conducted code reviews and architecture discussions.
    *Invitation/engagement confirmation, session materials, testimonials, programme documentation, and photos.

Optional Criterion 3 (OC3)

Evidence 6 – Significant Technical Contribution as a Software Engineer/Frontend engineer (Company 1)

Evidence demonstrating my role as one of the early engineers responsible for building the company’s technical foundation from inception. Within a few months of launch, the company successfully raised approximately USD $800k in pre-seed funding.

Evidence includes:

  • Recommendation letter from the Co-founder acknowledging my impact and how it helped with the fundraising.
  • GitHub commits and code contribution history.
  • Crunchbase link confirming the funding round.
  • Evidence describing my technical impact on the company’s early growth.

Evidence 7 – Significant Technical Leadership in Product Development (Company 2)

Evidence demonstrating my contribution after being recruited from a previous company, where I led engineering teams and feature development for a product-led technology company prior to its acquisition.

Evidence includes:

  • Recommendation letter from the CEO.
  • GitHub commits and code contribution history.
  • LinkedIn announcement confirming the acquisition.

Evidence 8 – Significant Technical Contribution to Product Modernisation (Company 3)

Evidence demonstrating my contribution to modernising and enhancing key product features, improving the platform prior to the company’s subsequent acquisition.

Evidence includes:

  • Recommendation letter from the CTO.
  • GitHub commits and code contribution history.
  • Evidence of the company’s acquisition.

I would appreciate feedback and answers to the below questions:

  1. Overall evidence structure: Does my proposed evidence structure appear to be mapped appropriately to the Mandatory Criterion, OC2, and OC3, or are there any obvious gaps or overlaps that I should address?
  2. Mandatory Criterion – Product Leadership: For my first MC evidence (leading a digital event ticketing platform as CTO with measurable commercial growth), is this sufficient for the Mandatory Criterion, or would you expect to see stronger evidence of external recognition in addition to the commercial and technical impact?
  3. Media coverage: I’m scheduled to be interviewed by a technology journalist later this month about the product I lead as CTO. The interview is taking place because we’ve recently launched publicly after building the product in stealth, where only a select number of event organisers had access to the platform. We’ve now gone public and have also started expanding beyond Nigeria, with our first event already running on the platform in Kenya. Assuming the interview is published by a recognised technology publication, would this strengthen my Mandatory Criterion evidence, and if so, how would you recommend incorporating it?
  4. Community contribution: I’m also part of the organising team of a non-profit, faith-based annual technology event that has been running since 2023 and attracts thousands of attendees. As part of the 2024 edition, I helped organise the hackathon, which was conducted online before the main event, with the winners announced on the event day. I was part of the team responsible for planning, coordinating, and running the hackathon. Could this type of contribution support my application? If so:
  • What specific evidence would you recommend including?
  • Would it be more appropriate under the Mandatory Criterion or Optional Criterion 2 (Recognition for work beyond my immediate occupation)?
  1. Overall strength: Based on the evidence structure I’ve outlined, are there any obvious weaknesses or missing pieces that you think I should address before submitting my application?
1 Like
2

@Raphael @Francisca_Chiedu @Akash_Joshi

3

The CTO evidence leans heavily on internal artefacts that sit inside your own company. The Mandatory Criterion explicitly wants recognition from outside that circle, reference letters from leading industry experts or evidence like news clippings, and states that letters of reference alone aren’t sufficient. Nothing in Evidence 1 clears that bar on its own yet.

The upcoming journalist interview changes that, provided it lands in a recognised technology publication rather than a local outlet. That’s the kind of third-party recognition MC is asking for, and it sits stronger inside MC than split off elsewhere.

On the hackathon, organising a single event is a harder sell than your two ongoing mentorship programmes for OC2’s sustained-record requirement. If you use it at all it belongs under OC2 rather than MC, but you already have two solid OC2 pieces and only need two, so I’d leave it out.

Happy to go deeper on the OC3 companies and the acquisition documentation if useful, that’s the area I’d want more scrutiny on before you submit.

2 Likes
4

Thank you very much, @Akash_Joshi, for the response. I am really grateful. Does that mean that the media mention interview coming up can be used as supporting evidence for MC evidence 1(and defend its timing because it comes right after our public lunch and not just as evidence to support the application)? Also, the Paystack sales dashboard is not internal, since it is not an internal dashboard, right? Since it is coming from our payment provider.

5

Hi @Amin_Ajao,

Your recognition as CTO Leading a Digital Product looks okay with external evidence such as Paystack sales and GitHub. However, showing that you are a co‑founder of the company through CAC documents or company credentials will strengthen it. A letter from your CEO may be dismissed as a letter from a colleague since you are on the same level. It’s better to get a letter from a reputable partner in this case.

Published thought leadership articles can work, but were you approached to write them? What is the name of the media outlet? It needs to be reputable. You also need to show that your article went through editorial review, and the metrics must be substantial.

Salary can support your case but is not substantial MC evidence on its own. They still need to see, from your overall application, that you have contributed to the advancement of the sector beyond your job.

For OC2, being invited to mentor as a result of your previous experience can be okay, especially if the organisation is reputable and the mentorship is relevant to the sector. You need to show the invitation letter, demonstrate how you mentored, and the impact of what you did. Programme documentation, session materials, testimonials, and photos can work, but show the invitation and photos first to establish a convincing foundation. Programme documentation, session materials, and testimonials can be easily dismissed. Evidence 4 and 5 appear to be mentorship, you may consider presenting them together, as each evidence set needs to be unique. Using mentorship for both does not show unique evidence.

For OC3, working as a Software Engineer in a company that raised USD $800k in pre seed funding within months shows you built something valuable. However, you need to show how you contributed as an engineer through code commits, contribution history, and a demonstration of your technical impact on the company’s early growth. A Crunchbase link confirming the funding round may not be very useful unless your name is mentioned, so a letter from a C suite person can highlight your contribution as it relates to the funding. For evidence 7, the evidence does not appear strong, commits and contribution history alone are not okay to substantial contribution, also they are directly similar to the previous evidence set, letters are not strong evidence, and LinkedIn announcements are usually not respected. For evidence 8, modernising and enhancing key product features may suggest you did not contribute substantially, you should be showing how you contributed to a product‑led company, not just individual product features. Company acquisition evidence will not show your contributions as a technical employee, although the CTO can mention it, but again, letters are not substantial.

You have some evidence that can serve as a good foundation, but to be honest, I won’t be able to give very useful feedback with just evidence listings.

All the best.

1 Like
6

Thank you very much for the feedback, @Raphael

For the recognition as CTO, I can definitely include the CAC document to support the evidence. Also, the recognition/interview about our public lunch of the same product can stand as supporting evidence to this as well, or stand alone?

7

@Amin_Ajao Well, being a CTO won’t show you were recognised. It’s a role title. It can however, show that you were in the position to have been able to lead the development of a product, team in a technological company. It also depends on the context of the interview as media mention or coverage of a product launch may be dismised as promotional.

All the best.

2 Likes
8

Yes, the interview can sit as supporting evidence inside MC alongside your product leadership piece, and the public launch context does defend the timing. The Guide’s concern about evidence created to support the timing of an application is about pieces manufactured for the submission itself. A journalist independently interviewing you because your product went live and expanded to Kenya is a real event, and the article should say so. Include the publication’s readership figures alongside the article.

You’re right that Paystack sits outside your company. That makes it stronger than internal analytics, though the assessor reads it as commercial evidence. External recognition for MC still needs a separate piece. Paystack corroborates the commercial scale claim, which is useful for OC3, but MC will need the interview and one more externally-validated piece to stand on.

1 Like
9

Your evidence structure is generally well mapped to the chosen criteria, with a clear distinction between product leadership, community contribution, and technical impact.

For the Mandatory Criterion, your CTO role and commercial growth provide a good foundation, but I’d recommend strengthening it with more independent external recognition. If the upcoming interview is published by a recognised technology publication, it would be a valuable addition as it demonstrates recognition beyond your employer. You can include it alongside your product leadership evidence rather than as a standalone document.

Your OC2 evidence also fits well. The mentorship programmes are relevant, and your involvement in organising a large technology event and hackathon would strengthen this criterion. Include evidence such as organiser listings, invitation emails, event agenda, photos, participant numbers, testimonials, or any documentation showing your specific responsibilities and impact.

OC3 appears appropriate, but make sure the focus is on your personal contribution rather than the company’s success. GitHub contributions, recommendation letters, and measurable technical outcomes should clearly demonstrate how your work influenced the product or business.

The only area to watch is relying too heavily on internal evidence such as GitHub commits and architecture diagrams. Balance these with independent validation, measurable outcomes, and third-party recognition wherever possible.

Overall, your structure is solid. My main suggestion would be to strengthen the Mandatory Criterion with more external recognition and ensure each evidence document clearly demonstrates your individual impact without overlapping across criteria.Wishing you the very best with your application.