Seeking an honest review of my UK Global Talent Visa (Exceptional Promise) evidence as a DevOps/Cloud Engineer, covering my professional recognition, technology contributions outside employment, open-source work, and significant technical contributions

Stage 1: Tech Nation Endorsement
1

GTV Exceptional Promise DevOps / Cloud Engineering Evidence Review

Hello everyone, please I would appreciate an honest review of my evidence structure for the UK Global Talent Visa under the Exceptional Promise route, with a focus on DevOps and Cloud Engineering.

My background combines Cloud Engineering, DevOps, Infrastructure Automation, FinOps and technical education. I currently work as a DevOps Engineer, where my work involves cloud infrastructure, CI/CD, containerisation, Kubernetes, Terraform, monitoring and deployment engineering.

Outside my professional employment, I contribute to the wider technology ecosystem through technical publications, television interviews, open-source contributions, technical education, community leadership and technology books.

My proposed evidence structure is below.

Mandatory Criteria

MC1: Published Technical Articles & Technology Thought Leadership

GTV Requirement: Demonstrate recognition as a potential leader in digital technology through published material or other evidence demonstrating contribution and visibility within the technology sector.

I have published 13+ technology articles from 2024 to date covering areas including Cloud Computing, Artificial Intelligence, Data, Cloud Security, Digital Transformation and Technology Education.

My articles have appeared in technology/business publications including BusinessDay, TechNext, TechEconomy, TechSoma Africa and Vanguard.

I intend to submit a focused selection of my strongest publications rather than submitting every article.

Selected publications

  1. “Why Africa’s AI Adoption Will Depend on Secure and Reliable Cloud Infrastructure”
    TechEconomy - 27 August 2026

  2. “Navigating Inflation Through Cloud Technology: How Businesses Can Reduce Costs and Build Resilience”
    TechEconomy - 7 August 2026

  3. “Data Driven Future: Empowering Africa’s Youth Through Tech & Cloud Skills”
    TechNext - August 2025

  4. “Cloud Adoption in Nigeria’s Banking: The Key to a Modern, Inclusive Future”
    BusinessDay - 10 January 2025

  5. “Why African Businesses Need to Treat Cloud Security as a Business Priority, Not an IT Problem”
    TechSoma Africa - 12 September 2024

Evidence I intend to provide

  • Publication name and logo

  • Article title, My name and byline

  • Publication date

  • Article URL, Screenshots of the published articles

  • Evidence of reader engagement/comments where available

  • Submission emails to the publications and Editorial acceptance/review emails

  • Publication/platform information demonstrating the credibility and technology relevance of the outlets

The evidence will demonstrate that my writing is focused on advancing discussion around Cloud, AI, Data and digital technology, rather than being unrelated general-interest writing.

MC2: Television Interviews & Expert Technology Commentary

GTV Requirement: Demonstrate recognition within the digital technology sector through evidence of professional recognition and contribution.

I have been invited to participate in television programmes to discuss technology-related topics, including Cloud, AI, cybersecurity, digital transformation and emerging technology trends.

My television appearances/invitations include:

  • Channels TV Tech Trends, 2025

  • Rapid TV Tech Trends, 2026

  • Global TV 2026

  • STV 2025

  • LN247 2025

For the application, I intend to focus on my strongest three appearances:

Evidence I intend to provide

  • Invitation email from the television station, why I was selected/invited, the email connected the invitation to my technology expertise and publications

  • Programme flyer, My photograph, name on the official programme material, Date and time of the programme, Topic to discussed, Television station logo

  • YouTube recording/official video on their Platform

  • Evidence of me participating in the programme, Video engagement including views, comments and likes

The purpose of this evidence is to demonstrate that my expertise in Cloud, AI, DevOps and emerging technology has resulted in invitations to provide public technology commentary.

MC3: Open-Source Contributions

GTV Requirement: Demonstrate recognition or contribution to the digital technology sector through significant technical contributions.

I have contributed to established open-source technology projects, including projects maintained by established technology organisations and communities.

My contributions involve technical fixes, codes, documentation improvements, issue resolution and code contributions, with contributions reviewed and accepted by project maintainers.

Evidence I intend to provide

For each selected contribution:

  • GitHub repository URL

  • GitHub issue/issue number and it’s URL

  • Pull Request URL, Pull Request showing my contribution

  • Evidence that the PR was merged

  • Maintainer review/comments, Maintainer approval

  • Commit history, Relevant code or documentation changes

  • Description of the problem/issue I addressed, Technical explanation of my solution

  • Evidence showing how the contribution benefits the project/users

  • Project/community information demonstrating the significance and active maintenance of the repository

I will focus on my strongest merged contributions rather than presenting a large number of minor GitHub activities like Docker Docs, next cloud server

Optional Criterion 2 - Contribution Outside My Core Employment

GTV Requirement: Demonstrate significant contribution to the digital technology sector outside my primary employment.

My OC2 evidence focuses on three areas:

  1. Technology community leadership and education

  2. Technical knowledge dissemination through books

  3. External recognition for my technology/community work

OC2-1: Founder & Technology Community Leadership -CodeSphere Hub

I am the Founder and Executive Director of CodeSphere Hub, a technology community focused on Technology, AI, STEM and Finance Empowerment.The community provides technology education, certification preparation, mentoring, technical masterclasses and technology outreach programmes.

Evidence: Community Leadership

  • CodeSphere Hub official website identifying me as Founder/Executive Director

  • Leadership team and volunteer structure

  • Programme documentation

  • CodeSphere Hub Annual Strategic Programme for 2026, Community activities and programmes

  • Evidence of the community’s reach and activities

Evidence: International Women’s Day Technology Outreach

I organised and hosted technology outreach activities designed to introduce students to technology, AI, digital skills and future technology careers.

Evidence includes:

  • International Women’s Day Technology Outreach flyer and 2 other more Technology Outreach

  • Flyer showing my name, photograph and role as host

  • Evidence of 150+ students participating

  • Video recording of the programme on CodeSphere Hub YouTube

  • Video of me speaking/facilitating

  • Video of Student testimonials from each school

  • Letter of appreciation from the school

  • BusinessDay coverage of the outreach identifying me in the published coverage

Evidence: Power BI & Azure Certification Masterclasses

I have also organised/facilitated technical education programmes focused on Power BI and Microsoft Azure certification preparation.

Evidence includes:

  • Masterclass flyer of programme to be for 1 month

  • LinkedIn announcement

  • Programme curriculum and Session schedule

  • Evidence showing me as facilitator/instructor and YouTube recording

  • Engagement including 30+ comments, likes on YouTube

  • Certification success/results from participants, LinkedIn testimonials from participants who passed certification examinations all tagged me and appreciated me

  • Testimonials from participants across Nigeria, India, Pakistan and the UK and their Video success stories

  • i will pick 2–3 strongest independent participant testimonials

Evidence: WorldQuant University Partnership

I initiated a partnership with WorldQuant University for its Data Science Lab programme. The programme ran for approximately 16 weeks.

Evidence includes:

  • Initial partnership communication, Email confirming/accepting the partnership

  • Programme announcement, Publicity materials on LinkedIn

  • Evidence of the programme, YouTube documentation, Commentss, Likes, Views

  • Participant engagement, Participant testimonials

NOTE: CodeSphere Hub website also documents all these activities, providing an additional consolidated source of evidence.

OC2-2: Technical Books & Knowledge Dissemination

Outside my professional role as a DevOps/Cloud Engineer, I contribute to the technology sector through technical education and knowledge dissemination. I have authored practical technology publications covering Power BI, Microsoft Azure Storage and Artificial Intelligence in Audit. My publications are designed to make technical knowledge more accessible, including free-access distribution that reduces financial barriers to technical education.

Publications

1. Artificial Intelligence (AI) in Audit: Intelligent Analytics, Fraud, Risk, and Sustainability Oversight

Published on Selar and Amazon July 2026

2. Azure Storage Mastery: A Practical Guide to Designing, Securing, Managing and Optimizing Cloud Storage on Microsoft Azure

Published on Selar July 2025

3. Power BI Interview Questions and Past Questions: A Practical Guide to Power BI Interview Preparation and Assessment

Published on Selar September 2024

Evidence of reach and external engagement

For my Power BI publication:

  • 4,816 free orders/downloads, 631 five-star reviews

  • 12 independent video testimonials and Testimonials from readers who used the material for examinations/interviews

For my Azure Storage publication:

  • 2,087 free orders/downloads, 93 five-star reviews

  • Independent review from an Azure MVP

Evidence I intend to submit

  • Selar dashboard showing orders/downloads

  • Book publication page

  • Review/rating screenshots and Reader testimonials

  • Independent video testimonials and Video testimonials showing how readers used the material

  • Letter from the Azure MVP who reviewed my book

  • Book covers, publication details and Publication dates

  • Links to the books/platforms

The evidence will focus on reach, independent reader engagement and practical technology education impact, rather than simply demonstrating that I wrote books.

OC2-3: External Recognition & Media Features

I have also received external recognition for my technology education and community leadership work.

TechSoma Africa

“Oladosu Ibrahim is Building Technology Pathways by Creating Opportunities for Others”

Published April 2025.

The feature discusses my technology/community work and CodeSphere Hub.

Supporting evidence:

  • Published article, Publication screenshot

  • Email requesting/confirming the feature and acknowledging my work

  • Article URL and Publication date

TechCabal

“Building Africa’s Digital Workforce: The Growing Impact of Oladosu Ibrahim and CodeSphere Hub”

Published in 2026.

Supporting evidence:

  • Published article and Article screenshot

  • Article URL, Evidence identifying me and CodeSphere Hub

  • Publication date

  • Supporting correspondence where available

I will use these features to demonstrate external recognition of my contribution to technology education and digital skills development, rather than simply counting media appearances.

Optional Criterion 3 - Significant Technical Contribution

GTV Requirement: Demonstrate significant technical, commercial or product contribution to a technology business. For OC3, I am presenting my individual technical contribution as a DevOps Engineer within an EdTech technology business, rather than attributing the wider work of the engineering team to myself. The evidence will specifically demonstrate the infrastructure, automation, deployment, cloud and platform engineering activities delivered or maintained by me, together with their measurable technical and operational impact.

OC3 / Evidence 1: DevOps Engineering

Role: DevOps Engineer within an EdTech technology business.

I am providing evidence of my individual contribution to the deployment, automation, scalability, reliability and operational management of an EdTech platform.

Evidence

  • AWS/Azure cloud infrastructure and resource configuration

  • Docker containerisation, Kubernetes deployments and orchestration

  • Terraform Infrastructure as Code, GitHub Actions CI/CD pipelines

  • CloudWatch and related monitoring/observability configurations

  • Infrastructure and system architecture diagrams

  • Relevant anonymised code and configurations

  • Deployment and workflow evidence

  • Git commits, pull requests and repository history where appropriate

The exhibits will be specifically annotated to show the infrastructure components, automation workflows, configurations and engineering activities attributable to my work, rather than presenting general platform infrastructure as evidence of my contribution.

Examples may include optimising cloud compute and resource configurations to improve utilisation and reduce unnecessary infrastructure consumption, automating deployment processes through CI/CD, containerising application workloads, managing Kubernetes deployments, and implementing Infrastructure as Code to make infrastructure provisioning more consistent and repeatable.

OC3 / Evidence 2: Measurable Technical & Operational Impact

The second evidence area will demonstrate the measurable outcomes resulting from my engineering work, supported by technical records and employer verification.

Where the business can disclose the information, I will provide before-and-after or operational metrics demonstrating:

  • Reduced deployment time and manual deployment effort

  • Fewer deployment and configuration errors

  • Improved CI/CD reliability and release consistency

  • Improved application and infrastructure availability

  • Better infrastructure utilisation

  • Cloud infrastructure cost optimisation

  • Faster detection and resolution of operational issues

  • Improved scalability for increasing platform workloads

  • Reduced infrastructure management overhead

Employer Verification

A formal employer reference will independently confirm:

  • My position as DevOps Engineer, Employment period

  • Technical responsibilities, Technologies used, including cloud infrastructure, Docker, Kubernetes, Terraform, GitHub Actions and monitoring

  • Specific engineering initiatives delivered by me, Infrastructure/platform components attributable to my work, Technical or operational impact, where independently verifiable

I would particularly appreciate feedback on whether the evidence is sufficiently strong for Exceptional Promise, whether any evidence appears repetitive or weak, and whether there are areas where I should strengthen the documentation before submission.

Thank you. @Raphael @Akash_Joshi

Thank you so much for all you do here…God bless you. I will really appreciate your feedback.

2

Thank you. @Francisca_Chiedu @Noddy

Thank you so much for all you do here…God bless you. I will really appreciate your feedback for my evidence above

3

The two profile features about you and the community are the strongest MC material in the pack, and they are currently under OC2. Media recognition belongs in MC, where the Guide asks for details of the publication and its audience. Before moving them, check each one is independent editorial and not a paid or sponsored placement, since assessors dismiss promotional features. The open source piece is the natural one to drop, because the Guide’s bar there is a significant contribution to a substantial project, which small fixes and docs changes won’t meet.

Articles you wrote yourself are weaker for MC than they look. They show you can get published, and the Guide actually lists thought-leadership op-eds under OC2. Leave out the pitch emails wherever the articles end up, because they show the pieces were your own initiative. Two of the selected articles also came out in the weeks before applying, and a cluster that recent is weaker than a record spread across the last few years.

OC3 is currently a description of the job. The infrastructure tooling is what a DevOps engineer is hired to use, so the evidence only works once it carries numbers, and depending on what the business agrees to disclose is the risk. OC3 is one of only two optional criteria here and won’t hold without figures. Get the before and after numbers confirmed in writing now, such as deployment time or cloud cost, and build the documents around the two changes that moved them most.

4

Sudais, on MC3 specifically, you’re right to push on this. Right now, your MC3 reads like a GitHub activity log: repos, PRs, commits, maintainer approvals. That proves you contributed. It does not prove you’re a potential leader in digital tech. For GTV, merged PRs are table stakes. The assessor will ask: So what? Who depends on it? What changed? Who noticed? Where is it cited or referenced?

5

The structure is generally coherent for an Exceptional Promise application, but the main issue is making sure each evidence item demonstrates the specific criterion, rather than simply showing that you are active in technology.

For MC, the publications and television appearances can potentially support the recognition requirement, but their strength will depend on whether they demonstrate recognition of your expertise rather than simply showing that you have published articles or appeared on programmes. The strongest evidence would show why you were selected, your technology expertise, the standing/reach of the publication or programme, and your individual contribution. The 13 articles should therefore not be relied upon simply because of their number, and television appearances should be supported by evidence showing that you were invited specifically because of your technology expertise.

For OC2, CodeSphere Hub provides a coherent basis for the criterion because it demonstrates activity outside your employment over time. However, the strongest evidence will be the material showing your personal leadership, scale of participation, independently verifiable outcomes and recognition by others. The books may support the wider knowledge-sharing narrative where there is substantial independent readership, reviews or other evidence of impact, but publication alone should not be treated as evidence of significant contribution.

For OC3, the proposed approach is sensible, but the technical artefacts alone will not establish a significant contribution. The evidence should connect your individual engineering work to measurable technical, operational, commercial or product impact. Git commits, Terraform, Kubernetes, CI/CD and architecture evidence should be used to establish what you personally built or changed, while employer verification and before/after metrics should establish why that contribution was significant to the technology business.

I would also be careful about repetition between OC2 community activities, books and media coverage. Each exhibit should have a distinct purpose. If the same outreach event, article or testimonial is being used repeatedly to establish different points, it may dilute rather than strengthen the portfolio.

Overall, the areas I would scrutinise most before submission are the level of recognition demonstrated by MC, the independent significance of the OC2 contribution, and the attribution of measurable impact to you personally in OC3.

6

Hi @Sudais hope you’re doing well.

A quick one your evidence listing.

First for MC, this isn’t about articles you’ve written yourself to share your ideas or show you’re a leader in your field, that’s actually for OC2. For MC, it need published pieces in professional or major trade publications, or well known media, that are about your work and how it’s moved the digital tech sector forward. Think things like you built a solution that fixed a real problem and the media covered it, you started a company that got acquired for a meaningful sum by a well respected organisation or you secured funding for a project you created, and that was featured publicly. The key thing here is: the publication is talking about what you’ve done not you writing the piece yourself.

Then MC2 this can work well, but only if the invitation clearly says you were invited as a recognised expert in your field, and what you discussed is relevant and actually pushes the sector forward and should not be online/virtual appearance. The invite shows recognition as an expert, but Tech Nation also want to see why they see you that way, because of something you’ve built, achieved, or are developing that advances the industry. Being asked just to talk generally about cloud, AI or DevOps won’t carry much weight, anyone can search for that online. From what we’re seeing in recent feedback, they want to see that you were invited specifically because of the real, tangible work you’ve done (or are doing) in those areas not just to share thoughts that many other people in your field could also talk about. That kind of general knowledge sharing fits better under OC2, if it meet other evidence elements, but for MC the focus is always, you’re being recognised as a leader for the impactful work you’ve delivered. That’s exactly what the official guidance means too

…publications about your work, …

not articles or interviews where you’re just sharing information or expertise broadly

For MC3, contributing to open source absolutely can count, but for MC specifically you need to be the author, lead, co-author, or a major contributor and the project itself has to be significant in scale. When you list your metrics and impact, focus more on your leadership role and the real difference you made, rather than just listing tasks you completed.

On OC2, Contribution Outside Core Employment: you’ve explained what your evidence is about, but haven’t clearly stated exactly which evidence you’re submitting as proof. For your work as Founder and Technology Community Lead with CodeSphere Hub, your website and records of your leadership are helpful, but they’ll be seen as self created or authored unless you also show clearly how your work actually advanced the sector as a whole. And what exactly are you providing to prove the community’s reach and its real world activity?

Your International Women’s Day tech outreach can be okay, but organising the event alone won’t show how it advanced the sector forward. It also needs to be something established and structured, not just a one off thing you put together. You’ve mentioned 150+ students were involved, so show that real engagement, things like testimonials from participants is good, engagements on your website or platform, email replies can help .Just sharing a video of you speaking or photos and flyers sadly won’t carry much weight on their own. If you worked alongside well known tech companies or government bodies, that’s exactly the kind of external validation that proves your work matters and has real backing.

You’ve got some really good evidence listing here, well done. But then, your list focuses too much on describing what you did, and not enough on showing independent, verified proof of that work and its impact as evidence.

I won’t be able to give very meaningful feedback without seeing the actual document your are submitting. I hope this bits help.

All the best.