Hi all — I’d really value input from anyone who has been endorsed (or refused) as a technical applicant with a services-firm employment background
Background: 19 years in technology, 13 as a Salesforce technical architect. Certified Application Architect, Data Architect, and Agentforce Specialist. My entire employment history is IT services companies — two large global consultancies (including several years in-country in London) and currently a staffing firm placing me at a global automotive manufacturer as Sr. Technical Architect. The problem: A well-known immigration firm reviewed my profile and declined, citing the guide’s ineligible list (“Consultancy, ERP Consultancy…”) — their view is that Salesforce implementation work through service companies is generally not eligible, regardless of other evidence.
What my case actually rests on (not consultancy delivery):
Mandatory + OC2: I independently authored an open-source Salesforce DevOps tool (built outside employment, unpaid). It is in production at two global enterprises and under evaluation at three more across four countries (verifiable via PackageSubscriber data). Launch post: ~108k LinkedIn impressions, sustained technical engagement from two Salesforce MVPs, a public technical exchange with the CTO-level team behind a leading competing DevOps toolchain. Published byline article on a major editorially-gated community platform; invited video on a well-known Salesforce YouTube channel;
OC1: As an employee on my current engagement, I solely designed and built a Python-based RAG semantic search and AI diagnostic engine, now in production — planning to frame under “innovation as an employee working in a new digital field or concept,” evidenced by a solo-authored architecture document and a signed employer letter confirming authorship and production use.
Thank you, Francisca. Here is my document map. (Kept anonymous — the tool is publicly tied to my name.)
MANDATORY — recognised as a leading talent
I have build a tool that is run by major companies
MC Doc 1 — Companies use my tool. Two separate proofs:
(a) Salesforce’s installation records. - when any company installs a tool like mine, Salesforce’s system automatically logs that install on their side — like an app store showing who downloaded an app. I cannot create, edit, or delete these logs. They show my tool live in production at a global car maker and a NASDAQ-listed IT firm, and under testing at three more companies (Germany, Netherlands, US — including a Johnson & Johnson subsidiary). The document will explain this in the same plain terms for the assessor.
(b) A signed letter from the car maker confirming they use it in production. So: machine-generated proof plus human confirmation, each backing the other.
MC Doc 2 — Salesforce itself recognised my writing.
Salesforce’s editors selected my article for their official Architecture Blog (final revisions now, publishing soon). - this is Salesforce’s own publication — the platform vendor choosing my work on merit. Authors cannot pay or self-publish there; editors select you.
MC Doc 3 — The wider field noticed. Two separate proofs:
(a) A published article on the largest community learning platform in the Salesforce world, where an editor (a Salesforce MVP — a title Salesforce awards to top community experts, fewer than ~300 worldwide) reviews and approves every piece.
(b) My tool’s launch post reached ~108,000 people with 1,100+ reactions in four days, which led to an invitation to present the tool on a popular Salesforce YouTube channel — the channel owner publicly called it an invitation.
OC2 — contribution outside my occupation The story: I built this alone, unpaid, in my own time — and experts engaged with it.
OC2 Doc 1 — I built it myself, outside work.
GitHub’s change history (every code edit is time-stamped and credited automatically) showing months of solo building and maintenance, all in my own time, unpaid.
OC2 Doc 2 — Experts engaged with the work. Two separate proofs:
(a) A public technical debate on linkedIn comments where the CTO-level team behind a competing tool challenged mine, and I answered point by point — rivals don’t debate work that doesn’t matter.
(b) Detailed comment threads from two Salesforce MVPs discussing the tool’s design.
OC1 — innovation as an employee The story: I stepped outside my own specialism to build something new.
OC1 Doc 1 — The system.
A design document I wrote alone for an AI-based search and diagnostic system, live in production at my client. Important context the document will state: I built it in Python — a language outside my core Salesforce expertise. I taught myself what the problem needed. That is the “new digital field” part of this criterion: a Salesforce architect independently building a working AI system in an unfamiliar stack.
OC1 Doc 2 — The client confirms it.
A signed letter from the client confirming I designed and built it alone and that it runs in production. (Agreed in principle; the signatory is not one of my three referees.)
Plus: CV and three reference letters — a Technical Architect Director at Salesforce, a former Director at a UK public financial institution , and a senior engineering lead at the car maker(my manager).
My question: with this map, does my services-firm employment history still sink the mandatory criterion, in your experience?
The consultancy exclusion is about the evidence you lean on, not a blanket bar on anyone who’s worked at a services firm. Your MC and OC2 case rests on a tool you built independently and unpaid, which sits entirely outside the employment relationship the immigration firm was worried about. That’s the right instinct, employer classification only bites where you’re leaning on the employer relationship itself as the evidence.
OC3 is where the services-firm history bites harder. That criterion is written for a founder, senior executive, board member or employee of a product-led digital technology company specifically, and a global automotive manufacturer engaged through a staffing firm doesn’t fit that definition even if your technical contribution there is real. I’d carry the AI search system under OC1 instead, innovation as an employee working on a new digital field doesn’t carry the same product-led company requirement, rather than also asking it to do OC3 work.
Referee choice matters too. The Guide explicitly excludes managers at outsourcing or consultancy firms from counting as “leading industry experts” for recognition evidence. None of your three referees fall into that category, so that part of your structure holds.
Your MC case stands or falls on whether the panel accepts the installation logs and the Salesforce blog placement as third-party recognition beyond employer testimony, not on your job title. That’s a stronger position than the immigration firm’s blanket read suggested.
For the Global Talent Visa. What matters is whether your evidence demonstrates innovation, technical excellence, leadership, and recognition beyond routine client delivery. Based on what you’ve shared, your consulting background alone should not be viewed as a barrier to applying. The success of your application will depend on whether your evidence clearly demonstrates innovation, measurable impact, independent recognition, and your contribution to the wider digital technology ecosystem.
Before submitting, review each piece of evidence and ask:
Does it demonstrate innovation rather than routine delivery?
Is the impact independently verifiable?
Does it show external recognition beyond my employer?
Does it clearly support the criterion under which it is being submitted?
A well-structured application that focuses on independently recognised technical achievements is generally more persuasive than one centred primarily on employment history.
We hope this feedback is helpful, and we wish you the very best with your Global Talent endorsement application.