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?
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.