No. It may establish training in the product without showing the organizational knowledge on which the transfer relies.
Identify what the certificate leaves open
Use accurate project, process and experience records to explain the applicant’s role. Keep contributions by colleagues clear and avoid presenting a current explanation as an old contemporaneous record.
Files that persuade in this area tend to look mundane: version-controlled procedure documents with an author's name on them, a training register showing who taught whom, a log of investigations that were referred upward, an email chain where a difficult judgement call was made. Ask which examples establish the material facts, and coordinate the employer's technical staff and legal reviewer before submission so the evidence neither overexposes confidential information nor becomes too generic to support the claim. Revision histories that name the employee, commissioning records for a system built in-house, an internal manual they wrote, and purchase files showing standard equipment was modified to a specification all speak without adjectives. Useful records can include controlled versions, change approvals, pilot results, training materials, access logs, deviation reports, meeting notes, and examples bearing the applicant's authorship or decision role.