Seeking Review: Exceptional Talent : Software Engineering Leader (Digital Technology)

Stage 1: Tech Nation Endorsement
1

Hi everyone,

Thank you to this community, reading through past threads here has already shaped a lot of how I’ve structured my application. I’m preparing to submit under Exceptional Talent and would really value feedback on the arrangement below, and an honest read on whether it stands a chance.

Background:
I’m a software engineering leader with around 11 years of experience across mobile, backend, data and platform engineering, currently an Engineering Manager at a growth-stage tech company in Africa.

Work Experience:

  • Company A (tech company, Africa, current): joined as an IC engineer, promoted to Lead, now Engineering Manager. Jan 2022–present.
  • Company B (regional examinations authority): software developer. 2019–2021.
  • Company C (US-based media/streaming company, contract role, concurrent with Company A): Senior Software engineer, Jun 2022–Oct 2023.
  • Company D (fintech/wallet startup, West Africa, consulting engagement): Jan 2025–present.

Letters of Recommendation (3 official + 2 supporting statements):

  • Co-founder & CTO, Company A (current employer). Covers MC/OC1/OC3.
  • Senior Director of Engineering, Company C (former manager, contract role). Covers OC3.
  • CEO, Company D (client relationship, not an employer). Covers OC1.
  • Supporting statement: former engineering leader at Company A, now CTO elsewhere. Covers MC/OC3 (process metrics, promotion).
  • Supporting statement: former manager at Company B. Covers OC1 (authorship of systems built there).

Mandatory Criterion:

  • A profile in a major national newspaper covering my career and engineering leadership (general-interest outlet, not a tech trade publication).
  • Career progression from IC to Engineering Manager at Company A, corroborated by two people who managed me at different stages.

Optional Criterion 1 (Innovation):

  • Built Company A’s flagship product single-handedly as the sole engineer on it at the time, from zero to public launch.
  • Built Company B’s first internally-developed application (50k+ downloads, 4.2★ on Google Play) plus two other internal systems, confirmed by a former manager since none are published under my name.
  • Company D: built cross-currency payment rails for a non-custodial wallet, supporting multiple African currencies and a major stablecoin, as an external consultant, corroborated by the CEO directly.

Optional Criterion 3 (Significant Technical/Commercial Contribution):

  • Company A flagship product: 295% active-user increase in its first week (built solo).
  • Company A: a real-time feature tied to a major national event that pushed the product to #3 in its App Store category.
  • Company A: process changes as Lead, cut incident response to near-zero and code review turnaround from 2 days to ~4 hours.
  • Company A: architected a data platform now tracking a large volume of financial and investment records, publicly credited by name by the CTO.
  • Company C: contributed to a hackathon-winning project during a concurrent contract role.

Would really appreciate an honest read on this, arrangement, evidence, letters, all of it. What stands out as weak or missing, and where do you think an assessor would push back hardest? Also curious whether this feels ready to file as is, or if there’s something obvious I’m not seeing.

2

@Raphael @Noddy @Akash_Joshi

Your feedback will be highly appreciated here.

3

Hello @Terminator. I think you should read the requirements @ https://technation-globaltalentvisa-guide.notion.site/

For OC1, the innovation is more about the newness of the solution and evidence of the solution being new. This is why patents are better for OC1 evidence. You also need to show evidence about how you individually contributed to the solution.

For OC3, it is more about the impact. I think you should merge the evidences you have in OC1 into the current OC3 evidences that you have.

For the letters of recommendations, it is less riskier to have recommendations from people who are not mentioned in your evidences.

The problem with your evidences and recommendations is that they are all tied to the people you have worked it which now reduces the quality of the OC3 evidences and backfires.

4

Thank you for the feedback @iyanuashiri, this is insighful and genuinely useful.

I checked the guide you linked, it confirmed your OC1 point exactly: for an employee, it’s about newness, not sole ownership, patents being the example evidence. My old OC1 item was indeed an impact story mislabeled as innovation. I’ve swapped it for a genuinely new AI automation project I built solo last year, well-documented, and will move the old item’s impact numbers into OC3 instead.

on your commend on the my recommendation and evidence being from the same set of people and only people I’ve worked with, I will be making some changes to follow a new arrangement:

Thanks again for the pointer, here’s where things stand now.

Letters of Recommendation (3 official + 4 supporting statements):

  • Head of Engineering, Company A (current manager). Covers MC.
  • Senior contact at Company E, an investment/finance firm that uses Company A’s data platform (client relationship, arm’s-length; not yet secured). Covers MC/OC3.
  • CEO, Company D (client relationship, not an employer). Covers OC1.
  • Supporting statement: Co-founder & CTO, Company A. Covers MC/OC3 (career progression, data platform).
  • Supporting statement: former manager at Company B. Covers OC1 (authorship of systems built there).
  • Supporting statement: Senior Director of Engineering, Company C (former manager, contract role). Covers OC3.
  • Supporting statement: former engineering leader at Company A, now CTO elsewhere. Covers MC/OC3 (process metrics, promotion).

Mandatory Criterion:

  • A profile in a major national newspaper covering my career and engineering leadership.
  • Career progression from IC to Engineering Manager at Company A, corroborated by two people who managed me at different stages, plus equity as a minor supporting detail.

Optional Criterion 1 (Innovation):

  • Company A: built an AI automation system last year, the first of its kind internally, solo, cutting a manual process from ~4 hours to under a minute, still live. Evidence: architectural diagram, screenshot of it running, git commit history.
  • Built Company B’s first internally-developed application (50k+ downloads, 4.2★) plus two other internal systems, confirmed by a former manager since none are published under my name.
  • Company D: built cross-currency payment rails for a non-custodial wallet, supporting multiple African currencies and a major stablecoin, as an external consultant, corroborated by the CEO directly.

Optional Criterion 3 (Significant Technical/Commercial Contribution):

  • Company A flagship product: 295% active-user increase in its first week, plus a later real-time feature tied to a major national event that pushed it to #3 in its App Store category (built solo). Evidence: internal analytics, App Store/Google Play screenshots.
  • Company A: architected a data platform now tracking a large volume of financial and investment records, since extended with the automation project above, publicly credited by name by the CTO in a contemporaneous internal post. Evidence: Architectural diagram, screenshot of it running, git commit history, screenshot of CTO publicly acknowledging my contribution and leadership
  • Company C: contributed to a hackathon-winning project during a concurrent contract role. The win was announced by the hackathon organizers themselves, and the project was later selected into a formal incubator program. Evidence: Hackathon winner announcement, screenshots of colleagues congratulating me, screenshot of the incubator team.

I dropped a fourth OC3 item entirely, some engineering process metrics that had zero backing beyond my former manager’s word. That was exactly your concentration point, so rather than patch it, I cut it.

Appreciate the specific feedback. Let me know if anything else stands out now.

5

The restructuring did its job. Swapping in the AI automation build gives OC1 a real newness claim, and cutting the unbacked process metrics removes the concentration problem that got flagged. Both were the right calls.

One thing to watch is that the automation project now straddles two criteria. It anchors OC1 as your innovation piece, and it also surfaces in OC3 as the extension to the data platform. An assessor needs each piece of evidence sitting under one criterion doing one job, so keep the automation build in OC1 and let the data platform carry OC3 on its own commercial impact.

MC is where an assessor will still push hardest. The newspaper profile is your one genuinely external piece, strong provided the coverage is about you and your leadership specifically. The progression and the manager corroboration both sit inside your own organisation, and Exceptional Talent expects recognition the wider field gives you, sustained over time. You need a second external anchor there: an individually judged award, or a speaking slot you were invited to by organisers outside your own network.

Your OC1 evidence is still self-produced documentation, which the Guide treats as the weakest proof of novelty. The Company D payment rails, corroborated directly by the CEO, is your most external OC1 piece, so that’s the one to lean on hardest.

6

The updated structure is materially clearer than the original one, particularly because you have separated the innovation evidence from the technical/commercial contribution evidence. I would still treat the following as the main points an assessor is likely to test.

For MC, the national newspaper profile is potentially useful if it specifically recognises your own engineering work, achievements or leadership, rather than simply mentioning you as an employee of the company. Career progression from IC to Engineering Manager is useful supporting evidence, but it is not automatically the same as external recognition as potential talent. I would therefore make sure your second MC evidence document independently demonstrates recognition of you personally.

For OC1, the new AI automation project is better positioned than the previous impact-based example if you can demonstrate what was genuinely new or innovative about what you created. The architecture, Git history and evidence that the system is live establish that you built and deployed it, but the evidence should also explain what made the solution innovative and what changed because of your work. The Company B and D examples can support OC1 if the innovative element of your own contribution is clear.

For OC3, the revised evidence is stronger because you have focused on the 295% active-user growth, App Store ranking, real-time feature and data-platform outcomes rather than relying on process metrics. The key issue remains attribution: the evidence should independently show what you personally designed or built, your responsibility for the outcome, and the resulting technical or commercial impact. The CTO/director statements can corroborate this, but should not be the only proof.

The Company C hackathon example could also potentially support OC3, but I would only rely on it if the evidence clearly establishes your individual technical contribution and what resulted from it.

Overall, OC1 and OC3 are plausible placements, but I would strengthen the application around three specific questions: MC — personal external recognition; OC1 — genuine innovation; OC3 — individual contribution and resulting significance/impact. Also make sure each evidence document has a distinct purpose and is not reused across criteria.

For Exceptional Promise, remember that you need at least 2 evidence documents showing recognition as potential talent, plus at least 2 pieces of evidence for each of the 2 optional criteria you select. Your CV and recommendation letters are separate from the maximum 10 eligibility-evidence documents.

7

Could you add in some more info in MC, many people actually failed on MC than the OCs when i check evidences here. In all humility and respect, this appears week.

Man this is leadership, Your tech leader right, show em wat you gat upto when thy gut gets satisfied, until then…

Man hv mentored young devs show it.

you hv spoken on conferences show it.

You hv contributed to Open Source Show it.

Man we all devs do these things bt here wanted here on Paper…And I want u win