Global talent clarifications

I would appreciate some clarification regarding eligibility for the Global Talent Visa under the Exceptional Promise route.

Can an applicant qualify with approximately two years of overall professional experience, consisting of one year in a non tech sector and one year of formal professional experience in the technology sector as a Software Developer?

I have also been consistently learning, developing software, and building projects outside of formal employment, although it took some time to secure my first professional role in the technology sector. Would having only one year of formal software development experience be sufficient for an Exceptional Promise application, provided that I can demonstrate strong evidence of my potential, achievements, and contributions to the technology sector?

Additionally, regarding open source contributions, does a contribution need to have measurable engagement, such as a significant number of GitHub stars, forks, users, or other evidence of adoption, to be considered valid evidence for a Global Talent Visa application? Or can meaningful contributions to reputable open source projects strengthen an application even when the project does not have a large number of stars or forks?

Thank you for your time and guidance. I would greatly appreciate any clarification you can provide.

@zeez Trust you’re okay.

Yes, in terms of eligibility, an applicant with one year of non sector experience and one year of sector experience can still be eligible. However, it might be difficult to prove your potential to be a leader through your skills and achievements. Your experience in a non tech role should be in areas that are closely adjacent to tech, so you can actually use some of your achievements and skills. Also, Tech Nation checks for sustained and continued impact or contribution, regardless of the pathway(promise or talent)

So while you may be eligible, you may struggle to present sustained achievements. But if you were in a role adjacent to core tech, like project management, for let’s say three years, and then transitioned into becoming a Software Engineer, that’s different. Because project management is an adjacent role in tech, you already have skills and some achievements that can be useful. And here’s how Tech Nation puts it:

…but can have had a longer career in another type of work. You must be able to prove your potential to be a leader through your skills and achievements.

So your one year of experience in a non tech role won’t meet that “longer career” element. Also, learning and developing software is good for self development, but Tech Nation’s application is evidence based. And that evidence needs to be validated by reputable people, platforms, or organisations.

On your question:

Would having only one year of formal software development experience be sufficient for an Exceptional Promise application?

While you may manage to be eligible with one year of experience plus your self development and personal projects, you will struggle to show sustained, externally validated evidence.

Yes, regardless of the pathway, you need to show reasonable metrics from relevant sector projects.

I will suggest you give some time to gather more evidence, contribute more to the open sources to increase your chances.

All the best.

Yes, one year of formal technology employment does not by itself prevent an Exceptional Promise application. There is no stated minimum number of years of formal software-development employment for Exceptional Promise. The relevant issue is whether you can demonstrate that you are a potential leader through the required recognition and qualifying evidence.

Your projects and software development outside formal employment can therefore be relevant, provided they demonstrate achievements or contribution to digital technology rather than simply showing that you have been learning. For Promise, you still need recognition as potential talent and at least two qualifying optional criteria, with the early-career requirement.

For open source, the guidance does not state a minimum number of GitHub stars, forks, users or downloads that a project must have. So a project does not need a particular star count to be relevant. What matters is what the contribution demonstrates: your individual technical contribution, its significance, and, where applicable, recognition or impact within the digital-technology community. A meaningful contribution to a reputable project can therefore be useful even if the repository is relatively small, but simply having merged PRs is not automatically sufficient to establish the relevant criterion. The evidence should explain what you contributed and why that contribution matters.