Use examples of the applicant’s own analysis, decisions or process work, with enough context to distinguish them from team output reviewed only at a high level.
Attribute contributions accurately
A presentation created by a subordinate should not be described as the applicant’s technical work. Explain any substantive contribution the applicant made and why it demonstrates the claimed knowledge.
Provide enough context to follow the change from proposal to implementation. Distinguish the original author, later updates and the applicant’s own notes. A screen may show an output without explaining the employee’s reasoning. Never sign a declaration implying authorship of a colleague’s examples.
The employer decides what to withhold, but must leave enough to prove the claim. A supervisory role does not disqualify an applicant from showing personal knowledge, provided the record captures the judgment actually exercised rather than a simple approval signature. Describe a specific instance where the manager chose between competing options, resolved a conflict in the underlying method, or corrected a subordinate's approach, since that kind of decision demonstrates command of the process itself. A colleague who received direction can describe what was taught and how, which corroborates the manager's contribution without requiring the manager to have personally produced every document. Keep the emphasis on the reasoning behind the direction given, because oversight alone, without a described judgment, reads the same as passive awareness rather than personal expertise.