Exceptional Promise Application Review (Software Engineer)

Stage 1
1

Dear All,

A good day to you. :wave:t4: :slightly_smiling_face:

I am in the process of putting in my Global talent application for Exceptional Promise category (been gathering evidences for almost four months now, really a cumbersome process :face_exhaling:). I am a Senior Frontend Engineer for a global leader in mobile application security with 5 years of experience.

All evidence documents and letters have been prepared and duly signed. I’m planning to submit on January 24th or 25th, 2026 and would particularly appreciate any feedback on my overall evidences particularly in Optional Criteria 2 (OC2). All evidences provided are a record of all my significant impact so far.

It might be a long read, so I apologize for that in advance.

My application structure is summarized below:

Mandatory Three Recommendation Letters

NOTE: All recommendation letters were digitally signed (both the three required letters and the supporting letters used as evidences)

Letter 1 — CEO, Company A (Mobile Security)

Credentials: 10+ years cybersecurity, BlackHat speaker, recognized by Google/Microsoft/Apple
Supports: MC1 + OC3.1
Emphasizes: Product Module X leadership, platform modernization, business impact, sustained contributions, team leadership progression, UK contribution potential

Letter 2 — Managing Director, Tech Hub D

Credentials: Tech ecosystem development, corporate tech leadership ($80M revenue company)
Supports: MC1 + MC2 (alternative perspective)
Emphasizes: Long-term relationship (2020-2025), intern→engineer→mentor progression, career acceleration to international company

Letter 3 — Senior Program Manager, Google

Credentials: 12+ years experience, infrastructure programs across Africa, AI/ML strategy leadership
Supports: MC1 + OC2.2 + overall potential assessment
Emphasizes: Emerging talent potential, speaking effectiveness, community contribution, UK tech sector contribution potential

Mandatory Criterion (MC)

Theme: Emerging leadership in product engineering and community development

MC1 — Product Leadership at Company A (a global leader in Mobile Security SaaS)

Document Contents:

  • Led complete frontend development of Product Module X (industry-first post-production security monitoring solution)
  • Product Module X timeline: Initial launch Nov 2022 → Evolution to standalone platform 2022-2025
  • Revenue impact: $250k+ generated, now company’s highest-paying add-on
  • Scale: Monitoring 60,000+ applications, detected 9,000+ unscanned mobile app versions
  • Industry recognition: Featured at Conference A (world’s largest cybersecurity event), written about by multiple top-tier cybersecurity publications with combined traffic of over 1.5 million monthly visits.
  • Technical leadership: Architecture diagrams, release notes, GitHub PRs showing 14k+ code changes

Screenshots/Visual Evidence Included:

  • FIGURE A: Internal release announcement for initial module (Nov 2022) with contribution acknowledgment
  • FIGURE B: Evolution announcement to standalone platform with GitHub release link
  • FIGURE C: GitHub PR showing 14k+ code changes
  • FIGURE D: Client-side workflow documentation and architectural design diagrams (Confluence)
  • FIGURE E-1: Dashboard screenshot showing monitored applications with unscanned versions (INTERNAL)
  • FIGURE E-2: Single app dashboard view with workflow buttons and data tables (INTERNAL)
  • FIGURE F: Top tier 1 cybersecurity publication article mentioning module as breakthrough at Conference A
  • FIGURE G: Top tier 2 cybersecurity publication article highlighting feature innovation data security
  • FIGURE H: Internal screenshots showing closed deals totaling ~$160k in cross-sell value (INTERNAL)
  • FIGURE I: 2026 engineering review call screenshot recognizing module as top-paying add-on (INTERNAL)
  • FIGURE J: Production database query showing 9,000+ detected unscanned applications (INTERNAL)

MC2 — Senior Technical Mentorship at Tech Hub D (My previous company) (2022 - Present)

Document Contents:

  • 3+ years sustained volunteer mentorship (2022-2025) at structured program (6-month virtual and 3 month in-person) outside day job.
  • Selected as a mentor due to program alumni status and as a senior mentor based on expertise.
  • 150+ frontend developers mentored through in-person, hands-on guidance
  • Created curriculum modules and video tutorials for official program (HTML, CSS, JavaScript, React)
  • Peer-voted recognition: “Mentor of the Year” and “Frontend Facilitator of the Year” 2022
  • Mentee outcomes: some graduates now at top firms in the tech industry of my country.
  • Program scale: 800+ graduates since inception from 1,000+ applicants annually across West Africa

Screenshots/Visual Evidence Included:

  • FIGURE A: Learning platform screenshots showing curriculum modules list
  • FIGURE B: Video tutorial interface screenshots from learning platform (HTML & CSS modules)
  • FIGURE C: Collage of 4 in-person mentorship session photos (2022-Present)
  • FIGURE D: Social media acknowledgment posts from mentees
  • FIGURE E: Award certificates for both “Mentor of the Year” and “Frontend Mentor of the Year”
  • FIGURE F: Profiles grid showing 16 mentored interns with their current roles and companies with link to view more.

MC3 — Reference Letter from Tech Hub D Director

Supports MC1 and MC2

Letter emphasizes:

  • References my career progression with company: intern (2020) → junior engineer (2021) → voluntary mentor (2022-present)
  • Leadership during internship (cohort representative)
  • Sustained voluntary contribution over 3+ years
  • Impact on program quality and graduate outcomes
  • Progression to Company A while maintaining mentorship commitment

Optional Criterion 2 (OC2) — Industry Advancement

Theme: Knowledge sharing through speaking and community contributions

OC2.1 — Industry Advancement through Knowledge Sharing - GDG (2022 and 2025)

Document Contents:

  • Contains a 1-page Supporting Letter from community lead.
  • Multiple speaking invitations at Google Developer flagship events (2022, 2025)
  • Google I/O (July 2022): Talk about WebAssembly and practical use cases in building modern Progressive Applications - 120+ attendees
  • DevFest (Dec 2022): Talk on practical ways to secure mobile applications from a developer’s perspective - 150+ attendees
  • DevFest (Dec 2025): Co-presented “AI Technology Applications” - 130+ attendees
  • Community reach: 1,800+ active members and largest community in a certain region of my country

Screenshots/Visual Evidence Included:

  • FIGURE A: Photo collage - speaking on stage + group photo with attendees (Event 1)
  • FIGURE B: Official community social media post confirming talk with speaker bio (Event 1)
  • FIGURE C: Official community social media post announcing Event 2 with speaker details
  • FIGURE D: Photos of stage presentation and attendee section (Event 2)
  • FIGURE E: Official community social media post announcing Event 3 as speaker
  • FIGURE F: Photo collage - speaking on stage + full group photo with 130+ attendees (Event 3)

OC2.2 — Large Tech Conference F Impact (2022 and 2023)

Document Contents:

  • Contains a 2-page Supporting Letter from Programs Director at the time who is now an Innovation and Entrepreneurship Consultant currently leading innovation strategy for the Government of Cape Verde.
  • Main-stage panel speaking at large tech summit (Oct 2022) - 10,000+ attendees (24,000 registered)
  • Topic: “How to jumpstart your tech career” - shared technical career transition journey and answered questions relating to myths for aspiring techies
  • Follow-up role: Core organizer for 2023 event (led impact team doing operations like handling registration for thousands of participants; interview of laptop awardee recipients during 2023 tech event)
  • Conference scale and impact documentation
  • Post-event attendee feedback and testimonials (although I wasn’t mentioned in the posts)

Screenshots/Visual Evidence Included:

  • FIGURE A: Email invitation from organizing team for panelist session
  • FIGURE B: Social media post showing 4 photos of massive crowd during registration
  • FIGURE C: Split image - main stage appearance (highlighted) + attendee perspective view
  • FIGURE D: Email screenshot of “Certificate of Recognition” as Impact Department team lead (2023)
  • FIGURE F: Social media screenshots showing 4 post-event testimonials from attendees

OC2.3 — Open Source Blockchain Contributions (2022 and 2023)

Document Contents:

  • Project 1 (2022): Trading platform frontend development - GitHub shows top contributor status
  • Project 2 (2023): DeFi lending protocol complete UI implementation - Top contributor
  • Project 3 (2023): IP protection platform - Ranked top 5 projects among 15+ teams at international hackathon
  • Projects don’t have much industry recognition. Projects 1 and 2 even though open sourced with me as top contributor were mostly POCs for emerging technologies at the time. I was top contributor for project 3 but this is a hackathon and I am not sure about the impact of the project to the overall community but I explained in detail what problems they were trying to solve.
  • The platforms for which projects 1 and 2 had gone through significant changes over the past years and I am unable to provide third party validation as the data had been sunsetted. I have all repo stats though.

Screenshots/Visual Evidence Included:

  • FIGURE A: GitHub contribution graph showing top contributor status with commit list for Project 1
  • FIGURE B: UI screenshots of Project 1 (trading interface and wallet connect pages)
  • FIGURE C: GitHub contribution graph showing top contributor status with commit list for Project 2
  • FIGURE D: Application UI screenshots for Project 2 (multiple pages shown)
  • FIGURE E: GitHub commit history screenshot for Project 3 development
  • FIGURE F: GitHub contributors page showing top contributor ranking for Project 3
  • FIGURE G: Discord/platform screenshot announcing Top five finalists with team name highlighted

Optional Criterion 3 (OC3) — Significant Technical Contributions

Theme: High-impact engineering contributions with measurable business outcomes

OC3.1 — Technical Contributions at Company A (Mobile Security SaaS)

Document Contents:

  • Platform Modernization Leadership that aided platform expansion:
    • Led Framework X v3→v4 upgrade across 30+ components
    • Led TypeScript migration (100+ modules)
    • Test coverage improvement: 15% → 70% over 2 years
    • Built component library and design system documented in Storybook
  • A vulnerability Comparison Module I had built:
    • Real-time drift analysis comparing security results across app versions
    • Complex comparison logic implementation
  • Recognition:
    • Top frontend contributor (60% of major releases since joining)
    • Received award for leading frontend initiatives Q2 2025 (Award series started in 2025)
    • Promotion to Senior Engineer and Frontend Team Lead 2025
  • Business Impact:
    • Features I led has supported Company ARR growth: almost $1.5M+ revenue growth between 2022 and 2023.

Screenshots/Visual Evidence Included:

  • FIGURE A: Storybook documentation interface screenshot + GitHub PRs list for global UI components
  • FIGURE B: Confluence document showing E2E test integration documentation for Cypress framework
  • FIGURE C: GitHub PR screenshot for Cypress integration + list of related component migration PRs
  • FIGURE D: GitHub PR screenshot showing file compare pages implementation for Feature Y
  • FIGURE E: Confluence documentation screenshots explaining comparison logic algorithms (2 screenshots of pages)
  • FIGURE F: Internal dashboard screenshots showing file compare results (vulnerability changes visualization)
  • FIGURE G: GitHub contributors page showing top contributor status (2022 to date)
  • FIGURE H: Revenue growth chart from analytics platform showing $2.5M→$4.5M trajectory
  • FIGURE I: Award for frontend initiatives certificate (Q2 2025)
  • FIGURE J: Internal communication screenshots showing multiple feature release announcements

OC3.2 — Engineering Manager Reference Letter

Supports OC3.1 in detail

Letter emphasizes:

  • Direct management perspective (2023-2025)
  • Specific technical contributions with examples
  • Leadership progression and team management
  • Quality standards and delivery consistency
  • Impact on company competitive positioning

OC3.3 — Technical Contributions at Startup B (Marketing Automation SaaS) (2023)

Document Contents:

  • Contains a 1-page Supporting Letter from CEO and Co-Founder who is also a global talent EP awardee. Letter supports my impact to the product.
  • Role: Lead Frontend Engineer (part-time contract, 3 months intensive - 2023)
  • Company details: started from Nigeria but now moved operations to the UK and registered there as startup, marketing automation platform
  • Complete frontend ownership:
    • Next.js and TypeScript architecture
    • Performance optimization: 70%+ page load time reduction (SSR, SSG, code splitting)
    • Component library and design system creation
    • Top contributor: 160+ commits establishing complete client-side foundation
  • Key Features Built:
    • Feature A - Marketing message customization interface (custom rich-text editor, variable insertion, template management)
    • Feature B - Embeddable lead generation widget (deployed 5,200+ domains, 12,000+ pages)
  • Business Impact:
    • Platform scale: 14,000+ active users within 13 months
    • Feature A: 2.3M+ marketing automations executed, 1M+ business leads generated
    • Feature B: 1M+ leads captured across deployments
    • Successful Product Hunt launch with positive reviews

Screenshots/Visual Evidence Included:

NOTE: I couldn’t provide product metrics mentioned in the document due to limited access to company resources. I only talked about my leadership and used the reference letter to corroborate my claims.

  • FIGURE A: GitHub contributors graph showing top contributor status over 3-month period (PRIVATE REPO - redacted)
  • FIGURE B: UK Government Companies House business registration page for Startup B
  • FIGURE C: Product Hunt launch page screenshot + 5 user review comments showing positive feedback
  • FIGURE D: Application UI screenshot showing Feature A editor interface
  • FIGURE E: GitHub commit history screenshot for messaging channels development (PRIVATE REPO - redacted)
  • FIGURE F: Application UI screenshot showing Feature B embeddable form interface
  • FIGURE G: GitHub commit history screenshot for Feature B development (PRIVATE REPO - redacted)

OC3.4 — Technical Contributions at Startup C (Healthcare Technology) (2023)

Document Contents:

  • Contains a 1-page Supporting Letter from CEO to support company metrics along with the other content.
  • Role: Founding Frontend Engineer (part-time contract, 7 months - 2023)
  • Company mission: Free pharmacy management system addressing Nigerian healthcare accessibility
  • Complete frontend architecture ownership:
    • Next.js and TypeScript infrastructure
    • Design system and component library
    • Zero-to-launch responsibility over 7 months
  • Core Modules Built:
    • Authentication and Role-Based Access Control (RBAC) for healthcare compliance
    • POS/Checkout System (multi-payment methods, inventory sync, receipt generation)
    • Inventory Management System (expiry alerts, batch tracking for drug traceability, stock management)
  • Healthcare Impact:
    • 20+ pharmacies across 5 cities
    • 1,000+ prescriptions processed
    • 10,000+ pharmaceutical products managed
    • Prevented medication dispensing errors through automated tracking
    • Reduced manual stock-taking time from hours to minutes
    • Patient safety improvements through expiry prevention

Screenshots/Visual Evidence Included:

NOTE: I couldn’t provide product metrics mentioned in the document due to limited access to company resources. I only talked about my leadership and used the reference letter to corroborate my claims.

  • FIGURE A: GitHub contributors graph showing sole frontend contributor status (May-Dec 2023) (PRIVATE REPO - redacted)
  • FIGURE B: Application screenshots showing multiple authentication pages (login, signup, account setup)
  • FIGURE C: Two dashboard screenshots side-by-side - Inventory Management System (left) + POS Interface (right)
  • FIGURE D: GitHub commit history screenshot for POS feature development (PRIVATE REPO - redacted)
  • FIGURE E: GitHub commit history screenshot for Inventory Management System (PRIVATE REPO - redacted)
  • FIGURE F: GitHub PR screenshot for authentication pages implementation (PRIVATE REPO - redacted)

Thank you for taking time to read this far. I appreciate any form of feedback I can get towards strengthening my application.

CC: @alexnk @Akash_Joshi @pahuja @Francisca_Chiedu @Raphael

I would really appreciate your feedback on my application.

1 Like
2

there is no recongnition in your MC
naming this community belittle the events DG Developer Community Speaking Engagements

3

Thanks for the reply @tunde1234. Can you shed more light on this?

Point 1

The evidence examples which I feel my MC aligns with are:

You led the growth of a product-led digital technology company, product or team inside a digital technology company, as evidenced by reference letter(s) from leading industry expert(s) describing your work, or as evidenced by news clippings, lines of code from public repos or similar evidence.

Having a product which I built receive international third party validation through recognition by top tier cybersecurity publications while generating significant revenue for my company is how I am framing this. Based on my job role, my impact can be felt mostly through code and the things I build.

Outside of your normal day-to-day job role, you established, led or were a senior contributor to a large technology-led industry initiative, evidenced through reference letter(s) from global senior project executives.

OR

You led the growth of a non-profit organisation or social enterprise with a specific focus on the digital technology sector, as evidenced by reference letter(s) from leading industry expert(s) describing your work, or as evidenced by news clippings or similar evidence.

As a addition to the first MC document, I have significantly led the growth of a large technology-led industry initiative which was non-profit through mentoring that have had a real impact.

Point 2

GDG Developer Community Speaking Engagements evidence document was actually named Industry Advancement through Knowledge Sharing - GDG. Does this hold more meaning?

I’d appreciate your suggestion as I have some doubts about my OC2 evidences.