Exceptional Promise review: around six years in tech, Remotion open source evidence, MC and recommendation letters

Hi everyone,

I’m preparing a Stage 1 endorsement application under Exceptional Promise in digital technology and would appreciate candid feedback on my evidence.

I have nearly six years of experience in technology. My first two years were junior roles where I built my engineering foundation.
My greater technical ownership, leadership and contributions outside work developed later. I now work as a senior software developer at a UK property technology company.
Previously, I was a senior engineer and tech lead at a fintech company and worked on web and mobile products for a large publisher.

Mandatory criterion, recognition: In 2026, I served as a technical judge at a hackathon involving my employer, a university and an industry partner. I assessed teams using formal criteria and supported their use of the event’s technology platform.
I have the event agenda, judging framework, scoring and participant communications, and public event posts.
An external organiser has been asked to formally confirm my judging role.
I also have a frontend team lead appointment on a collaborative project outside work.

OC2, contribution outside work: I contributed a fix to an established open-source framework with more than 60,000 stars.
The maintainers merged it, shipped it in an official release and credited me in their release notes. I also have multiple merged contributions to another open-source product, covering new functionality, AI integration and reliability.
Separately, I made sustained public contributions to a former employer’s open-source repository after my employment there ended. I can provide the public records to a reviewer.

OC3, significant technical contribution: At my current company, I developed a build and runtime configuration approach that was adopted across additional repositories.
I have evidence of my original implementation, the request for wider adoption and the completed rollout. I also built a product feature that the CEO confirmed using for property-market analysis.
I also built a product feature that the CEO confirmed using for property-market analysis.
At the fintech company mentioned earlier, I delivered core mobile, web and backend functionality, then progressed into technical leadership.
I have delivery records and a signed letter from the former CTO who supervised and promoted me.

I have OC1 innovation evidence for an integrated property-analysis product and a marketplace I co-founded as CTO. The marketplace is built but has not launched to live users or generated revenue. I am considering OC1 as an alternative to OC2 or OC3.

Three signed recommendation letters, with the recommenders’ CVs attached: one from the founder and CEO of my current UK employer, and one from the former CTO who supervised me at the fintech company. My third recommender is my former boss at the publishing company. He is its Deputy IT Manager and Webmaster, has 14 years of experience and directly supervised my work. .

My main questions are:

  1. Is Exceptional Promise credible with my total experience, given that my first two years were junior and my leadership developed later?

  2. Does the judging evidence show recognition of my potential, especially if the external organiser confirms my role?

  3. Would you prioritise OC2 and OC3, or use OC1 instead? What is the weakest item?

  4. Are these three recommenders suitable?

  5. Is there any other thing I need to change or update?

I can share redacted evidence pages and public links with someone willing to review the documents more closely. Honest feedback would be appreciated. Thank you.

Title is barely relevant for GTV, so I would not complicate the case with that.

With nearly six years in technology, you are slightly beyond the typical Promise profile. I would call this borderline Promise. A strong case can still overcome that, but your evidence should focus on achievements within the recent five-year period.

MC: I would not rely heavily on the hackathon judging as currently presented. Ideally, MC should establish recognition that exists independently of your employer. Here, it reads more like you represented your employer at an event involving the employer. If the judging role was independently offered to you because of your standing, that changes the position. Otherwise, its value may be limited.

OC2: A merged PR and contributor credit alone do not necessarily establish significant contribution. The substance matters. Was there an issue-to-PR process, meaningful technical analysis, review discussion and a substantial implementation? What happened after merge? Release inclusion, backports, documentation changes or subsequent adoption would help establish significance.

For the former employer repository, I would clearly prove when your employment ended and that the later contributions were genuinely voluntary. Otherwise, it may be unclear whether this was actually activity outside your occupation or some continuing professional obligation.

OC3: This sounds much stronger. The CEO letter is useful, but I would corroborate it with the public technical footprint wherever possible. You already mention repositories and implementation records elsewhere, so it would be careless not to use those to support the contribution claimed under OC3.

OC1: Revenue is not required to prove innovation, but an unlaunched product is harder because you have less external evidence showing that the claimed innovation exists and matters. Equally, revenue alone does not prove innovation. A product could make substantial revenue and still fail OC1 if the underlying work is not demonstrably innovative.

Overall, I would currently prioritise OC2 and OC3, with OC3 looking the clearest. I would only replace one with OC1 if the innovation evidence is substantially stronger than it currently sounds.

Thanks, your distinction between judging at an event and being recognised independently is helpful.

I participated through my employer, so I would not describe it as an independent invitation. However, the CEO says he chose me to judge because he trusted my technical judgement, and I have the scoring records showing that I assessed the teams. If the external organiser confirms my role but not the reason I was chosen, would you still regard this as useful MC evidence, or only supporting context?

I also have proof that my OC3 architecture was implemented and adopted across other repositories, so that case does not rest on the CEO letter alone.

Your OC2 point makes me think I should lead with the larger merged feature work and its review history, using the official release credit as corroboration. If the hackathon is too closely tied to my employer for MC, could recognition from an independent open-source project help form a separate MC case, or would you keep that entirely under OC2?

Once again, I really appreciate your response @Jeleel_M

On MC, I think the main issue is the requirement for wider industry recognition. The organiser confirming that you judged and the scoring records prove the role, but they do not necessarily prove why you were recognised beyond your employer. Since the participation came through your employer, I would still treat it as supporting MC evidence rather than a strong standalone item.

Your OC3 sounds much stronger if you already have implementation and adoption across other repositories. Definitely use those public footprints to support the CEO letter.

For OC2, I would lead with the larger merged feature, review history and official release credit. That gives a much clearer contribution trail.

Independent open-source recognition can help MC, but it should show recognition of you, not just that your PR was merged. A maintainer explicitly recognising your expertise, repeated reliance on your work, or being given a meaningful project role would be much stronger for MC.

@Akash_Joshi, @Raphael and other may have a different view on how much weight they would give the hackathon judging for MC.

The organiser’s confirmation independently verifies that you served as a judge. Your CEO’s explanation adds context about why you were selected, though it remains employer testimony unless the organiser confirms the selection rationale. Judging can support MC; its weight depends on evidence of selectivity, your responsibilities and the recognition attached to the role. Use the event records to show what you assessed, and treat the CEO’s account as corroboration.

The substantial merged feature work and sustained review history should lead your OC2 case. Explain the scope of your contribution and establish that it was voluntary work beyond your paid role. The release credit corroborates attribution after the work itself is evidenced. Independent open-source recognition could support a distinct MC claim if the project recognises you personally as an emerging leader; routine credit for a contribution belongs with that OC2 evidence. Keep the claims separate and do not reuse the same evidence across criteria.

Cross-repository adoption gives your OC3 architecture evidence of wider use. Identify the repositories using it and show your individual role in the design and rollout. Evidence of sustained use or outcomes would establish its impact; adoption alone does not show how significant the contribution was.

Thank you very much for your feedback. For OC2, I will document my separate contribution that was credited in an official release, alongside the larger merged feature.

I agree that MC is the part I most need to strengthen, particularly the evidence of recognition beyond my employer. I will treat the hackathon judging as supporting evidence and see how I can establish more about how I was selected.

Thank you @Akash_Joshi
Awesome feedback
I’ll work on this

Once your experience is over 5 years, you are generally assessed against the Exceptional Talent level rather than Exceptional Promise. The technical judging role may also be worth looking at more carefully. Because the hackathon involved your employer, it may not necessarily demonstrate recognition from the wider industry. In recent years, hackathon judging has not carried as much weight on its own, although it could potentially support an Exceptional Promise application if there is strong independent recognition around the role.

For the open-source evidence, how long did you contribute to the projects, and how recent are the contributions? The recency and sustained nature of the contribution could be important.

Also, from what you have shared, you currently seem to have one main piece of evidence under each criterion. You generally need at least two pieces of evidence for each criterion, so I would look at whether you have enough strong, distinct evidence rather than relying too heavily on one achievement.

Personally, I would prioritise OC2 and OC3, as your evidence seems more straightforward for demonstrating measurable contribution and impact than innovation.

For OC1, I would be cautious. Simply building a product does not necessarily demonstrate innovation. You would need to clearly show what was innovative about the product, what problem it solved differently from existing solutions, and ideally some evidence of external recognition, adoption, traction or impact. If the marketplace has not launched and has no users or revenue yet, that could make the innovation case harder to establish.

Thank you very much @Francisca_Chiedu

@Ayodele_Ayoola Hope you’re doing well.

With over five years of experience in tech, you would generally fall under the Exceptional Talent route. Because of that, you would need to clearly explain to Tech Nation why you’re applying through the Exceptional Promise pathway despite having more than five years of experience.

Also, the fact that your first two roles were junior positions doesn’t change the fact that you were already working in mainstream technology during those years. The level of seniority is usually not the deciding factor. What may help is if there was a genuine gap or break in your tech career. For instance, if you took time out for an MSc, a study leave, or worked in a completely non tech role for a period, then make that very clear in your personal statement and anywhere else it is relevant. Don’t assume the assessor will connect the dots on their own. Spell it out clearly.

Regarding your judging evidence, based on what you’ve described, it may be viewed more as an oversight or evaluation activity within your employer’s ecosystem rather than assessing the work of peers as a recognised expert in your field. The assessment appears to focus on how participants used an event technology platform, which seems tied to your company’s use case rather than demonstrating sector wide expertise.

Likewise, evidence such as the event agenda, judging framework, scoring sheets, participant communications, and event posts could potentially be considered internal or self generated documentation. You could still include them, but I would position them as supporting evidence rather than the primary evidence.

Even if an external organiser confirms your involvement, the challenge is that the activity itself may not meet the threshold of assessing the work of other experts in the field as an expert. Another point is that you currently appear to have only one piece of evidence under this criterion. Ideally, you should have at least two distinct and independent pieces of evidence for each criterion you’re claiming.

For OC2, the 60,000 stars achievement is certainly noteworthy. However, the key wording in this criterion is substantial and meaningful contribution. I’ve seen cases where contributions were rejected because assessors considered them basic rather than significant.

The fact that maintainers merged your work and credited you is definitely positive because it demonstrates recognition. Your multiple merged contributions to another open source project can also strengthen the case. The important questions are: what exactly did you contribute, and how impactful were those contributions?

I would recommend presenting all of the open source work together as a single OC2 evidence set because they fall under the same category of contribution. Doing this can help demonstrate sustained involvement over time, which is valuable. Just make sure that each piece of evidence should remain unique and not be reused across multiple criteria.

If I remember correctly, you mentioned:

I now work as a senior software developer at a UK property technology company.

One thing to consider is that many property technology companies are not necessarily product led businesses. Since OC3 specifically requires contributions made within a product led digital technology company, this point becomes very important.

You may find the discussion below useful in understanding why the product led requirement is often a decisive factor for OC3:

Your work within the company is certainly relevant and could be helpful if you can demonstrate your technical contributions with solid evidence such as code contributions, internal documentation, technical correspondence, architecture decisions, and supporting letters from leadership. That said, before anything else, you need to address whether the company satisfies the product led requirement.

Regarding the other company you mentioned, is it product led? What products have they built or delivered? Also, while a CTO letter can add value, it is usually not enough on its own. The letter should reference and support documentary evidence that clearly shows your technical contribution.

For OC1, you’ve explained what you co founded, but I don’t yet see clear evidence showing innovation.

An integrated property analysis product combined with a marketplace could potentially be innovative. However, based on recent feedback trends I’ve seen, simply combining those two functions may not by itself be enough to establish innovation in the way Tech Nation expects.

The key question is: what exactly was innovative about what you built? What was genuinely new, unique, or differentiated?

Overall, OC2 looks potentially workable, but OC3 first needs to satisfy the product led requirement. OC1 could work as well, but you would need stronger evidence demonstrating innovation.

On your specific questions:

  1. Is Exceptional Promise credible with my total experience, given that my first two years were junior and my leadership developed later?

In my view, no. Since those two years were still spent in mainstream technology roles, the fact that they were junior positions generally does not reduce your overall years of experience for Tech Nation’s assessment.

  1. Does the judging evidence show recognition of my potential, especially if the external organiser confirms my role?

At the moment, it still appears largely internal because the recognition comes through relationships and activities that are mainly known within your company and its immediate partners. It may carry more weight if the external organiser is a well known and reputable organisation with recognised standing in the industry.

  1. Would you prioritise OC2 and OC3, or use OC1 instead? What is the weakest item?

OC2 seems to be okay, but you need another type of contribution to have to unique sets in the criterion. OC3 currently has a challenge because of the product led requirement.OC1 has potential, but as presented, there isn’t enough evidence showing innovation.

  1. Are these three recommenders suitable?

I would look beyond their job titles. Review their public profiles carefully and make sure they are clearly recognised experts in their respective fields, as required by the guidance. It’s also worth checking that they meet all other recommendation letter requirements.

  1. Is there anything else I should change or improve?

Yes. you should spend more time strengthening your evidence. Most of the areas that need attention have already been highlighted above.

Regarding sharing redacted evidence and public links

I can share redacted evidence pages and public links with someone willing to review the documents more closely. Honest feedback would be appreciated. Thank you.

I agree that having the actual evidence reviewed by someone experienced with the Tech Nation process can be extremely valuable. However, for me, any review or guidance provided outside this platform would be treated as a paid service.

All the best.