Review request for Exceptional Talent application

Stage 1: Tech Nation Endorsement
1

Hello everyone, long-time lurker first time poster here. :waving_hand: Would greatly appreciate any feedback on this first draft of evidence breakdown for my application for GTV via the exceptional talent route.

The through line is that I am world class in research and development of high performance software systems, specialising in mathematics, cryptography, and finance, with a proven track record of both practical and financial results.

I have two main complications to manage. The first is that most of my evidence is not attributed to me personally but to my team, which I’m hoping to address with letters attesting to my personal contributions.

The second is that the company names, their relationships, and the product names, are quite confusing, and unfortunately my pieces of evidence have these different names spread around haphazardly.

The story is: I was an early employee at a startup company incorporated as “A”, but known publicly as “B”. We were acquired by company “X”, after which “B” was renamed to “C”. The main product of “A” (the reason it was bought by “X”) is software called “S2”. Awkwardly, a completely new and innovative next generation of “S2”, that we developed from scratch after the acquisition by “X”, was given the underwhelming name “S3” (yes, we literally just changed the number), making our achievement look like a version bump to anyone who didn’t look more closely.

In case it’s relevant, “S2” and “S3” have always been open source projects, even though they were developed by commercial companies and my work for them was paid.

The main things I’m concerned about in my application are:

  • MC has only two weak pieces of evidence

  • Second OC3 evidence is vague

  • How exactly to prove my personal contribution to the team’s successes

With that in mind, here is my evidence breakdown:

Letters of Recommendation from:

  1. Famous researcher in the industry who championed the innovation of “S2” and who successfully advocated using “S3” as standard in the industry’s infrastructure (though it has since been superseded).

  2. University professor at a top US university who is the CEO/founder of a company that uses “S3” as its core enabling technology.

  3. Joint letter from CEO and CTO (founders) of a different company that uses “S3” as its core enabling technology (similar but distinct from the company from letter 2).

MC: Recognition

  1. Salary evidence from “X” that shows salary increasing from 5x to 10x market rate for several years starting at the date of acquisition of “A”. Documents mostly refer to “A” with some from “X”.

  2. First prize for my team (unrelated to work at “A” or “X”) for a competition to imagine, design and develop an innovative product prototype in our industry over the course of a weekend. Unfortunately called a “hackathon”, though it was a bit more sophisticated than a typical hackathon.

    1. Website announcement with my github handle

    2. Photo of me (with the team) on stage receiving the prize

    3. Attestation from other teammates with details of my contribution

OC1: Innovation

  1. Designed and built a core component of “S2” that led to it achieving performance widely believed to be impossible, consequently enabling the creation of a whole new class of systems.

    1. Github evidence (needs letter from colleague who rewrote the github history after my departure as part of a reorganisation which removed my name and added his)

    2. Industry media coverage of the “S2” achievements in general (doesn’t name me personally, refers primarily to “C”, nor the role of my specific contribution to the outcome; relying on the LoR from CTO of “A” below to establish this)

  2. Led the development of performance improvements to “S3” which achieved performance an order of magnitude better than our competitors and remains best-in-class and the baseline against which others are measured (the software component and associated performance benchmark is entirely unrelated to the one in point 1).

    1. Industry media picking up and publishing praise from THE industry founder (which was itself only a Tweet, but it responds directly to the announcement of our results by the CTO of “A”). Media coverage all attribute the results to “C” or “S3 by X”. (Again, relying on the LoR from CTO of “A” below to establish my role in this result)

    2. Github evidence of my personal contributions (pull requests)

    3. Citations in papers as a benchmark

  3. Letter of recommendation from the CTO of “A”, who can vouch for my personal contributions in evidence 1 and 2.

OC3: Impact

  1. Acquisition of company “A” by “X” for almost half a billion dollars. (The acquisition was directly related to new innovations and techniques that I invented and implemented, but unfortunately all those innovations have slipped outside the 5 year window for evidence, even though the acquisition itself is still within the window.)

    1. Industry media coverage of the purchase. These all say “B” was bought by “X” for half a billion dollars. Many cite our particular performance achievement (separate from those mentioned in OC1) that directly led to the acquisition.

    2. Statement in the media from a founder of “X” saying the performance of “S2” was integral to the acquisition.

  2. Industry use of “S3”.

    1. Github stars (900) / forks (400)

    2. Proof of adoption (for a time) as a standard by our industry (mentioned in Recommendation Letter 1)

    3. Companies of the authors of my second and third Recommendation Letters have attracted significant VC funding.

    4. Use by NVidia (unfortunately only acknowledged in an obscure announcement of one of their pieces of software, even though their code shows they copy-pasted my work)

    5. Use by Google indirectly via their use of the product of my third Recommendation Letter’s company (this is an announcement on Google’s homepage; they don’t mention “S3” nor “C” nor even “X”, so attribution is quite indirect)

  3. Letter of recommendation from the CEO of “A”, who can vouch that my personal contributions led directly to the acquisition of “A” by “X”, and the success of “S3” in the industry.

Thanks for reading this far! General impressions and/or specific feedback would be very welcome!

2

Your MC concern is real. Two documents are the published minimum, but they still need to establish recognition of you personally. Salary evidence alone cannot show significant sector impact beyond day-to-day work. For the team prize, show its standing and evidence tying your own contribution to the result.

OC3 needs one clear impact claim. Choose the strongest evidence of actual use, explain why that use matters, then link it to your specific work through dated, checkable code or PR records. Keep OC3’s impact claim distinct from OC1’s innovation claim. If you reuse an exhibit, it still needs to establish the relevant claim under each criterion; one document may not be sufficient unless it meets both.

Add a short key mapping each company and product name, then use those labels consistently in captions. Explain the repository-history change with a clear chronology, and pair the colleague’s account with dated records that still identify your work. Letters can support attribution, but they cannot carry the case alone.

3

This looks like a potentially strong Exceptional Talent profile. My main concern is that much of the independent evidence recognises the products and companies, while the letters are being relied upon to prove your personal role. Letters can support that connection, but they should not have to establish it on their own.

For MC, the salary evidence could be persuasive with a credible market comparison, although it primarily shows that your employer valued you highly. The hackathon may be weaker unless it was a recognised, highly selective competition and your individual contribution is clearly documented. As it stands, MC remains exposed.

For OC1, S3 appears to be your strongest evidence. I would show a direct connection between your pull requests, the technical improvement, the benchmark result and the independent commentary or academic citations. S2 is riskier because the current repository no longer attributes the work to you. A colleague’s explanation helps, but dated technical records would still be needed.

For OC3, the acquisition is impressive, but it primarily demonstrates the company’s value, and the underlying work may fall outside the five-year period. The documented industry adoption of S3 and verifiable Nvidia use seem stronger. The adopter companies’ VC funding and the indirect Google connection are probably too remote.

A short mapping of the company and product names would also make the evidence much easier to follow.

Overall, I see a potentially strong OC1, but MC and OC3 still need work. Your career sounds exceptional; the current evidence architecture does not yet prove it.

4

@argonaut Hope you are doing well.

Your application background sounds a bit complex, just like you mentioned, but the key is to present everything as simply and clearly as possible. Focus on explicitly highlighting what you personally built or did. If you need to mention broader team achievements or projects where your direct role isn’t obvious, be silence on what you weren’t directly involved in and back up your specific claims with a reference letter from an independent expert or an executive who was involved.

Regarding your salary, high compensation alone isn’t enough regardless of the amount. Your overall application still needs to show how you have advanced the tech sector beyond just doing your paid job.

A team award is generally considered weak evidence on its own because it doesn’t clearly prove your personal contribution. Website announcements, photos, or attestation letters from your own teammates won’t sufficiently demonstrate what you specifically did to win that prize. In my experience, Tech Nation looks heavily at context and personal recognition when evaluating awards and prizes.

Looking at your OC1 Innovation evidence, this criterion strictly requires proof of genuine innovation. Designing and building core components of “S2” shows competent work, but it doesn’t automatically prove innovation. It fits much better under OC3, significant Contribution if done within a product led company, provided it meets the required evidence criteria.

Leading performance improvements for “S3” also doesn’t demonstrate innovation. It fits better under MC for leadership, assuming the rest of the supporting evidence aligns with MC’s requirements.

Keep in mind that reference letters aren’t standalone evidence, they only serve to validate the concrete evidence you present. If the underlying evidence is weak, the assessors will dismiss the reference letters as well.

For OC3, you are expected to demonstrate substantial technical or commercial contributions in a product led company. The acquisition of Company “A” by “X” helps prove that your work was valuable enough to attract a buyer, but the acquisition alone doesn’t show what you personally did to build that value. Since your contribution involved new techniques, this piece might work under OC1 instead, provided all other innovation requirements are met.

Industry media coverage provides solid independent validation, but media statements about a product made by a founder won’t prove your individual contribution unless you are explicitly named as the developer or key contributor.

GitHub stars and forks show popularity or adoption, but not actual industry usage. Do you have direct correspondence or proof from companies using it? For instance, Google using it is great, but without direct concrete proof mentioning your work, the assessor will likely dismiss your claim.

I’d suggest going through the official Tech Nation guidance again to understand what each criterion requires, also make sure each piece of evidence is placed under the right criterion. Right now, a couple of items look misaligned between OC1 and OC3, this is the first thing before checking evidence strength. They have to be checked against the right criterion.

It might also be worth taking a bit more time to gather stronger evidence that directly attributes the work to you, as that will significantly increase your chances.

All the best.

5

Honest read: strong technical story, but MC is not strong enough yet and personal attribution is your biggest risk. Don’t submit until both are fixed.

  • MC: Salary + hackathon prize won’t cut it. Salary supports only. Hackathon is weak unless it’s a major recognised competition. MC needs external recognition of you: named media, major awards, invited keynotes, expert letters calling you a leading talent.

  • Naming chaos: Make a one-page glossary: A/B/C/X/S2/S3, dates, roles. Annotate every document. Otherwise assessors will get lost.

  • Personal contribution: Letters help but aren’t enough. Need commits, PRs, release notes, benchmarks, citations, maintainer/external expert letters that explicitly say “he designed/built X and it led to Y.” Recover GitHub history evidence if possible.

  • OC1: S2/S3 innovations look strong if you prove novelty + your role. Media not naming you is supporting only. Get CTO/CEO and external adopter letters.

  • OC3: Acquisition is your best evidence but must directly link to your personal work. S3 adoption/stars/forks good but indirect. Nvidia/Google use needs confirmation. Drop VC funding of recommenders its irrelevant.

  • Verdict: OC1/OC3 could work. MC likely fails as-is. Delay 6–2 months and build named recognition, or reframe as Promise if evidence is promise-level.